Your Website Score is

Similar Ranking

92
BING
bing.com
92
NASA
nasa.gov
92
FILE SHARING AND STORAGE MADE SIMPLE
mediafire.com
92
ATTENTION REQUIRED! | CLOUDFLARE
namecheap.com
92
SAMSUNG CANADA | MOBILE | TV | HOME APPLIANCES
samsung.com
92
OFFICE 365 LOGIN | MICROSOFT OFFICE
office.com

Latest Sites

24
SPÉCIALISTE DE LA TRANSFORMATION DIGITALE INNOVANTE
agencedigitale-allianced8.com
19
PLAYSTATION 5 ONLINE STORE | BEST PLAYSTATION
best-playstation.com
19
NEWSONHY TECH NEWS MOVIES BLOGGING TOOLS GUEST POST MOBILES PACKAGE
newsonhy.online
31
HOME | CURRENCY CLAN |YOUR CURRENCY BUDDY
currencyclan.com
3
MILLIONS OF SEO BACKLINKS - 1 BILLION LINKS
1billionlinks.com
58
MUSLIM.OR.ID - MEMURNIKAN AQIDAH MENEBARKAN SUNNAH
muslim.or.id
19
MOVIEXFILM | FILMS FULL HD | WATCH MOVIES ONLINE
moviexfilm.com

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
CloudFlare
CDN
Nginx
Web Servers
Font Awesome
Font Scripts
Google Tag Manager
Tag Managers
Apache
Web Servers
LiteSpeed
Web Servers

92 amazon.co.jp Last Updated: 8 months

Success 70% of passed verification steps
Warning 15% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 77%
Best Practices Desktop Score 79%
SEO Desktop Score 75%
Progressive Web App Desktop Score 19%
Performance Mobile Score 59%
Best Practices Mobile Score 79%
SEO Mobile Score 99%
Progressive Web App Mobile Score 54%
Page Authority Authority 72%
Domain Authority Domain Authority 94%
Moz Rank 7.2/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 35 Characters
AMAZON | 本, ファッション, 家電から食品まで | アマゾン
Meta Description 85 Characters
Amazon.co.jp 公式サイト。アマゾンで本, 日用品, ファッション, 食品, ベビー用品, カー用品ほか一億種の商品をいつでもお安く。通常配送無料(一部を除く)
Effective URL 24 Characters
https://www.amazon.co.jp
Excerpt Page content
Amazon | 本, ファッション, 家電から食品まで | アマゾン ...
Keywords Cloud Density
prime40 dayセール36 もっと見る9 今すぐチェック8 amazon8 セール会場へ8 終了まで6 パソコン4 プライムデー3 ケース品3
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
prime 40
dayセール 36
もっと見る 9
今すぐチェック 8
amazon 8
セール会場へ 8
終了まで 6
パソコン 4
プライムデー 3
ケース品 3
Google Preview Your look like this in google search result
AMAZON | 本, ファッション, 家電から食品まで | アマゾン
https://www.amazon.co.jp
Amazon.co.jp 公式サイト。アマゾンで本, 日用品, ファッション, 食品, ベビー用品, カー用品ほか一億種の商品をいつでもお安く。通常配送無料(一部を除く)
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~579.94 KB
Code Size: ~578.39 KB
Text Size: ~1.55 KB Ratio: 0.27%

Social Data

Delicious Total: 0
Facebook Total: 341,602
Google Total: 0
Linkedin Total: 0
Pinterest Total: 0
Stumbleupon Total: 0
Tumblr Total: 0
Vk Total: 0

Estimation Traffic and Earnings

2,174,920
Unique Visits
Daily
4,023,602
Pages Views
Daily
$7,764
Income
Daily
60,897,760
Unique Visits
Monthly
114,672,657
Pages Views
Monthly
$194,100
Income
Monthly
704,674,080
Unique Visits
Yearly
1,351,930,272
Pages Views
Yearly
$2,049,696
Income
Yearly

Desktop

Desktop Screenshot
Estimated Input Latency 30 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
Keep request counts low and transfer sizes small 279 requests • 4,283 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minify JavaScript Potential savings of 9 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Largest Contentful Paint 2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Remove unused JavaScript Potential savings of 140 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Properly size images Potential savings of 65 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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 17.2 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid serving legacy JavaScript to modern browsers Potential savings of 10 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid enormous network payloads Total size was 4,283 KiB
Large network payloads cost users real money and are highly correlated with long load times
Efficiently encode images Potential savings of 178 KiB
Optimized images load faster and consume less cellular data
Serve images in next-gen formats Potential savings of 373 KiB
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 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
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
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
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 62 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short Root document took 540 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid an excessive DOM size 3,616 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)
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Cumulative Layout Shift 0.056
Cumulative Layout Shift measures the movement of visible elements within the viewport
Time to Interactive 3.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Speed Index 2.3 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/).
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Defer offscreen images Potential savings of 857 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Remove unused CSS Potential savings of 81 KiB
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
Reduce JavaScript execution time 1.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Mobile

Mobile Screenshot
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
Total Blocking Time 280 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First CPU Idle 4.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/).
Time to Interactive 9.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid serving legacy JavaScript to modern browsers Potential savings of 10 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Remove unused JavaScript Potential savings of 90 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Avoids enormous network payloads Total size was 1,230 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 5.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Efficiently encode images Potential savings of 30 KiB
Optimized images load faster and consume less cellular data
Properly size images Potential savings of 66 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Document uses legible font sizes 99.69% 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
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce JavaScript execution time 2.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Estimated Input Latency 60 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
Initial server response time was short Root document took 480 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce the impact of third-party code Third-party code blocked the main thread for 860 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
Remove unused CSS Potential savings of 50 KiB
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
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Defer offscreen images Potential savings of 157 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoids an excessive DOM size 675 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)
Max Potential First Input Delay 460 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid long main-thread tasks 12 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 73 KiB
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
Largest Contentful Paint 10.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Avoid chaining critical requests 7 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
Uses efficient cache policy on static assets 13 resources found
A long cache lifetime can speed up repeat visits to your page
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
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
Keep request counts low and transfer sizes small 167 requests • 1,230 KiB
To set budgets for the quantity and size of page resources, add a budget.json file

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Congratulations! Your Domain Authority is good
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

46

Global Rank

4

Japan
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 405 
content-type: text/html;charset=UTF-8
content-length: 0
server: Server
date: Tue, 13 Oct 2020 12:42:22 GMT
x-amz-rid: Y64M64NMDBW0C2FTSBTA
set-cookie: skin=noskin; path=/; domain=.amazon.co.jp
cache-control: no-cache
pragma: no-cache
expires: -1
vary: Accept-Encoding,User-Agent,Content-Type,Accept-Encoding,X-Amzn-CDN-Cache,X-Amzn-AX-Treatment,User-Agent
strict-transport-security: max-age=47474747; includeSubDomains; preload
x-frame-options: SAMEORIGIN
x-cache: Error from cloudfront
via: 1.1 71b90b61d58fd2a84fb0ad4ce0fc268c.cloudfront.net (CloudFront)
x-amz-cf-pop: YTO50-C3
x-amz-cf-id: 3GIj9wIBRtI71yCggji-VB3gLrJrev18WPTZUwXUAYOmUzzRvypWZg==
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments