Tools & Wizards About Us
watchfinder.es screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

watchfinder.es

Watchfinder & Co. - The Pre-Owned Watch Specialist

Page Load Speed

2.1 sec in total

First Response

169 ms

Resources Loaded

1.7 sec

Page Rendered

179 ms

watchfinder.es screenshot

About Website

Visit watchfinder.es now to see the best up-to-date Watchfinder content and also check out these interesting facts you probably never knew about watchfinder.es

Visit Watchfinder to buy and sell luxury watches. Browse pre-owned watches from Rolex, Omega, Breitling, TAG Heuer, Cartier and more, all available now.

Visit watchfinder.es

Key Findings

We analyzed Watchfinder.es page load time and found that the first response time was 169 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

watchfinder.es performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value5.7 s

50/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

watchfinder.es

169 ms

watchfinder.es

293 ms

www.watchfinder.es

442 ms

css2

31 ms

a53c3757abeeba50.js

170 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 70% of them (35 requests) were addressed to the original Watchfinder.es, 8% (4 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (614 ms) belongs to the original domain Watchfinder.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.8 kB (21%)

Content Size

512.5 kB

After Optimization

403.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Watchfinder.es main page is 512.5 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. 65% of websites need less resources to load. Javascripts take 324.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 104.9 kB

  • Original 122.9 kB
  • After minification 103.5 kB
  • After compression 18.0 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. This page needs HTML code to be minified as it can gain 19.3 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 104.9 kB or 85% of the original size.

Image Optimization

-2%

Potential reduce by 949 B

  • Original 54.7 kB
  • After minification 53.8 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. Watchfinder images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.0 kB

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

CSS Optimization

-0%

Potential reduce by 10 B

  • Original 10.3 kB
  • After minification 10.3 kB
  • After compression 10.3 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. Watchfinder.es has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (88%)

Requests Now

42

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

watchfinder.es

watchfinder.es

169 ms

watchfinder.es

watchfinder.es

293 ms

www.watchfinder.es

www.watchfinder.es

442 ms

css2

css2

31 ms

a53c3757abeeba50.js

a53c3757abeeba50.js

170 ms

main.a1e95b9ee61799ab9ca9.css

main.a1e95b9ee61799ab9ca9.css

71 ms

styles.9d4bb090728413fbff66.css

styles.9d4bb090728413fbff66.css

141 ms

global.f8966ddf84db9bf14298.css

global.f8966ddf84db9bf14298.css

204 ms

core

core

277 ms

home

home

211 ms

vueVendor.bec7725d88152c5270c2.js

vueVendor.bec7725d88152c5270c2.js

397 ms

vendor.c16dab180dd1077f8ddd.js

vendor.c16dab180dd1077f8ddd.js

391 ms

swiperVendor.6ef7504317fb70e3444a.js

swiperVendor.6ef7504317fb70e3444a.js

397 ms

main.63b1d97a8cc97b451a47.js

main.63b1d97a8cc97b451a47.js

274 ms

productCard.77b0fd2828831c530aad.js

productCard.77b0fd2828831c530aad.js

392 ms

jquery.b22fed506aa1a257f36b.js

jquery.b22fed506aa1a257f36b.js

467 ms

jqueryUi.61ce0d17c43904602f7a.js

jqueryUi.61ce0d17c43904602f7a.js

395 ms

script.c99560559c00f0186e07.js

script.c99560559c00f0186e07.js

394 ms

lazySizes.ed93578ca18154857b1d.js

lazySizes.ed93578ca18154857b1d.js

394 ms

formValidation.6633d7b0f9dbecc3deae.js

formValidation.6633d7b0f9dbecc3deae.js

515 ms

ga4Datalayer.2c2ecd5ea79a1865bc5e.js

ga4Datalayer.2c2ecd5ea79a1865bc5e.js

515 ms

shopMenuImages.f84fc1c60da08cde734f.js

shopMenuImages.f84fc1c60da08cde734f.js

514 ms

typeahead.39d101fce2c12ed9e466.js

typeahead.39d101fce2c12ed9e466.js

515 ms

scriptDefer.91f628cfe1935fbd5bee.js

scriptDefer.91f628cfe1935fbd5bee.js

524 ms

wfConsentCookie.f8ba0ae0d5df139bf162.js

wfConsentCookie.f8ba0ae0d5df139bf162.js

536 ms

regionSelector.7749a57b268800d6d7a8.js

regionSelector.7749a57b268800d6d7a8.js

553 ms

browserDetect.82d496b1203f9a4180bc.js

browserDetect.82d496b1203f9a4180bc.js

554 ms

enquiry.0706f3ba31d00ab15036.js

enquiry.0706f3ba31d00ab15036.js

551 ms

tooltips.de8d3c2e9c29f1b9615b.js

tooltips.de8d3c2e9c29f1b9615b.js

552 ms

basketItemCount.27e95132c666a8ff06ad.js

basketItemCount.27e95132c666a8ff06ad.js

553 ms

articlesInject.879bc366e177cf2552ed.js

articlesInject.879bc366e177cf2552ed.js

598 ms

competitionPopup.7b2ecb12f03a0b99c5fb.js

competitionPopup.7b2ecb12f03a0b99c5fb.js

609 ms

imageUploader.512ee3ebc61ec8e9f032.js

imageUploader.512ee3ebc61ec8e9f032.js

612 ms

globalLocation.62ceaff1a6553473eb43.js

globalLocation.62ceaff1a6553473eb43.js

612 ms

owl.carousel.min.js

owl.carousel.min.js

614 ms

home.627370bec7615fbebdea.js

home.627370bec7615fbebdea.js

611 ms

gtm.js

gtm.js

255 ms

ai.0.js

ai.0.js

119 ms

New-Arrivals-Home-page-dark_3000x900.jpg;quality=80;h=450

New-Arrivals-Home-page-dark_3000x900.jpg;quality=80;h=450

165 ms

logo_wfco-mark-white-new-2019-07-03-01-25-20-978.png

logo_wfco-mark-white-new-2019-07-03-01-25-20-978.png

157 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

185 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

231 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuBWYMZg.ttf

335 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuOKfMZg.ttf

335 ms

icomoon.735625be2e87f6e8790f.ttf

icomoon.735625be2e87f6e8790f.ttf

356 ms

search-insights@2.7.0

search-insights@2.7.0

56 ms

landing

landing

227 ms

js

js

117 ms

infinitytrack.js

infinitytrack.js

52 ms

destination

destination

102 ms

Accessibility Review

watchfinder.es accessibility score

98

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.

Best Practices

watchfinder.es best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

watchfinder.es SEO score

99

Search Engine Optimization Advices

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 Watchfinder.es 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 Watchfinder.es 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

watchfinder.es

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