Tools & Wizards About Us
vreeken.nl screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

vreeken.nl

Vreeken's Zaden

Page Load Speed

4.6 sec in total

First Response

745 ms

Resources Loaded

3.6 sec

Page Rendered

225 ms

vreeken.nl screenshot

About Website

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

Al vanaf 1926 is ons familiebedrijf Vreeken’s Zaden gespecialiseerd in zaden.

Visit vreeken.nl

Key Findings

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

Performance Metrics

vreeken.nl performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

vreeken.nl

745 ms

www.vreeken.nl

1254 ms

reset.min.css

96 ms

style.min.css

191 ms

zaden.min.css

283 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 95% of them (53 requests) were addressed to the original Vreeken.nl, 2% (1 request) were made to Ajax.googleapis.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Vreeken.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.7 kB (21%)

Content Size

593.1 kB

After Optimization

471.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vreeken.nl main page is 593.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 343.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 52.2 kB

  • Original 62.8 kB
  • After minification 61.3 kB
  • After compression 10.6 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 52.2 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 10.8 kB

  • Original 343.9 kB
  • After minification 333.1 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. Vreeken images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 58.5 kB

  • Original 184.8 kB
  • After minification 184.4 kB
  • After compression 126.3 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 58.5 kB or 32% of the original size.

CSS Optimization

-10%

Potential reduce by 152 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 1.4 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. Vreeken.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 26 (49%)

Requests Now

53

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vreeken.nl

vreeken.nl

745 ms

www.vreeken.nl

www.vreeken.nl

1254 ms

reset.min.css

reset.min.css

96 ms

style.min.css

style.min.css

191 ms

zaden.min.css

zaden.min.css

283 ms

jquery-ui-1.10.3.custom.min.css

jquery-ui-1.10.3.custom.min.css

285 ms

jquery.min.js

jquery.min.js

21 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

467 ms

jquery.impromptu.min.js

jquery.impromptu.min.js

300 ms

toggles.min.js

toggles.min.js

301 ms

pdfobject.min.js

pdfobject.min.js

300 ms

functions.js

functions.js

375 ms

clearbox.js

clearbox.js

376 ms

js

js

66 ms

awstats_misc_tracker.js

awstats_misc_tracker.js

374 ms

cb_style.css

cb_style.css

97 ms

cb_config.js

cb_config.js

95 ms

cb_language.js

cb_language.js

95 ms

cb_core.js

cb_core.js

95 ms

search.png

search.png

131 ms

logo.png

logo.png

127 ms

menu.png

menu.png

130 ms

logo_pdf.jpg

logo_pdf.jpg

185 ms

home_seeds.png

home_seeds.png

130 ms

nieuwsbrief.jpg

nieuwsbrief.jpg

131 ms

homepage_aardperen.jpg

homepage_aardperen.jpg

197 ms

homepage_pootaardappels_2024.jpg

homepage_pootaardappels_2024.jpg

210 ms

homepage-aanbiedingen.jpg

homepage-aanbiedingen.jpg

195 ms

maak-je-eigen-zakje-zaad-thumb.jpg

maak-je-eigen-zakje-zaad-thumb.jpg

211 ms

wederverkoop.jpg

wederverkoop.jpg

317 ms

190871-bak-siermais-mergoscia.jpg

190871-bak-siermais-mergoscia.jpg

360 ms

733887-agapanthus-africanus-blue-sunfield-dr-brouwer-elisabeth.jpg

733887-agapanthus-africanus-blue-sunfield-dr-brouwer-elisabeth.jpg

463 ms

831300-citroengras.jpg

831300-citroengras.jpg

353 ms

neem-een-kijkje.jpg

neem-een-kijkje.jpg

388 ms

nieuwsgierigheid-naar-planten.jpg

nieuwsgierigheid-naar-planten.jpg

477 ms

slowfood.jpg

slowfood.jpg

409 ms

facebook.jpg

facebook.jpg

446 ms

awstats_misc_tracker.js

awstats_misc_tracker.js

328 ms

background.gif

background.gif

357 ms

content_spring.jpg

content_spring.jpg

377 ms

blank.gif

blank.gif

415 ms

outer_prev.png

outer_prev.png

420 ms

outer_pause.png

outer_pause.png

432 ms

outer_start.png

outer_start.png

446 ms

outer_next.png

outer_next.png

449 ms

loading.gif

loading.gif

469 ms

close.png

close.png

506 ms

prev.png

prev.png

512 ms

next.png

next.png

526 ms

pause.png

pause.png

538 ms

start.png

start.png

541 ms

icovreeken.ttf

icovreeken.ttf

518 ms

print.min.css

print.min.css

96 ms

zaden_print.min.css

zaden_print.min.css

97 ms

css

css

36 ms

icons.png

icons.png

97 ms

Accessibility Review

vreeken.nl accessibility score

76

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

vreeken.nl best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vreeken.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Vreeken.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

vreeken.nl

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