Tools & Wizards About Us
warentuin.nl screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

warentuin.nl

Warentuin l Jouw Online Tuincentrum

Page Load Speed

28.6 sec in total

First Response

52 ms

Resources Loaded

27.9 sec

Page Rendered

592 ms

warentuin.nl screenshot

About Website

Visit warentuin.nl now to see the best up-to-date Warentuin content for Netherlands and also check out these interesting facts you probably never knew about warentuin.nl

Ontdek Warentuin, jouw online tuincentrum voor alles wat je nodig hebt voor huis, tuin, dier en kerst! Vind de beste kwaliteit en prijzen hier.

Visit warentuin.nl

Key Findings

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

Performance Metrics

warentuin.nl performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.205

61/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

warentuin.nl

52 ms

www.warentuin.nl

810 ms

calendar.min.css

55 ms

styles-m.min.css

74 ms

bootstrap-grid.min.css

136 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Warentuin.nl, 57% (32 requests) were made to Cdn.warentuin.nl and 20% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (9.8 sec) relates to the external source Kiyoh.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 588.6 kB (30%)

Content Size

2.0 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Warentuin.nl main page is 2.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. Only a small number of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 333.8 kB

  • Original 379.9 kB
  • After minification 355.1 kB
  • After compression 46.1 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 333.8 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 4.4 kB

  • Original 82.2 kB
  • After minification 77.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. Warentuin images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 205.4 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.1 MB

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 205.4 kB or 16% of the original size.

CSS Optimization

-20%

Potential reduce by 45.0 kB

  • Original 225.9 kB
  • After minification 225.9 kB
  • After compression 180.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. Warentuin.nl needs all CSS files to be minified and compressed as it can save up to 45.0 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

42

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

warentuin.nl

warentuin.nl

52 ms

www.warentuin.nl

www.warentuin.nl

810 ms

calendar.min.css

calendar.min.css

55 ms

styles-m.min.css

styles-m.min.css

74 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

136 ms

swiper.min.css

swiper.min.css

72 ms

postcodecheckout.min.css

postcodecheckout.min.css

136 ms

autocomplete-address.min.css

autocomplete-address.min.css

72 ms

styles-l.min.css

styles-l.min.css

139 ms

css

css

52 ms

warentuin-parasol-logo_4x_2.png

warentuin-parasol-logo_4x_2.png

541 ms

grey-money.png

grey-money.png

232 ms

grey-delivery.png

grey-delivery.png

233 ms

grey-garden.png

grey-garden.png

232 ms

preloader-img.svg

preloader-img.svg

241 ms

retrieve-widget.html

retrieve-widget.html

9805 ms

email-decode.min.js

email-decode.min.js

18 ms

require.min.js

require.min.js

223 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

224 ms

bundle0.min.js

bundle0.min.js

226 ms

bundle1.min.js

bundle1.min.js

228 ms

bundle2.min.js

bundle2.min.js

231 ms

bundle3.min.js

bundle3.min.js

234 ms

bundle4.min.js

bundle4.min.js

229 ms

bundle5.min.js

bundle5.min.js

234 ms

static.min.js

static.min.js

402 ms

mixins.min.js

mixins.min.js

402 ms

requirejs-config.min.js

requirejs-config.min.js

401 ms

postcode.min.js

postcode.min.js

401 ms

autocompleteaddress.min.js

autocompleteaddress.min.js

403 ms

init.min.js

init.min.js

403 ms

7416ced696d1d16266706c562.js

7416ced696d1d16266706c562.js

9797 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

227 ms

nederlands.png

nederlands.png

9553 ms

gtm.js

gtm.js

9405 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky462EK9C0Ym4fA5Tg.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Ky462EK9C0Ym4fA5Tg.woff

9343 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KyK62EK9C0Ym4fA5Tg.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KyK62EK9C0Ym4fA5Tg.woff

9349 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm62EK9C0Ym4fA5Tg.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kzm62EK9C0Ym4fA5Tg.woff

9517 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7GEK9C0Ym4fA5Tg.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxm7GEK9C0Ym4fA5Tg.woff

9349 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7GEK9C0Ym4fA5Tg.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kxf7GEK9C0Ym4fA5Tg.woff

9402 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw47GEK9C0Ym4fA5Tg.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8Kw47GEK9C0Ym4fA5Tg.woff

9402 ms

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KwR7GEK9C0Ym4fA5Tg.woff

nwpBtKy2OAdR1K-IwhWudF-R9QMylBJAV3Bo8KwR7GEK9C0Ym4fA5Tg.woff

9565 ms

athlete2.woff

athlete2.woff

59 ms

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqF5JxCkSnKXEzTrovA.woff

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqF5JxCkSnKXEzTrovA.woff

9515 ms

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqGdJxCkSnKXEzTrovA.woff

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqGdJxCkSnKXEzTrovA.woff

9515 ms

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqItOxCkSnKXEzTrovA.woff

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqItOxCkSnKXEzTrovA.woff

9515 ms

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqOdOxCkSnKXEzTrovA.woff

nwpDtKy2OAdR1K-IwhWudF-R3woAa8opPOrG97lwqOdOxCkSnKXEzTrovA.woff

9515 ms

js-translation.json

js-translation.json

9300 ms

thuiswinkel-widget.css

thuiswinkel-widget.css

8263 ms

kiyoh-widget.js

kiyoh-widget.js

8263 ms

tw_waarborg_logo_1.png

tw_waarborg_logo_1.png

8262 ms

tw_waarborg_logo_2.png

tw_waarborg_logo_2.png

8262 ms

print.min.css

print.min.css

218 ms

owl.carousel.min.css

owl.carousel.min.css

4 ms

perfect-scrollbar.min.css

perfect-scrollbar.min.css

7867 ms

tw_rating_135.png

tw_rating_135.png

8800 ms

Accessibility Review

warentuin.nl accessibility score

73

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

warentuin.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

warentuin.nl SEO score

82

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 Warentuin.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 Warentuin.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

warentuin.nl

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