Amazon.co.jp - SEO Checker

Your Website Score is

Similar Ranking

ON24: THE DIGITAL EXPERIENCE PLATFORM TO CREATE EXPERIENCES YOUR AUDIENCES DEMAND.

on24.com

RTL.HR - SVE NAJVAŽNIJE VIJESTI NA JEDNOM MJESTU - RTL

rtl.hr

HOMEPAGE | USCIS

uscis.gov

JD.COM, INC.

jd.com

BEST BUY: SHOP ONLINE FOR DEALS & SAVE | BEST BUY CANADA

bestbuy.ca

IT세상을 바꾸는 힘 지디넷코리아

zdnet.co.kr

WIKIPEDIA

wikipedia.org

Latest Sites

PORTSTONE PARTNERS LIMITED

portstonepartnersltd.com

VENICTRADE.COM

venictrade.com

COINLUNO.COM

coinluno.com

SIGNCURRENCY.COM

signcurrency.com

ALLTRADESFX.COM

alltradesfx.com

MODERN KITCHENS | READIKIT | HOME PAGE

readikit.com

av4.xyz

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

59 amazon.co.jp Last Updated: 10 months

Success 62% of passed verification steps

Warning 15% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 88%

Best Practices Desktop Score 77%

SEO Desktop Score 91%

Progressive Web App Desktop Score 19%

Performance Mobile Score 60%

Best Practices Mobile Score 77%

SEO Mobile Score 99%

Progressive Web App Mobile Score 30%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Charset Encoding

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

Title Tag 35 Characters

AMAZON | 本, ファッション, 家電から食品まで | アマゾン

Meta Description 103 Characters

Amazon.co.jp 公式サイト。お急ぎ便ご利用で当日・翌日にお届け。アマゾンで本, 日用品, ファッション, 食品, ベビー用品, カー用品ほか一億種の商品をいつでもお安く。通常配送無料(一部を除く)

Effective URL 24 Characters

https://www.amazon.co.jp

Excerpt Page content

Amazon | 本, ファッション, 家電から食品まで | アマゾンメインコンテンツにスキップ ...

Meta Keywords 4 Detected

Amazon アマゾン通販インターネットショッピング

Keywords Cloud Density

詳しくはこちら14 amazon9 その他を表示7 ファッション3 クリスマスギフト20193 パソコン3 ここに履歴が表示されます2 チェックした商品詳細ページに簡単に戻る事が出来ます2 ギフト券2 amazonで売る2

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

Keyword	Freq	Title	Desc	Domain	H1	H2
詳しくはこちら	14
amazon	9
その他を表示	7
ファッション	3
クリスマスギフト2019	3
パソコン	3
ここに履歴が表示されます	2
チェックした商品詳細ページに簡単に戻る事...	2
ギフト券	2
amazonで売る	2

Google Preview Your look like this in google search result

AMAZON | 本, ファッション, 家電から食品まで | アマゾン

https://www.amazon.co.jp

Robots.txt File Detected

http://amazon.co.jp/robots.txt

Sitemap.xml File Detected

http://amazon.co.jp/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~443.03 KB

Code Size: ~414.06 KB

Text Size: ~28.97 KB Ratio: 6.54%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

Amazon Cloudfront

CDN

PWA - Manifest

Manifest is not valid

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

Desktop

Uses efficient cache policy on static assets 13 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 16.3 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

Remove unused CSS Potential savings of 68 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 603 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 470 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 263 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 10 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 1.0 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 153 KB

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

Speed Index 2.1 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,683 KB

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

Minimize main-thread work 2.2 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 3 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,691 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 17 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 350 requests • 4,683 KB

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

Mobile

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,184 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 130 KB

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

Speed Index 3.7 s

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

First CPU Idle 6.1 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,190 KB

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

Minimize main-thread work 6.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.3 s

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

Avoid chaining critical requests 5 chains found

Avoids an excessive DOM size 620 elements

First Meaningful Paint 2.5 s

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

Keep request counts low and transfer sizes small 195 requests • 3,190 KB

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

Uses efficient cache policy on static assets 18 resources found

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

Max Potential First Input Delay 240 ms

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

Time to Interactive 11.4 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 at 11.4 s

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

Estimated Input Latency 50 ms

First Contentful Paint (3G) 5160 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are not sized appropriately 96% 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 95.95% 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 766 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 530 ms

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

Efficiently encode images Potential savings of 320 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 510 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 250 ms

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

Reduce JavaScript execution time 2.7 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

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 405 Method Not Allowed
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Server: Server
Date: Sun, 22 Dec 2019 20:05:54 GMT
Set-Cookie: skin=noskin; path=/; domain=.amazon.co.jp
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: MW7C9286W4JZQ3N59V6V
X-Frame-Options: SAMEORIGIN
X-Cache: Error from cloudfront
Via: 1.1 bad43b7a5f64a218c0ba43b47a8d182f.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: IAD79-C1
X-Amz-Cf-Id: bXNmSMKSrNAxtd4JuJkGxJDdtcT1QdLCVQkfVUT72f1HTBcLBzzUxQ==

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	amazon.co.jp	52.119.164.121	IN	59
A	amazon.co.jp	52.119.168.48	IN	59
A	amazon.co.jp	52.119.161.5	IN	59
NS	amazon.co.jp	ns3.p31.dynect.net	IN	86400
NS	amazon.co.jp	pdns4.ultradns.org	IN	86400
NS	amazon.co.jp	ns2.p31.dynect.net	IN	86400
NS	amazon.co.jp	pdns1.ultradns.net	IN	86400
NS	amazon.co.jp	pdns3.ultradns.org	IN	86400
NS	amazon.co.jp	pdns6.ultradns.co.uk	IN	86400
NS	amazon.co.jp	pdns5.ultradns.info	IN	86400
NS	amazon.co.jp	ns4.p31.dynect.net	IN	86400
NS	amazon.co.jp	pdns2.ultradns.net	IN	86400
NS	amazon.co.jp	ns1.p31.dynect.net	IN	86400
MX	amazon.co.jp	amazon-smtp.amazon.com	IN	7200
TXT	amazon.co.jp	facebook-domain-verification=q0vtskklb65bdw766sy92dffo95y08	IN	3600
TXT	amazon.co.jp	v=spf1 include:amazon.com include:spf-bma.mpme.jp include:amazon-spf.mrs.mpub.ne.jp -all	IN	3600
TXT	amazon.co.jp	adobe-idp-site-verification=b6bcd3e5aaffc63607c8bf75744d9a0d1febc50dd7f389428e2ae476c9ba8814	IN	3600
TXT	amazon.co.jp	spf2.0/pra include:amazon.com include:spf-bma.mpme.jp include:amazon-spf.mrs.mpub.ne.jp -all	IN	3600

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

59 amazon.co.jp Last Updated: 10 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Amazon Cloudfront

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments