Trafimarrelo.Com.Mx - Info trafimarrelo.com.mx

trafimarrelo.com.mx receives about 181 unique visitors and 544 (3.00 per visitor) page views per day which should earn about $2.22/day from advertising revenue. Estimated site value is $1,621.29. According to Alexa Traffic Rank trafimarrelo.com.mx is ranked number 4,772,139 in the world and 4.0E-6% of global Internet users visit it. Site is hosted in San Antonio, Texas, 78288, United States and links to network IP address 13.84.220.114. This server supports HTTPS and doesn't support HTTP/2.

About - trafimarrelo.com.mx


Technologies used on Website

Web Servers
IIS
Web Frameworks
Microsoft ASP.NET
Operating Systems
Windows Server

trafimarrelo.com.mx Profile

Title: phpinfo()
Last update was 125 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with trafimarrelo.com.mx in any way. Only publicly available statistics data are displayed.

How popular is trafimarrelo.com.mx?

181 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
181
Monthly Unique Visitors:
4,344
Pages per Visit:
3.00
Daily Pageviews:
544
Alexa Rank:
4,772,139 visit alexa
Alexa Reach:
4.0E-6%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  trafimarrelo.com.mx
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is trafimarrelo.com.mx?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
trafimarrelo.com.mx
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
trafimarrelo.com.mx
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much trafimarrelo.com.mx can earn?

Daily Revenue:
$2.22
Monthly Revenue:
$66.60
Yearly Revenue:
$810.30
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do trafimarrelo.com.mx lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is trafimarrelo.com.mx worth?

Website Value:
$1,621.29

+ Where is trafimarrelo.com.mx hosted?

Server IP:
13.84.220.114
ASN:
AS8075 
ISP:
Microsoft Corporation 
Server Location:
San Antonio
Texas, TX
78288
United States, US
 

Other sites hosted on 13.84.220.114

There are no other sites hosted on this IP

+ How fast does trafimarrelo.com.mx load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

First CPU Idle 0.3 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Speed Index 0.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 81 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://trafimarrelo.com.mx/
76 KB
http://trafimarrelo.com.mx/infor.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
3 KB
http://trafimarrelo.com.mx/infor.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42
2 KB
Minimizes main-thread work - 0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
70 ms
Rendering
34 ms
Other
17 ms
Parse HTML & CSS
6 ms
Script Evaluation
2 ms
Script Parsing & Compilation
1 ms
Avoid an excessive DOM size - 2,941 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
2,941
Maximum DOM Depth
8
Maximum Child Elements
221
Keep request counts low and transfer sizes small - 3 requests • 81 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
381 KB
Document
176 KB
Image
25 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Enable text compression - Potential savings of 64 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://trafimarrelo.com.mx/
76 KB64 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://trafimarrelo.com.mx/
0 ms132 ms76 KB76 KB200text/htmlDocument
http://trafimarrelo.com.mx/infor.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
145 ms246 ms3 KB2 KB200image/gifImage
http://trafimarrelo.com.mx/infor.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42
145 ms219 ms2 KB2 KB200image/gifImage
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://trafimarrelo.com.mx/infor.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
0 ms3 KB
http://trafimarrelo.com.mx/infor.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42
0 ms2 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
156 ms
6 ms
172 ms
68 ms
240 ms
5 ms
246 ms
21 ms
280 ms
14 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
129 ms2 ms1 ms
Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 130 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 1.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
First Contentful Paint (3G) 2349 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 1.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Keep request counts low and transfer sizes small - 3 requests • 81 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
381 KB
Document
176 KB
Image
25 KB
Stylesheet
00 KB
Media
00 KB
Font
00 KB
Script
00 KB
Other
00 KB
Third-party
00 KB
Enable text compression - Potential savings of 64 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

URL
SizePotential Savings
http://trafimarrelo.com.mx/
76 KB64 KB
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://trafimarrelo.com.mx/
0 ms331 ms76 KB76 KB200text/htmlDocument
http://trafimarrelo.com.mx/infor.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
350 ms475 ms3 KB2 KB200image/gifImage
http://trafimarrelo.com.mx/infor.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42
350 ms448 ms2 KB2 KB200image/gifImage
Uses efficient cache policy on static assets - 2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://trafimarrelo.com.mx/infor.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
0 ms3 KB
http://trafimarrelo.com.mx/infor.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42
0 ms2 KB
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
353 ms
8 ms
361 ms
7 ms
369 ms
8 ms
378 ms
109 ms
488 ms
5 ms
495 ms
40 ms
538 ms
18 ms
JavaScript execution time - 0.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
822 ms10 ms4 ms
Avoids enormous network payloads - Total size was 81 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://trafimarrelo.com.mx/
76 KB
http://trafimarrelo.com.mx/infor.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
3 KB
http://trafimarrelo.com.mx/infor.php?=PHPE9568F35-D428-11d2-A769-00AA001ACF42
2 KB
Minimizes main-thread work - 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Style & Layout
480 ms
Rendering
193 ms
Other
95 ms
Parse HTML & CSS
37 ms
Script Evaluation
10 ms
Script Parsing & Compilation
4 ms
Garbage Collection
2 ms
Avoid an excessive DOM size - 2,941 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). Learn more.

Statistic
ElementValue
Total DOM Elements
2,941
Maximum DOM Depth
8
Maximum Child Elements
221
Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Server response times are low (TTFB) - Root document took 330 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

All text remains visible during webfont loads
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Avoid chaining critical requests
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

PHP Version 5.4.24 renders only 7 pixels tall (18 CSS pixels) .
PCRE (Perl Com…sions) Support and 688 others render only 5 pixels tall (12 CSS pixels) .
C:\Program Fil…120\DTS\Binn\; and 775 others render only 5 pixels tall (12 CSS pixels) .
Zend Engine v2…d Technologies and 4 others render only 5 pixels tall (12 CSS pixels) .
pdo_sqlite and 48 others render only 8 pixels tall (20 CSS pixels) .
mbstring exten…e version 2.1. and 109 others render only 5 pixels tall (12 CSS pixels) .
no value and 115 others render only 5 pixels tall (12 CSS pixels).
#FF8000 and 1 others render only 5 pixels tall (12 CSS pixels).
#0000BB and 1 others render only 5 pixels tall (12 CSS pixels).
#000000 and 1 others render only 5 pixels tall (12 CSS pixels).
#007700 and 1 others render only 5 pixels tall (12 CSS pixels).
#DD0000 and 1 others render only 5 pixels tall (12 CSS pixels).
Additional Modules and 3 others render only 8 pixels tall (20 CSS pixels).
This program i…file: LICENSE and 2 others render only 5 pixels tall (12 CSS pixels).

Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 63.8KiB (84% reduction).

Compressing http://trafimarrelo.com.mx/ could save 63.8KiB (84% reduction).

Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,008 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <th>Value</th> falls outside the viewport.
The element <td class="v">AMD64</td> falls outside the viewport.
The element <td class="v">\\.\pipe\IISFC…6-a5b221915971</td> falls outside the viewport.
The element <td class="v">10000</td> falls outside the viewport.
The element <td class="v">C:\Program Fil…(x86)\PHP\v5.4</td> falls outside the viewport.
The element <td class="v">C:\ProgramData</td> falls outside the viewport.
The element <td class="v">C:\Windows\sys…ppData\Roaming</td> falls outside the viewport.
The element <td class="v">C:\inetpub\tem…AppPool.config</td> falls outside the viewport.
The element <td class="v">DefaultAppPool</td> falls outside the viewport.
The element <td class="v">C:\Program Fil…)\Common Files</td> falls outside the viewport.
The element <td class="v">C:\Program Fil…)\Common Files</td> falls outside the viewport.
The element <td class="v">C:\Program Files\Common Files</td> falls outside the viewport.
The element <td class="v">TRAFIMAR-WEB</td> falls outside the viewport.
The element <td class="v">C:\Windows\system32\cmd.exe</td> falls outside the viewport.
The element <td class="v">NO</td> falls outside the viewport.
The element <td class="v">C:\Windows\sys…\AppData\Local</td> falls outside the viewport.
The element <td class="v">2</td> falls outside the viewport.
The element <td class="v">Windows_NT</td> falls outside the viewport.
The element <td class="v">C:\Program Fil…120\DTS\Binn\;</td> falls outside the viewport.
The element <td class="v">.COM;.EXE;.BAT….WSF;.WSH;.MSC</td> falls outside the viewport.
The element <td class="v">x86</td> falls outside the viewport.
The element <td class="v">Intel64 Family…, GenuineIntel</td> falls outside the viewport.
The element <td class="v">6</td> falls outside the viewport.
The element <td class="v">4f01</td> falls outside the viewport.
The element <td class="v">C:\ProgramData</td> falls outside the viewport.
The element <td class="v">C:\Program Files (x86)</td> falls outside the viewport.
The element <td class="v">C:\Program Files (x86)</td> falls outside the viewport.
The element <td class="v">C:\Program Files</td> falls outside the viewport.
The element <td class="v">C:\Windows\sys…nt\PowerShell\</td> falls outside the viewport.
The element <td class="v">C:\Users\Public</td> falls outside the viewport.
The element <td class="v">C:</td> falls outside the viewport.
The element <td class="v">C:\Windows</td> falls outside the viewport.
The element <td class="v">C:\Windows\TEMP</td> falls outside the viewport.
The element <td class="v">C:\Windows\TEMP</td> falls outside the viewport.
The element <td class="v">GTMX</td> falls outside the viewport.
The element <td class="v">TRAFIMAR-WEB$</td> falls outside the viewport.
The element <td class="v">C:\Windows\sys…\systemprofile</td> falls outside the viewport.
The element <td class="v">C:\Windows</td> falls outside the viewport.
The element <td class="v">/infor.php</td> falls outside the viewport.
The element <td class="v">/infor.php</td> falls outside the viewport.
The element <td class="v">Microsoft-IIS/8.5</td> falls outside the viewport.
The element <td class="v">HTTP/1.1</td> falls outside the viewport.
The element <td class="v">0</td> falls outside the viewport.
The element <td class="v">80</td> falls outside the viewport.
The element <td class="v">trafimarrelo.com.mx</td> falls outside the viewport.
The element <td class="v">/infor.php</td> falls outside the viewport.
The element <td class="v">C:\inetpub\wwwroot\infor.php</td> falls outside the viewport.
The element <td class="v">/</td> falls outside the viewport.
The element <td class="v">GET</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">40967</td> falls outside the viewport.
The element <td class="v">66.102.8.47</td> falls outside the viewport.
The element <td class="v">66.102.8.47</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">C:\inetpub\wwwroot\infor.php</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">172.16.0.6</td> falls outside the viewport.
The element <td class="v">/LM/W3SVC/1</td> falls outside the viewport.
The element <td class="v">DEFAULT WEB SITE</td> falls outside the viewport.
The element <td class="v">1</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">off</td> falls outside the viewport.
The element <td class="v">CGI/1.1</td> falls outside the viewport.
The element <td class="v">C:\inetpub\wwwroot</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">0</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">no value</td> falls outside the viewport.
The element <td class="v">C:\inetpub\wwwroot\</td> falls outside the viewport.
The element <td class="v">/LM/W3SVC/1/ROOT</td> falls outside the viewport.
The element <td class="v">7.1.1952.0</td> falls outside the viewport.
The element <td class="v">67.212.187.106</td> falls outside the viewport.
The element <td class="v">Mozilla/5.0 (L…Safari/537.36</td> falls outside the viewport.
The element <td class="v">trafimarrelo.com.mx</td> falls outside the viewport.
The element <td class="v">gzip,deflate,br</td> falls outside the viewport.
The element <td class="v">text/html,*/*;q=0.8</td> falls outside the viewport.
The element <td class="v">0</td> falls outside the viewport.
The element <td class="v">keep-alive</td> falls outside the viewport.
The element <td class="v">no-store, no-cache</td> falls outside the viewport.
The element <td class="v">RESPONDER</td> falls outside the viewport.
The element <td class="v">/infor.php</td> falls outside the viewport.
The element <td class="v">1574565667.5225</td> falls outside the viewport.
The element <td class="v">1574565667</td> falls outside the viewport.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Leverage browser caching
You have enabled browser caching. Learn more about browser caching recommendations.
Reduce server response time
Your server responded quickly. Learn more about server response time optimization.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Minify HTML
Your HTML is minified. Learn more about minifying HTML.
Minify JavaScript
Your JavaScript content is minified. Learn more about minifying JavaScript.
Eliminate render-blocking JavaScript and CSS in above-the-fold content
You have no render-blocking resources. Learn more about removing render-blocking resources.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does trafimarrelo.com.mx use compression?

trafimarrelo.com.mx does not use compression.
Original size: 75.37 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

trafimarrelo.com.mx supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: *.trafimarrelo.com.mx
Organization: Trafimar S.A.
Location: Cuidad de Mexico, OU=Sistemas, Cuidad de Mexico, MX
Issuer: GlobalSign Organization Validation CA - SHA256 - G2
Valid from: May 11 19:54:24 2017 GMT
Valid until: May 12 19:54:24 2018 GMT
Authority: Is not a CA
Keysize: 2048 Bits
Common Name: GlobalSign Organization Validation CA - SHA256 - G2
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign Root CA
Valid from: Feb 20 10:00:00 2014 GMT
Valid until: Feb 20 10:00:00 2024 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support

trafimarrelo.com.mx does not support HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Content-Type: text/html
Server: Microsoft-IIS/8.5
X-Powered-By: PHP/5.4.24
X-Powered-By: ASP.NET
Date: Sun, 24 Nov 2019 03:21:02 GMT
Content-Length: 77183

+ DNS Lookup

Type Ip Target TTL
TXT 600
TXT 600
MX trafimarrelo-com-mx.mail.protection.outlook.com 600
SOA 600
Mname ns1-04.azure-dns.com
Rname azuredns-hostmaster.microsoft.com
Serial Number 1
Refresh 600
Retry 300
Expire 2419200
Minimum TTL 0
A 13.84.220.114 581
NS ns1-04.azure-dns.com 3581
NS ns2-04.azure-dns.net 3581
NS ns3-04.azure-dns.org 3581
NS ns4-04.azure-dns.info 3581

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.mx...
Domain Name: trafimarrelo.com.mx

Created On: 2004-01-21
Expiration Date: 2020-01-20
Last Updated On: 2019-10-11
Registrar: Akky (Una division de NIC Mexico)
URL: http://www.akky.mx
Whois TCP URI: whois.akky.mx
Whois Web URL: http://www.akky.mx/jsf/whois/whois.jsf

Registrant:
Name: Trafimar, S.A.
City: Ciudad de Mexico
State: Ciudad de Mexico
Country: Mexico

Administrative Contact:
Name: Trafimar, S.A
City: Ciudad de Mexico
State: Ciudad de Mexico
Country: Mexico

Technical Contact:
Name: Heriberto Vera Ceron
City: Ciudad de Mexico
State: Ciudad de Mexico
Country: Mexico

Billing Contact:
Name: Ivette Martinez
City: Ciudad de Mexico
State: Ciudad de Mexico
Country: Mexico

Name Servers:
DNS: ns1-04.azure-dns.com
DNS: ns2-04.azure-dns.net
DNS: ns3-04.azure-dns.org
DNS: ns4-04.azure-dns.info

DNSSEC DS Records:


% NOTICE: The expiration date displayed in this record is the date the
% registrar's sponsorship of the domain name registration in the registry is
% currently set to expire. This date does not necessarily reflect the
% expiration date of the domain name registrant's agreement with the sponsoring
% registrar. Users may consult the sponsoring registrar's Whois database to
% view the registrar's reported date of expiration for this registration.

% The requested information ("Information") is provided only for the delegation
% of domain names and the operation of the DNS administered by NIC Mexico.

% It is absolutely prohibited to use the Information for other purposes,
% including sending not requested emails for advertising or promoting products
% and services purposes (SPAM) without the authorization of the owners of the
% Information and NIC Mexico.

% The database generated from the delegation system is protected by the
% intellectual property laws and all international treaties on the matter.

% If you need more information on the records displayed here, please contact us
% by email at email .

% If you want notify the receipt of SPAM or unauthorized access, please send a
% email to email .

% NOTA: La fecha de expiracion mostrada en esta consulta es la fecha que el
% registrar tiene contratada para el nombre de dominio en el registry. Esta
% fecha no necesariamente refleja la fecha de expiracion del nombre de dominio
% que el registrante tiene contratada con el registrar. Puede consultar la base
% de datos de Whois del registrar para ver la fecha de expiracion reportada por
% el registrar para este nombre de dominio.

% La informacion que ha solicitado se provee exclusivamente para fines
% relacionados con la delegacion de nombres de dominio y la operacion del DNS
% administrado por NIC Mexico.

% Queda absolutamente prohibido su uso para otros propositos, incluyendo el
% envio de Correos Electronicos no solicitados con fines publicitarios o de
% promocion de productos y servicios (SPAM) sin mediar la autorizacion de los
% afectados y de NIC Mexico.

% La base de datos generada a partir del sistema de delegacion, esta protegida
% por las leyes de Propiedad Intelectual y todos los tratados internacionales
% sobre la materia.

% Si necesita mayor informacion sobre los registros aqui mostrados, favor de
% comunic*** a email.

% Si desea notificar sobre correo no solicitado o accesos no autorizados, favor
% de enviar su mensaje a email.
Last update was 125 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with trafimarrelo.com.mx in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

u92.com
4 secs
neginwp.ir
1 min
neginservice.ir
1 min
ngurdoto-shuttle.com
2 mins
negin2000.blogfa.com
2 mins
navakstore.ir
3 mins
secure.vantagefx.com
3 mins
88999.live
3 mins
nasaji.com
4 mins
impala-shuttles.com
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
trafimarrelo.com.mx widget