Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 70

    SEO

    Google-friendlier than
    29% of websites

kingsroad.jp

ブランド 時計 ゼットン

Page Load Speed

6.1 sec in total

First Response

532 ms

Resources Loaded

4.8 sec

Page Rendered

812 ms

kingsroad.jp screenshot

About Website

Visit kingsroad.jp now to see the best up-to-date Kingsroad content for Japan and also check out these interesting facts you probably never knew about kingsroad.jp

最安値を目指すブランド時計専門店 Zetton(ゼットン)|オメガ、パネライ、タグホイヤー

Visit kingsroad.jp

Key Findings

We analyzed Kingsroad.jp page load time and found that the first response time was 532 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

kingsroad.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value26.7 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value1.179

1/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

kingsroad.jp

532 ms

www.kingsroad.jp

1197 ms

sps_common.css

491 ms

default.css

503 ms

jquery.min.js

26 ms

Our browser made a total of 197 requests to load all elements on the main page. We found that 39% of them (76 requests) were addressed to the original Kingsroad.jp, 19% (38 requests) were made to Rakuten.ne.jp and 17% (33 requests) were made to Image1.shopserve.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Image1.shopserve.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 383.7 kB (7%)

Content Size

5.8 MB

After Optimization

5.4 MB

In fact, the total size of Kingsroad.jp main page is 5.8 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 274.1 kB

  • Original 311.3 kB
  • After minification 247.6 kB
  • After compression 37.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 63.7 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 274.1 kB or 88% of the original size.

Image Optimization

-1%

Potential reduce by 32.5 kB

  • Original 5.3 MB
  • After minification 5.2 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Kingsroad images are well optimized though.

JavaScript Optimization

-26%

Potential reduce by 49.8 kB

  • Original 189.8 kB
  • After minification 189.7 kB
  • After compression 140.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 49.8 kB or 26% of the original size.

CSS Optimization

-52%

Potential reduce by 27.2 kB

  • Original 52.7 kB
  • After minification 48.9 kB
  • After compression 25.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Kingsroad.jp needs all CSS files to be minified and compressed as it can save up to 27.2 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (36%)

Requests Now

194

After Optimization

124

The browser has sent 194 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kingsroad. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

kingsroad.jp accessibility score

66

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

kingsroad.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

kingsroad.jp SEO score

70

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kingsroad.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Kingsroad.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Kingsroad. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: