Tools & Wizards About Us
watch.ne.jp screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

watch.ne.jp

高級腕時計専門の修理工房 カナルクラブ

Page Load Speed

4.1 sec in total

First Response

602 ms

Resources Loaded

3.4 sec

Page Rendered

139 ms

watch.ne.jp screenshot

About Website

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

創業50年の老舗 高級時計専門の修理工房カナルクラブ。年間7000個の実績と信頼。【全国対応】ご来店・ご郵送もOK。全国からのご依頼多数。安心の一年保証・東京都御徒町上野5-25-1・JR御徒町駅より徒歩1分

Visit watch.ne.jp

Key Findings

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

Performance Metrics

watch.ne.jp performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value4,510 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.694

7/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

watch.ne.jp

602 ms

import.css

197 ms

ggg.css

330 ms

home.css

349 ms

style.css

326 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 94% of them (65 requests) were addressed to the original Watch.ne.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Watch.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 383.6 kB (43%)

Content Size

890.6 kB

After Optimization

507.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Watch.ne.jp main page is 890.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 679.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 12.1 kB

  • Original 15.7 kB
  • After minification 14.8 kB
  • After compression 3.6 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 12.1 kB or 77% of the original size.

Image Optimization

-37%

Potential reduce by 252.1 kB

  • Original 679.1 kB
  • After minification 427.0 kB

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. Obviously, Watch needs image optimization as it can save up to 252.1 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-59%

Potential reduce by 104.0 kB

  • Original 175.8 kB
  • After minification 172.8 kB
  • After compression 71.8 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 104.0 kB or 59% of the original size.

CSS Optimization

-77%

Potential reduce by 15.4 kB

  • Original 20.0 kB
  • After minification 15.7 kB
  • After compression 4.6 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.ne.jp needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (18%)

Requests Now

67

After Optimization

55

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

watch.ne.jp

watch.ne.jp

602 ms

import.css

import.css

197 ms

ggg.css

ggg.css

330 ms

home.css

home.css

349 ms

style.css

style.css

326 ms

jsapi

jsapi

20 ms

jquery.js

jquery.js

645 ms

yuga.js

yuga.js

370 ms

menu.js

menu.js

391 ms

swapimg.js

swapimg.js

494 ms

jquery.min.js

jquery.min.js

8 ms

reset-min.css

reset-min.css

301 ms

default.css

default.css

321 ms

common.css

common.css

362 ms

font.css

font.css

397 ms

header_bg.png

header_bg.png

388 ms

logo.gif

logo.gif

181 ms

tel.gif

tel.gif

189 ms

go_top.gif

go_top.gif

190 ms

go_kakaku.gif

go_kakaku.gif

167 ms

mainimg_bg.png

mainimg_bg.png

982 ms

mainimg.png

mainimg.png

930 ms

1.jpg

1.jpg

353 ms

company.jpg

company.jpg

363 ms

tokuteisyou.jpg

tokuteisyou.jpg

386 ms

kojinjyouhou.jpg

kojinjyouhou.jpg

526 ms

2.jpg

2.jpg

538 ms

baterry.jpg

baterry.jpg

582 ms

plastic.jpg

plastic.jpg

591 ms

galass.jpg

galass.jpg

698 ms

mojiban.jpg

mojiban.jpg

712 ms

bottom_ryuzu.jpg

bottom_ryuzu.jpg

776 ms

3.jpg

3.jpg

794 ms

maintenance.jpg

maintenance.jpg

869 ms

overhall.jpg

overhall.jpg

885 ms

polish.jpg

polish.jpg

969 ms

bousuitest.jpg

bousuitest.jpg

994 ms

4.jpg

4.jpg

1045 ms

belt_syuuri.jpg

belt_syuuri.jpg

1061 ms

blesslete.jpg

blesslete.jpg

1099 ms

hirsch.jpg

hirsch.jpg

1167 ms

5.jpg

5.jpg

1152 ms

otoiawase.jpg

otoiawase.jpg

1197 ms

muryoukonpou.jpg

muryoukonpou.jpg

1223 ms

container_bg.gif

container_bg.gif

1235 ms

top_catch.jpg

top_catch.jpg

1281 ms

rolex_price_top.png

rolex_price_top.png

1317 ms

omega_price_top.png

omega_price_top.png

1535 ms

maintenance_baner.jpg

maintenance_baner.jpg

1391 ms

parts_baner.jpg

parts_baner.jpg

1544 ms

ga.js

ga.js

13 ms

muryoconpo.jpg

muryoconpo.jpg

1537 ms

__utm.gif

__utm.gif

11 ms

ate1.jpg

ate1.jpg

1282 ms

hirsch.jpg

hirsch.jpg

1308 ms

links.jpg

links.jpg

1402 ms

go_kakaku2.gif

go_kakaku2.gif

200 ms

1_on.jpg

1_on.jpg

171 ms

2_on.jpg

2_on.jpg

174 ms

3_on.jpg

3_on.jpg

195 ms

4_on.jpg

4_on.jpg

174 ms

5_on.jpg

5_on.jpg

170 ms

maintenance_baner2.jpg

maintenance_baner2.jpg

334 ms

parts_baner2.jpg

parts_baner2.jpg

333 ms

muryoconpo2.jpg

muryoconpo2.jpg

336 ms

ate1_on.jpg

ate1_on.jpg

492 ms

hirsch2.jpg

hirsch2.jpg

380 ms

links2.jpg

links2.jpg

391 ms

go_top2.gif

go_top2.gif

497 ms

Accessibility Review

watch.ne.jp accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

watch.ne.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

watch.ne.jp SEO score

91

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watch.ne.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Watch.ne.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

watch.ne.jp

Open Graph description is not detected on the main page of Watch. 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: