Amazon.cn - SEO Checker - Website Review

Your Website Score is

Similar Ranking

IDPAY | آیدی پی

idpay.ir

KÊNH THÔNG TIN KINH TẾ - TÀI CHÍNH VIỆT NAM

cafef.vn

FREE CLIP ART - CLIP ART COLLECTION - DOWNLOAD CLIPART ON CLIPART LIBRARY

clipart-library.com

MUBI: WATCH AND DISCOVER MOVIES

mubi.com

SIMPLENOTE

simplenote.com

МВД РОССИИ

xn--b1aew.xn--p1ai

سینماتیکت بزرگترین مرجع فروش بلیت سینما

cinematicket.org

Latest Sites

CASINO REVIEWS AND GAME BONUSES - JENNYCASINO.COM

jennycasino.com

AMAZON.COM

amazon.com

powerofdream.co.id

BITMINEROPTIONS

bitmineroptions.com

欢迎访问本网站

gtr.com

OMEGAPRO FOREX

omegaprofx.com

LUXCITI : TIENDA ONLINE DE PRODUCTOS DE PELUQUERÍA, COMPRAS ONLINE ESPAÑA

luxciti.es

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

41 amazon.cn Last Updated: 1 year

Success 47% of passed verification steps

Warning 15% of total warning

Errors 38% of total errors, require fast action

Mobile

Performance Desktop Score 63%

Best Practices Desktop Score 69%

SEO Desktop Score 82%

Progressive Web App Desktop Score 19%

Performance Mobile Score 48%

Best Practices Mobile Score 69%

SEO Mobile Score 91%

Progressive Web App Mobile Score 59%

Page Authority Authority 64%

Domain Authority Domain Authority 84%

Moz Rank 6.4/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 23 Characters

亚马逊-网上购物商城：要网购, 就来Z.CN!

Meta Description 137 Characters

亚马逊中国（z.cn）坚持“以客户为中心”的理念，秉承“天天低价，正品行货”信念，销售图书、电脑、数码家电、母婴百货、服饰箱包等上千万种产品。亚马逊中国提供专业服务：正品行货天天低价，机打发票全国联保。货到付款，30天内可退换货。亚马逊为中国消费者提供便利、快捷的网购体验。

Effective URL 21 Characters

https://www.amazon.cn

Excerpt Page content

亚马逊-网上购物商城：要网购, 就来Z.cn! ...

Meta Keywords 14 Detected

网购网上购物在线购物网购网站网购商城购物网站网购中心购物中心卓越亚马逊卓越亚马逊亚马逊中国 joyo amazon

Keywords Cloud Density

amazon2 全球开店2 您最近查看的商品和相关推荐2 查看或编辑你的浏览历史记录2 浏览产品详情页后2 点击此处即可轻松返回您感兴趣的页面2 镇店之宝2 全部分类2 增值电信业务经营许可证1 公益社区1

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
amazon	2
全球开店	2
您最近查看的商品和相关推荐	2
查看或编辑你的浏览历史记录	2
浏览产品详情页后	2
点击此处即可轻松返回您感兴趣的页面	2
镇店之宝	2
全部分类	2
增值电信业务经营许可证	1
公益社区	1

Google Preview Your look like this in google search result

亚马逊-网上购物商城：要网购, 就来Z.CN!

https://www.amazon.cn

Robots.txt File Detected

http://amazon.cn/robots.txt

Sitemap.xml File No Found

http://amazon.cn/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: 1970-01-01 / 51 years

Create on: 1970-01-01 / 51 years

Expires on: 1970-01-01 / 621 months 14 days

Nameservers

pdns1.ultradns.net

pdns3.ultradns.org

ns1.p31.dynect.net

ns1.dynect.cn

ns1.dynect.net.cn

ns2.p31.dynect.net

Page Size Code & Text Ratio

Document Size: ~798.1 KB

Code Size: ~746.4 KB

Text Size: ~51.69 KB Ratio: 6.48%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.8 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 50 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

Remove unused CSS Potential savings of 70 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 613 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

Reduce server response times (TTFB) Root document took 2,380 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 40 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 277 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 100 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 430 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.5 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

Defer offscreen images Potential savings of 1,690 KB

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

Properly size images Potential savings of 1,095 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 4.0 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 1.9 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,438 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 4.1 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 3,841 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 0.9 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 244 requests • 4,438 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 17 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 360 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 3.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

Mobile

Total Blocking Time 980 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 3.4 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

Defer offscreen images Potential savings of 687 KB

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

Properly size images Potential savings of 214 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 8.4 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 6.3 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 3,727 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 9.1 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.2 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 5 chains found

Avoid an excessive DOM size 1,149 elements

Minify JavaScript Potential savings of 3 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 2.2 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 196 requests • 3,727 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Use video formats for animated content Potential savings of 349 KB

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

Serve static assets with an efficient cache policy 23 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 550 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 9.2 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) 4860 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 180 ms

Tap targets are not sized appropriately 99% 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 69.38% 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 29 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 550 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

Reduce server response times (TTFB) Root document took 1,380 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 211 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 1,730 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

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

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 200 OK
Server: Server
Date: Wed, 25 Dec 2019 11:02:19 GMT
Content-Type: text/html
Content-Length: 2294
Connection: keep-alive
Vary: Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
Content-Encoding: gzip
x-amz-rid: 2BWFEPAVM93941XD3R6V
Edge-Control: no-store

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	amazon.cn	54.222.60.218	IN	899
NS	amazon.cn	ns1.dynect.net.cn	IN	14029
NS	amazon.cn	ns2.dynect.net.cn	IN	14029
NS	amazon.cn	ns2.dynect.cn	IN	14029
NS	amazon.cn	ns1.dynect.cn	IN	14029
NS	amazon.cn	ns3.p31.dynect.net	IN	14029
NS	amazon.cn	ns2.p31.dynect.net	IN	14029
NS	amazon.cn	ns1.p31.dynect.net	IN	14029
NS	amazon.cn	u5.amazon.cn	IN	14029
NS	amazon.cn	ns4.p31.dynect.net	IN	14029
NS	amazon.cn	u2.amazon.com	IN	14029
MX	amazon.cn	amazon-smtp.amazon.com	IN	900
TXT	amazon.cn	v=spf1 include:amazon.com -all	IN	900
TXT	amazon.cn	spf2.0/pra include:amazon.com -all	IN	900

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

41 amazon.cn Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments