Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

wurth.be

Würth Belux Online Shop | 130.000 producten - Bestel snel en makkelijk

Page Load Speed

5.8 sec in total

First Response

488 ms

Resources Loaded

5.1 sec

Page Rendered

213 ms

About Website

Welcome to wurth.be homepage info - get ready to check Wurth best content for Belgium right away, or after learning these important things about wurth.be

Het grootste assortiment schroeven, bouten, moeren, pluggen, boren, smeermiddelen, machines en meer. Snelle levering! Technische info. Alles voor de vakman. Wekelijkse promoties!

Visit wurth.be

Key Findings

We analyzed Wurth.be page load time and found that the first response time was 488 ms and then it took 5.4 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

wurth.be performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value4,760 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

www.wurth.be

488 ms

EUR

1824 ms

webfont_wl2.css

103 ms

screen.20160317150140524.min.css

205 ms

service_menu.20160317150140524.min.css

305 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 26% of them (18 requests) were addressed to the original Wurth.be, 49% (33 requests) were made to Eshop.wurth.be and 13% (9 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Eshop.wurth.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 675.2 kB (39%)

Content Size

1.7 MB

After Optimization

1.1 MB

In fact, the total size of Wurth.be main page is 1.7 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 830.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 50.1 kB

  • Original 60.7 kB
  • After minification 55.4 kB
  • After compression 10.7 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.1 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 54.4 kB

  • Original 830.4 kB
  • After minification 776.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. Wurth images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 470.4 kB

  • Original 739.3 kB
  • After minification 737.3 kB
  • After compression 268.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 470.4 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 100.3 kB

  • Original 119.4 kB
  • After minification 71.1 kB
  • After compression 19.1 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. Wurth.be needs all CSS files to be minified and compressed as it can save up to 100.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (64%)

Requests Now

66

After Optimization

24

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

Accessibility Review

wurth.be accessibility score

63

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

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.

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 IDs are not unique

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

wurth.be 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

wurth.be SEO score

84

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

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