Tools & Wizards About Us
vintageheuer.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

vintageheuer.com

Page Load Speed

6.3 sec in total

First Response

530 ms

Resources Loaded

3.6 sec

Page Rendered

2.1 sec

vintageheuer.com screenshot

About Website

Click here to check amazing Vintageheuer content. Otherwise, check out these important facts you probably never knew about vintageheuer.com

We celebrate masterpieces from the golden years of Heuer and fine examples of wristwatches from some of the most prestigious watchmakers in the world.

Visit vintageheuer.com

Key Findings

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

vintageheuer.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value18,420 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value26.3 s

0/100

10%

Network Requests Diagram

www.vintageheuer.com

530 ms

font-awesome.min.css

152 ms

css

191 ms

toolset-common-es.css

63 ms

style.css

85 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 82% of them (65 requests) were addressed to the original Vintageheuer.com, 5% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (852 ms) belongs to the original domain Vintageheuer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.9 kB (8%)

Content Size

854.0 kB

After Optimization

784.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vintageheuer.com main page is 854.0 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. 70% of websites need less resources to load. Images take 586.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 50.2 kB

  • Original 63.3 kB
  • After minification 63.3 kB
  • After compression 13.1 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 50.2 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 31 B

  • Original 586.4 kB
  • After minification 586.3 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. Vintageheuer images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 9.8 kB

  • Original 137.3 kB
  • After minification 137.2 kB
  • After compression 127.5 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

-15%

Potential reduce by 9.9 kB

  • Original 67.0 kB
  • After minification 59.7 kB
  • After compression 57.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. Vintageheuer.com needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (86%)

Requests Now

73

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.vintageheuer.com

www.vintageheuer.com

530 ms

font-awesome.min.css

font-awesome.min.css

152 ms

css

css

191 ms

toolset-common-es.css

toolset-common-es.css

63 ms

style.css

style.css

85 ms

style.min.css

style.min.css

83 ms

views-frontend.css

views-frontend.css

521 ms

styles.css

styles.css

532 ms

cell-menu-css.css

cell-menu-css.css

114 ms

toolset-notifications.css

toolset-notifications.css

114 ms

ddl-front-end.css

ddl-front-end.css

142 ms

toolset-common.css

toolset-common.css

141 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

143 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

143 ms

wpv-pagination.css

wpv-pagination.css

182 ms

jquery.min.js

jquery.min.js

149 ms

lazysizes.min.js

lazysizes.min.js

181 ms

toolset-common-es-frontend.js

toolset-common-es-frontend.js

182 ms

ddl-layouts-frontend.js

ddl-layouts-frontend.js

179 ms

style.css

style.css

401 ms

js

js

385 ms

bootstrap.js

bootstrap.js

398 ms

jquery.elevateZoom-3.0.8.min.js

jquery.elevateZoom-3.0.8.min.js

383 ms

app.js

app.js

395 ms

api.js

api.js

177 ms

422568cfe11f2e1415f5b71180f38009.css

422568cfe11f2e1415f5b71180f38009.css

402 ms

views-frontend.js

views-frontend.js

401 ms

wp-polyfill.min.js

wp-polyfill.min.js

401 ms

index.js

index.js

403 ms

ddl-tabs-cell-frontend.js

ddl-tabs-cell-frontend.js

402 ms

api.js

api.js

400 ms

index.js

index.js

403 ms

wp-embed.min.js

wp-embed.min.js

440 ms

underscore.min.js

underscore.min.js

440 ms

backbone.min.js

backbone.min.js

443 ms

core.min.js

core.min.js

441 ms

widget.min.js

widget.min.js

441 ms

mouse.min.js

mouse.min.js

443 ms

resizable.min.js

resizable.min.js

444 ms

draggable.min.js

draggable.min.js

444 ms

button.min.js

button.min.js

446 ms

position.min.js

position.min.js

443 ms

dialog.min.js

dialog.min.js

764 ms

utils.js

utils.js

755 ms

ddl-menu-cell-front-end.js

ddl-menu-cell-front-end.js

379 ms

datepicker.min.js

datepicker.min.js

350 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

370 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

344 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

342 ms

wp-util.min.js

wp-util.min.js

364 ms

wp-playlist.min.js

wp-playlist.min.js

342 ms

wpv-pagination-embedded.js

wpv-pagination-embedded.js

327 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

153 ms

placeholder-200x100.png

placeholder-200x100.png

205 ms

placeholder-1269x157.png

placeholder-1269x157.png

527 ms

placeholder-428x293.png

placeholder-428x293.png

527 ms

wibble.png

wibble.png

544 ms

placeholder-500x500.png

placeholder-500x500.png

201 ms

placeholder-420x150.png

placeholder-420x150.png

206 ms

placeholder-505x135.png

placeholder-505x135.png

205 ms

analytics.js

analytics.js

320 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

320 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

321 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

484 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

445 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

171 ms

Vintage-Heuer-Logo.png

Vintage-Heuer-Logo.png

164 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

312 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

302 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

546 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

479 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

477 ms

recaptcha__en.js

recaptcha__en.js

227 ms

collect

collect

44 ms

visit-sister-banner.png.png

visit-sister-banner.png.png

849 ms

1-1.jpg

1-1.jpg

57 ms

1.jpg

1.jpg

16 ms

1.jpg

1.jpg

852 ms

1-3.jpg

1-3.jpg

584 ms

Accessibility Review

vintageheuer.com accessibility score

71

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

Image elements do not have [alt] attributes

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.

Best Practices

vintageheuer.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

vintageheuer.com SEO score

76

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

vintageheuer.com

Open Graph data is detected on the main page of Vintageheuer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: