Tools & Wizards About Us
wever-ducre.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

wever-ducre.com

Design Lighting from Belgium with Love | Wever & Ducré

Page Load Speed

4.2 sec in total

First Response

1.1 sec

Resources Loaded

2.4 sec

Page Rendered

716 ms

wever-ducre.com screenshot

About Website

Click here to check amazing Wever Ducre content for Netherlands. Otherwise, check out these important facts you probably never knew about wever-ducre.com

Life is too short for boring lighting. Wever & Ducré stands for trendy LED luminaires with an appealing design and high-quality material. Get inspired.

Visit wever-ducre.com

Key Findings

We analyzed Wever-ducre.com page load time and found that the first response time was 1.1 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wever-ducre.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value1,160 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

www.weverducre.com

1093 ms

otSDKStub.js

33 ms

container_caghevPl.js

1041 ms

libs.css

228 ms

style.css

350 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wever-ducre.com, 15% (3 requests) were made to Cdn.cookielaw.org and 5% (1 request) were made to M.xal.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Weverducre.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 552.7 kB (53%)

Content Size

1.0 MB

After Optimization

489.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Wever-ducre.com main page is 1.0 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. 40% of websites need less resources to load. HTML takes 621.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 507.9 kB

  • Original 621.1 kB
  • After minification 567.1 kB
  • After compression 113.2 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 507.9 kB or 82% of the original size.

JavaScript Optimization

-8%

Potential reduce by 27.3 kB

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

CSS Optimization

-23%

Potential reduce by 17.4 kB

  • Original 76.6 kB
  • After minification 76.6 kB
  • After compression 59.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. Wever-ducre.com needs all CSS files to be minified and compressed as it can save up to 17.4 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (55%)

Requests Now

11

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.weverducre.com

www.weverducre.com

1093 ms

otSDKStub.js

otSDKStub.js

33 ms

container_caghevPl.js

container_caghevPl.js

1041 ms

libs.css

libs.css

228 ms

style.css

style.css

350 ms

gtm.js

gtm.js

75 ms

script.js

script.js

891 ms

7dbca7d9-9db5-4a80-9d1f-b4142d523d72.json

7dbca7d9-9db5-4a80-9d1f-b4142d523d72.json

33 ms

wever-ducre-logo.svg

wever-ducre-logo.svg

369 ms

xalgroup-logo.svg

xalgroup-logo.svg

371 ms

Gotham-Book.woff

Gotham-Book.woff

885 ms

otBannerSdk.js

otBannerSdk.js

17 ms

Gotham-Bold.woff

Gotham-Bold.woff

698 ms

css-vars-ponyfill.min.js

css-vars-ponyfill.min.js

243 ms

ChronicleTextG1-SemiIta-Pro_Web.woff

ChronicleTextG1-SemiIta-Pro_Web.woff

555 ms

ChronicleTextG1-Italic-Pro_Web.woff

ChronicleTextG1-Italic-Pro_Web.woff

141 ms

ChronicleTextG1-Semibd-Pro_Web.woff

ChronicleTextG1-Semibd-Pro_Web.woff

553 ms

ChronicleTextG1-Regular-Pro_Web.woff

ChronicleTextG1-Regular-Pro_Web.woff

556 ms

ChronicleTextG1-Bold-Pro_Web.woff

ChronicleTextG1-Bold-Pro_Web.woff

555 ms

iconfont.woff

iconfont.woff

556 ms

Accessibility Review

wever-ducre.com accessibility score

82

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-*] attributes do not match their roles

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.

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

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.

Best Practices

wever-ducre.com best practices score

92

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

Page has valid source maps

SEO Factors

wever-ducre.com SEO score

86

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

wever-ducre.com

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