Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

wijnvoordeel.be

Betere wijn, meer voordeel | Wijnvoordeel

Page Load Speed

7.2 sec in total

First Response

1.3 sec

Resources Loaded

5.6 sec

Page Rendered

371 ms

wijnvoordeel.be screenshot

About Website

Click here to check amazing Wijnvoordeel content for Belgium. Otherwise, check out these important facts you probably never knew about wijnvoordeel.be

Online wijn bestellen tegen de laagste prijzen bij de voordeligste wijnwinkel van België.

Visit wijnvoordeel.be

Key Findings

We analyzed Wijnvoordeel.be page load time and found that the first response time was 1.3 sec and then it took 5.9 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

wijnvoordeel.be performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value6,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value20.8 s

2/100

10%

Network Requests Diagram

www.wijnvoordeel.be

1310 ms

stylesheet.css

289 ms

style.css

409 ms

style.res.css

401 ms

fancybox.css

304 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 60% of them (83 requests) were addressed to the original Wijnvoordeel.be, 9% (13 requests) were made to N8.pleisty.com and 6% (8 requests) were made to Api.trustpilot.com. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Newsletter.wijnvoordeel.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (50%)

Content Size

2.2 MB

After Optimization

1.1 MB

In fact, the total size of Wijnvoordeel.be main page is 2.2 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. Javascripts take 976.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 135.5 kB

  • Original 165.1 kB
  • After minification 138.0 kB
  • After compression 29.5 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 27.0 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 135.5 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 31.8 kB

  • Original 823.0 kB
  • After minification 791.2 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. Wijnvoordeel images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 735.0 kB

  • Original 976.5 kB
  • After minification 809.1 kB
  • After compression 241.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 735.0 kB or 75% of the original size.

CSS Optimization

-82%

Potential reduce by 181.5 kB

  • Original 220.4 kB
  • After minification 171.4 kB
  • After compression 38.9 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. Wijnvoordeel.be needs all CSS files to be minified and compressed as it can save up to 181.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (54%)

Requests Now

134

After Optimization

62

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

Accessibility Review

wijnvoordeel.be accessibility score

75

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

button, link, and menuitem elements do not have accessible names.

High

[role]s do not have all required [aria-*] attributes

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

Low

No form fields have multiple labels

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

wijnvoordeel.be best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

wijnvoordeel.be SEO score

93

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

    ISO-8859-15

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wijnvoordeel.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 Wijnvoordeel.be main page’s claimed encoding is iso-8859-15. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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