Tools & Wizards About Us
vanhoutteghem.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 0

    Best Practices

  • 92

    SEO

    Google-friendlier than
    75% of websites

vanhoutteghem.com

Juwelier Vanhoutteghem | horloges en juwelen van topmerken | OMEGA - Breitling - Zenith

Page Load Speed

4.1 sec in total

First Response

672 ms

Resources Loaded

2.8 sec

Page Rendered

679 ms

vanhoutteghem.com screenshot

About Website

Welcome to vanhoutteghem.com homepage info - get ready to check Vanhoutteghem best content right away, or after learning these important things about vanhoutteghem.com

Juwelier Vanhoutteghem Gent is officiële verdeler van exclusieve merken waaronder OMEGA, Breitling, Zenith, TAG Heuer, Baume & Mercier, Hermès, Montblanc, Marco Bicego, Messika. Ontdek ons ruim assort...

Visit vanhoutteghem.com

Key Findings

We analyzed Vanhoutteghem.com page load time and found that the first response time was 672 ms and then it took 3.4 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

vanhoutteghem.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.214

58/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

vanhoutteghem.com

672 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

97 ms

css_JoYP3SyEFWEMl4HgoN3y8m7tsdG7OJhA4tzrebCC8bs.css

163 ms

css_qQkEXJwFxCy_6l1GYQlqn6UQNM2wbv9yfXqODXohz3A.css

180 ms

css_Uxop_srdsZonMX8Oh4b-Q4BW_Ck5HM0-PiEF18oqvZY.css

269 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 70% of them (26 requests) were addressed to the original Vanhoutteghem.com, 8% (3 requests) were made to and 5% (2 requests) were made to Use.typekit.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Vanhoutteghem.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.3 kB (30%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 21.3 kB

  • Original 28.6 kB
  • After minification 26.8 kB
  • After compression 7.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 21.3 kB or 75% of the original size.

Image Optimization

-15%

Potential reduce by 228.1 kB

  • Original 1.5 MB
  • After minification 1.3 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. Obviously, Vanhoutteghem needs image optimization as it can save up to 228.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-76%

Potential reduce by 136.5 kB

  • Original 179.4 kB
  • After minification 127.6 kB
  • After compression 42.9 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 136.5 kB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 179.4 kB

  • Original 211.6 kB
  • After minification 207.5 kB
  • After compression 32.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. Vanhoutteghem.com needs all CSS files to be minified and compressed as it can save up to 179.4 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

19

  • Images
  • JavaScript
  • CSS

The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vanhoutteghem. 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

vanhoutteghem.com

vanhoutteghem.com

672 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

97 ms

css_JoYP3SyEFWEMl4HgoN3y8m7tsdG7OJhA4tzrebCC8bs.css

css_JoYP3SyEFWEMl4HgoN3y8m7tsdG7OJhA4tzrebCC8bs.css

163 ms

css_qQkEXJwFxCy_6l1GYQlqn6UQNM2wbv9yfXqODXohz3A.css

css_qQkEXJwFxCy_6l1GYQlqn6UQNM2wbv9yfXqODXohz3A.css

180 ms

css_Uxop_srdsZonMX8Oh4b-Q4BW_Ck5HM0-PiEF18oqvZY.css

css_Uxop_srdsZonMX8Oh4b-Q4BW_Ck5HM0-PiEF18oqvZY.css

269 ms

css_pWEj4m7SsCVUGXebNsjZAoAxL9_4bzj_uH_qHO4dY_8.css

css_pWEj4m7SsCVUGXebNsjZAoAxL9_4bzj_uH_qHO4dY_8.css

186 ms

css

css

24 ms

jquery.min.js

jquery.min.js

5 ms

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js

186 ms

js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js

js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js

189 ms

js_mni7heuOHtGV3jBNUCVTHOGYbsQqEXyG0BGK4MMRvyA.js

js_mni7heuOHtGV3jBNUCVTHOGYbsQqEXyG0BGK4MMRvyA.js

321 ms

kbq4bhr.js

kbq4bhr.js

154 ms

js_m8wJ6mvdP0liDcbBmqLpo1EvLIqBTYUpwxnZcKIkVPw.js

js_m8wJ6mvdP0liDcbBmqLpo1EvLIqBTYUpwxnZcKIkVPw.js

264 ms

analytics.js

analytics.js

8 ms

d

d

399 ms

collect

collect

12 ms

frame1.png

frame1.png

853 ms

pattern.png

pattern.png

92 ms

logo_white.png

logo_white.png

186 ms

scroll_down.png

scroll_down.png

95 ms

logo.png

logo.png

162 ms

10551056_739224686149626_206090378196170371_n_2.jpg

10551056_739224686149626_206090378196170371_n_2.jpg

175 ms

_INK4495.jpg

_INK4495.jpg

1240 ms

banner-5.jpg

banner-5.jpg

370 ms

banner-6.jpg

banner-6.jpg

400 ms

2_1.jpg

2_1.jpg

349 ms

CO_Globemaster_VueFuite_1600x900.jpg

CO_Globemaster_VueFuite_1600x900.jpg

647 ms

tipsparels.jpg

tipsparels.jpg

437 ms

asset-version-ee570b79a1-emergency-ii-black.jpg

asset-version-ee570b79a1-emergency-ii-black.jpg

462 ms

globemaster.jpg

globemaster.jpg

480 ms

test.jpg

test.jpg

524 ms

0sivwNkKpWH

0sivwNkKpWH

8 ms

ChW7PAAAA

ChW7PAAAA

7 ms

KT3KS9Aol4WfR6Vas8kNcg.woff

KT3KS9Aol4WfR6Vas8kNcg.woff

27 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

645 ms

3vstc9+Bxx0yGFHwvs45rgTTjrltDPOOue8Cy665LIrrspwzXU33HTLbZnuuOteeGMPPPTIY088lSXbMzmeeyHXS3leeS3fG2+9894HBT765PNvwoVuzwAAAA==

3vstc9+Bxx0yGFHwvs45rgTTjrltDPOOue8Cy665LIrrspwzXU33HTLbZnuuOteeGMPPPTIY088lSXbMzmeeyHXS3leeS3fG2+9894HBT765PNvwoVuzwAAAA==

5 ms

p.gif

p.gif

128 ms

Accessibility Review

vanhoutteghem.com accessibility score

81

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 input fields do not have accessible names

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

vanhoutteghem.com SEO score

92

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vanhoutteghem.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Vanhoutteghem.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

vanhoutteghem.com

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