Tools & Wizards About Us
fhb-watch.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

fhb-watch.com

FHB classic/スイスのクラシック・ヴィンテージ腕時計ブランド

Page Load Speed

4.9 sec in total

First Response

559 ms

Resources Loaded

3.9 sec

Page Rendered

423 ms

fhb-watch.com screenshot

About Website

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

FHB classicは、数多くのデザインから現代に相応しい形として復元したスイスのクラシック・ヴィンテージ腕時計ブランド。

Visit fhb-watch.com

Key Findings

We analyzed Fhb-watch.com page load time and found that the first response time was 559 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

fhb-watch.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,150 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

fhb-watch.com

559 ms

www.fhb-watch.com

570 ms

normalize.css

188 ms

foundation.css

519 ms

foundation-icons.css

352 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 92% of them (44 requests) were addressed to the original Fhb-watch.com, 4% (2 requests) were made to B92.yahoo.co.jp and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fhb-watch.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 372.3 kB (5%)

Content Size

8.1 MB

After Optimization

7.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fhb-watch.com main page is 8.1 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. 50% of websites need less resources to load. Images take 8.0 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 13.7 kB

  • Original 18.0 kB
  • After minification 16.7 kB
  • After compression 4.3 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 13.7 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 334.0 kB

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

JavaScript Optimization

-17%

Potential reduce by 15.3 kB

  • Original 90.9 kB
  • After minification 90.9 kB
  • After compression 75.6 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 15.3 kB or 17% of the original size.

CSS Optimization

-18%

Potential reduce by 9.2 kB

  • Original 52.4 kB
  • After minification 51.7 kB
  • After compression 43.2 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. Fhb-watch.com needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (40%)

Requests Now

42

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FHB 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 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fhb-watch.com

fhb-watch.com

559 ms

www.fhb-watch.com

www.fhb-watch.com

570 ms

normalize.css

normalize.css

188 ms

foundation.css

foundation.css

519 ms

foundation-icons.css

foundation-icons.css

352 ms

all.css

all.css

381 ms

ideal-image-slider.css

ideal-image-slider.css

376 ms

sld_t.css

sld_t.css

379 ms

lightslider.css

lightslider.css

386 ms

modernizr.js

modernizr.js

530 ms

jquery.js

jquery.js

754 ms

foundation.min.js

foundation.min.js

764 ms

jquery.inview.min.js

jquery.inview.min.js

566 ms

lightslider.js

lightslider.js

574 ms

top.js

top.js

688 ms

ideal-image-slider.js

ideal-image-slider.js

704 ms

iis-captions.js

iis-captions.js

751 ms

products.js

products.js

774 ms

scrollanime.js

scrollanime.js

856 ms

s_retargeting.js

s_retargeting.js

514 ms

s_retargeting.js

s_retargeting.js

718 ms

fhb_logo_sp.png

fhb_logo_sp.png

188 ms

fhb_logo.png

fhb_logo.png

192 ms

f903-yw01_th.jpg

f903-yw01_th.jpg

349 ms

new.jpg

new.jpg

188 ms

f903-swr-bk01_th.jpg

f903-swr-bk01_th.jpg

341 ms

f903-ywr-br01_th.jpg

f903-ywr-br01_th.jpg

557 ms

f903-sw01_th.jpg

f903-sw01_th.jpg

373 ms

f901-swr01_th.jpg

f901-swr01_th.jpg

374 ms

f901-swa01_th.jpg

f901-swa01_th.jpg

570 ms

top_media.jpg

top_media.jpg

846 ms

top_shop.jpg

top_shop.jpg

1044 ms

top_collection_03.jpg

top_collection_03.jpg

1309 ms

top_collection_sp_03.jpg

top_collection_sp_03.jpg

1158 ms

fhb_logo_bottom.png

fhb_logo_bottom.png

742 ms

gtm.js

gtm.js

19 ms

gtm.js

gtm.js

116 ms

top_f903_1600x900_02.jpg

top_f903_1600x900_02.jpg

1691 ms

top_f930_1600x900_02.jpg

top_f930_1600x900_02.jpg

1286 ms

top_f901_1600x900_02.jpg

top_f901_1600x900_02.jpg

1499 ms

previous.png

previous.png

1191 ms

next.png

next.png

1317 ms

top_f903_1200x1200_02.jpg

top_f903_1200x1200_02.jpg

1890 ms

top_f930_1200x1200_02.jpg

top_f930_1200x1200_02.jpg

1473 ms

top_f901_1200x1200_02.jpg

top_f901_1200x1200_02.jpg

1663 ms

foundation-icons.woff

foundation-icons.woff

1432 ms

fa-brands-400.woff

fa-brands-400.woff

1588 ms

controls.png

controls.png

1296 ms

Accessibility Review

fhb-watch.com accessibility score

90

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

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

Links do not have a discernible name

Best Practices

fhb-watch.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

fhb-watch.com 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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fhb-watch.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 Fhb-watch.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

fhb-watch.com

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