Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

watch-rescue.com

時計修理専門店ウォッチレスキュー | 腕時計の修理・電池交換・買取り、ヴィンテージウォッチの販売ならウォッチレスキュー

Page Load Speed

10.7 sec in total

First Response

1.6 sec

Resources Loaded

6.5 sec

Page Rendered

2.6 sec

About Website

Click here to check amazing Watch Rescue content for Japan. Otherwise, check out these important facts you probably never knew about watch-rescue.com

腕時計の修理・電池交換からオメガやロレックスなどブランド時計のオーバーホール、金属ベルトの調整や革ベルトの交換など、時計の事なら時計修理専門店ウォッチ​レスキューへおまかせください。ヴィンテージウォッチ・アンティークウォッチの販売も行っております。

Visit watch-rescue.com

Key Findings

We analyzed Watch-rescue.com page load time and found that the first response time was 1.6 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

watch-rescue.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

watch-rescue.com

1597 ms

sbi-styles.min.css

382 ms

swiper.css

576 ms

style.min.css

889 ms

swell-icons.css

711 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 69% of them (50 requests) were addressed to the original Watch-rescue.com, 25% (18 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Watch-rescue.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.9 kB (6%)

Content Size

2.4 MB

After Optimization

2.3 MB

In fact, the total size of Watch-rescue.com main page is 2.4 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 149.3 kB

  • Original 177.0 kB
  • After minification 173.8 kB
  • After compression 27.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 149.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 667 B

  • Original 1.9 MB
  • After minification 1.9 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. Watch Rescue images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.2 kB

  • Original 304.4 kB
  • After minification 304.4 kB
  • After compression 303.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 766 B

  • Original 66.9 kB
  • After minification 66.7 kB
  • After compression 66.1 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. Watch-rescue.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (54%)

Requests Now

70

After Optimization

32

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

Accessibility Review

watch-rescue.com accessibility score

89

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

Links do not have a discernible name

Best Practices

watch-rescue.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

watch-rescue.com SEO score

84

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 uses 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 Watch-rescue.com 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 Watch-rescue.com 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 data is detected on the main page of Watch Rescue. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: