Your Website Score is

Similar Ranking

87
.NET |---. CROSS-PLATFORM. OPEN SOURCE.
windows.net
87
CCM - ONLINE COMMUNITY
ccm.net
87
GOOGLE
google.fi
87
東洋経済オンライン | 経済ニュースの新基準
toyokeizai.net
87
店铺浏览-淘宝网
janeeyre.tmall.com
87
COMO CRIAR UM SITE GRÁTIS | DESCUBRA COMO CRIAR UM SITE GRÁTIS - WEBNODE
webnode.com.br
87
WELCOME TO PYTHON.ORG
python.org

Latest Sites

24
THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ
noithatmanhhe.vn
19
SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP
nhacanhothongminh.com
16
CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM
crypto-mining.biz
57
99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING
999dice.com
19
RELANDICE BOT FOR 999DICE
relandice.com
23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.com

Top Technologies

Nginx
Web Servers
PHP
Programming Languages
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
jQuery
JavaScript Frameworks
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

87 amazon.com.mx Last Updated: 10 months

Success 47% of passed verification steps
Warning 30% of total warning
Errors 23% of total errors, require fast action
Share

Desktop

Mobile

Performance Desktop Score 91%
Best Practices Desktop Score 77%
SEO Desktop Score 82%
Progressive Web App Desktop Score 19%
Performance Mobile Score 74%
Best Practices Mobile Score 77%
SEO Mobile Score 100%
Progressive Web App Mobile Score 56%
Page Authority Authority 54%
Domain Authority Domain Authority 89%
Moz Rank 5.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 67 Characters
AMAZON.COM.MX: PRECIOS BAJOS - ENVÍO RÁPIDO - MILLONES DE PRODUCTOS
Meta Description 175 Characters
Envío gratis en pedidos elegibles. Pagos fáciles y seguros. Compra ahora electrónicos, libros, ropa y mucho más. Devoluciones fáciles. Inicia tu prueba de Amazon Prime gratis.
Effective URL 25 Characters
https://www.amazon.com.mx
Excerpt Page content
Amazon.com.mx: Precios bajos - Envío rápido - Millones de productos Saltar al contenido principal ...
Meta Keywords 17 Detected
Amazon Amazon.com.mx eBooks Kindle Kindle ebooks libros electronicos Kindle libros electronicos compras por Internet compras en linea amazon méxico hogar cocina bebé herramientas belleza relojes deportes y aire libre
Keywords Cloud Density
amazon12 productos10 para10 nuevos6 prime5 vendidos5 páginas4 todos4 videojuegos4 descubre4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
amazon 12
productos 10
para 10
nuevos 6
prime 5
vendidos 5
páginas 4
todos 4
videojuegos 4
descubre 4
Google Preview Your look like this in google search result
AMAZON.COM.MX: PRECIOS BAJOS - ENVÍO RÁPIDO - MILLONES DE PR
https://www.amazon.com.mx
Envío gratis en pedidos elegibles. Pagos fáciles y seguros. Compra ahora electrónicos, libros, ropa y mucho más. Devoluciones fáciles. Inicia tu prueb
Robots.txt File Detected
http://amazon.com.mx/robots.txt
Sitemap.xml File No Found
http://amazon.com.mx/sitemap.xml
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2019-05-09 / 1 year
Create on: 1997-10-29 / 23 years
Expires on: 2024-10-28 / 49 months 27 days

MarkMonitor ,United States United States United States United States

Amazon Technologies, Inc. Amazon Technologies, Inc. Amazon Technologies, Inc. Amazon Technologies, Inc.

Nameservers
pdns1.ultradns.net
pdns3.ultradns.org
ns2.p31.dynect.net
pdns6.ultradns.co.uk
ns1.p31.dynect.net
Page Size Code & Text Ratio
Document Size: ~378.69 KB
Code Size: ~351.43 KB
Text Size: ~27.26 KB Ratio: 7.20%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Remove unused CSS Potential savings of 69 KB
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
Serve images in next-gen formats Potential savings of 593 KB
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
Server response times are low (TTFB) Root document took 260 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 88 KB
Optimized images load faster and consume less cellular data
Minimize third-party usage Third-party code blocked the main thread for 0 ms
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Properly size images Potential savings of 52 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.9 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 0.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoid enormous network payloads Total size was 4,462 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 5 chains found
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
Avoid an excessive DOM size 1,512 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)
Minify JavaScript Potential savings of 4 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 357 requests • 4,462 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 18 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 0.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 11.6 s
A fast page load over a cellular network ensures a good mobile user experience
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

Mobile

Mobile Screenshot
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements
Document uses legible font sizes 93.99% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Remove unused CSS Potential savings of 41 KB
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
Serve images in next-gen formats Potential savings of 1,029 KB
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
Server response times are low (TTFB) Root document took 440 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 209 KB
Optimized images load faster and consume less cellular data
Reduce the impact of third-party code Third-party code blocked the main thread for 300 ms
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
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 1.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 164 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Properly size images Potential savings of 329 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 5.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoid enormous network payloads Total size was 2,775 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.6 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 6 chains found
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
Avoids an excessive DOM size 411 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)
First Meaningful Paint 2.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 165 requests • 2,775 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 11 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 180 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 6.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
First Contentful Paint (3G) 5760 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 20 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/1.1 405 Method Not Allowed
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Server: Server
Date: Tue, 26 Nov 2019 14:55:09 GMT
Strict-Transport-Security: max-age=47474747; includeSubDomains; preload
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Vary: Accept-Encoding,User-Agent,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment
x-amz-rid: T0JGN2TSPM59FPG8VRZM
X-Frame-Options: SAMEORIGIN
X-Cache: Error from cloudfront
Via: 1.1 613fc2ce2843d97a87bffbdb759c82a5.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: ORD52-C1
X-Amz-Cf-Id: Ct_rVgX76SItFM0QtRA2u7dr4H4BoSN_ypUbTmjEn_Ytbm3wxcomxA==
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A amazon.com.mx 52.94.239.35 IN 15
A amazon.com.mx 54.239.18.174 IN 15
A amazon.com.mx 52.94.225.241 IN 15
NS amazon.com.mx pdns1.ultradns.net IN 21599
NS amazon.com.mx pdns6.ultradns.co.uk IN 21599
NS amazon.com.mx pdns5.ultradns.info IN 21599
NS amazon.com.mx ns1.p31.dynect.net IN 21599
NS amazon.com.mx ns2.p31.dynect.net IN 21599
NS amazon.com.mx ns4.p31.dynect.net IN 21599
NS amazon.com.mx pdns3.ultradns.org IN 21599
NS amazon.com.mx pdns2.ultradns.net IN 21599
NS amazon.com.mx pdns4.ultradns.org IN 21599
NS amazon.com.mx ns3.p31.dynect.net IN 21599
MX amazon.com.mx amazon-smtp.amazon.com IN 899
TXT amazon.com.mx v=spf1 include:amazon.com -all IN 59
TXT amazon.com.mx spf2.0/pra include:amazon.com -all IN 59
TXT amazon.com.mx facebook-domain-verification=bg0rl60171p30byuyib2ljig5h19uz IN 59

Comments

Copyright © 2019 Check.web.id | Privacy Policy | Terms and Conditions
Languages | Bahasa Deutsch English Español Français Nederlands Português Pусский
Add extension to Chrome