Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

blokker.nl

Welkom bij Blokker, de huishoudwinkel van Nederland

Page Load Speed

8.1 sec in total

First Response

3.2 sec

Resources Loaded

4.4 sec

Page Rendered

465 ms

blokker.nl screenshot

About Website

Welcome to blokker.nl homepage info - get ready to check Blokker best content for Netherlands right away, or after learning these important things about blokker.nl

De winkel voor iedereen, met een ruim assortiment aan goede en betaalbare artikelen voor het huishouden, speelgoed en tuinmeubelen. Bestel gemakkelijk en snel en laat thuisbezorgen of haal af bij een ...

Visit blokker.nl

Key Findings

We analyzed Blokker.nl page load time and found that the first response time was 3.2 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

blokker.nl performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

www.blokker.nl

3225 ms

main.js

43 ms

product-tile.js

43 ms

einstein-recommendations.js

43 ms

global.css

29 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 59% of them (38 requests) were addressed to the original Blokker.nl, 23% (15 requests) were made to Images.blokker.nl and 5% (3 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Blokker.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 524.2 kB (22%)

Content Size

2.4 MB

After Optimization

1.9 MB

In fact, the total size of Blokker.nl main page is 2.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 482.9 kB

  • Original 529.9 kB
  • After minification 529.0 kB
  • After compression 47.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. 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 482.9 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.6 MB
  • After minification 1.6 MB

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. Blokker images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 309 B

  • Original 240.9 kB
  • After minification 240.9 kB
  • After compression 240.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

-94%

Potential reduce by 40.9 kB

  • Original 43.7 kB
  • After minification 2.7 kB
  • After compression 2.7 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. Blokker.nl needs all CSS files to be minified and compressed as it can save up to 40.9 kB or 94% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (29%)

Requests Now

56

After Optimization

40

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

Accessibility Review

blokker.nl accessibility score

71

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

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

blokker.nl best practices score

83

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

SEO Factors

blokker.nl SEO score

100

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

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 Blokker.nl 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 Blokker.nl 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 Blokker. 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: