Tools & Wizards About Us
klaverlily.nl screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

klaverlily.nl

Quality by Nature | Klaver Flowers

Page Load Speed

3.8 sec in total

First Response

293 ms

Resources Loaded

3.2 sec

Page Rendered

282 ms

klaverlily.nl screenshot

About Website

Click here to check amazing Klaver Lily content. Otherwise, check out these important facts you probably never knew about klaverlily.nl

Roze, wit, groot en klein. Lelies en Gypsophila vindt u in veel diverse vormen. Maar vooral: in verschillende kwaliteit en prijs.

Visit klaverlily.nl

Key Findings

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

Performance Metrics

klaverlily.nl performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value2,340 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.044

99/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

klaverlily.nl

293 ms

www.klaverflowers.com

503 ms

klaverflowers.com

985 ms

gtm.js

110 ms

logo.svg

102 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Klaverlily.nl, 65% (35 requests) were made to Klaverflowers.com and 9% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Klaverflowers.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.3 kB (29%)

Content Size

1.4 MB

After Optimization

979.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Klaverlily.nl main page is 1.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. 60% of websites need less resources to load. Images take 549.0 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 385.4 kB

  • Original 467.2 kB
  • After minification 456.7 kB
  • After compression 81.8 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 385.4 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 549.0 kB
  • After minification 549.0 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. Klaver Lily images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 11.9 kB

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

CSS Optimization

-0%

Potential reduce by 18 B

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

Requests Breakdown

Number of requests can be reduced by 10 (27%)

Requests Now

37

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

klaverlily.nl

klaverlily.nl

293 ms

www.klaverflowers.com

www.klaverflowers.com

503 ms

klaverflowers.com

klaverflowers.com

985 ms

gtm.js

gtm.js

110 ms

logo.svg

logo.svg

102 ms

maxresdefault.jpg

maxresdefault.jpg

214 ms

main-default-bottom-cached.js

main-default-bottom-cached.js

284 ms

pattern-left.svg

pattern-left.svg

1038 ms

calvados-03-small.jpg

calvados-03-small.jpg

314 ms

brandbox-bg-desktop.svg

brandbox-bg-desktop.svg

315 ms

signum-02-small.jpg

signum-02-small.jpg

411 ms

lelie.svg

lelie.svg

316 ms

xlence-krans-02-small.jpg

xlence-krans-02-small.jpg

409 ms

gipskruid.svg

gipskruid.svg

409 ms

logo-icon-fc-light.svg

logo-icon-fc-light.svg

426 ms

vlog-in-de-kas.jpg

vlog-in-de-kas.jpg

605 ms

toba.png

toba.png

471 ms

flower-left.svg

flower-left.svg

532 ms

logo-icon-fc.svg

logo-icon-fc.svg

550 ms

footer-logo-lilies.svg

footer-logo-lilies.svg

548 ms

footer-logo-gypsophila.svg

footer-logo-gypsophila.svg

600 ms

Montserrat-MediumItalic.woff

Montserrat-MediumItalic.woff

875 ms

Montserrat-SemiBoldItalic.woff

Montserrat-SemiBoldItalic.woff

885 ms

Montserrat-BoldItalic.woff

Montserrat-BoldItalic.woff

792 ms

Montserrat-Medium.woff

Montserrat-Medium.woff

752 ms

Montserrat-SemiBold.woff

Montserrat-SemiBold.woff

783 ms

Montserrat-Bold.woff

Montserrat-Bold.woff

850 ms

fa-light-300.woff

fa-light-300.woff

900 ms

fa-brands-400.woff

fa-brands-400.woff

900 ms

fa-regular-400.woff

fa-regular-400.woff

869 ms

fa-solid-900.woff

fa-solid-900.woff

1012 ms

LexendZetta-Regular.woff

LexendZetta-Regular.woff

899 ms

calvados-03-small.jpg

calvados-03-small.jpg

972 ms

js

js

71 ms

analytics.js

analytics.js

23 ms

collect

collect

16 ms

cookieconsent.min.js

cookieconsent.min.js

793 ms

api.js

api.js

33 ms

recaptcha__en.js

recaptcha__en.js

28 ms

anchor

anchor

54 ms

styles__ltr.css

styles__ltr.css

5 ms

recaptcha__en.js

recaptcha__en.js

15 ms

JmauVxhhvNeGRVvMjuhavwcr4cbjHfJOauIT80S7Fws.js

JmauVxhhvNeGRVvMjuhavwcr4cbjHfJOauIT80S7Fws.js

40 ms

webworker.js

webworker.js

86 ms

logo_48.png

logo_48.png

27 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

49 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

54 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

58 ms

recaptcha__en.js

recaptcha__en.js

29 ms

home-default-print.css

home-default-print.css

97 ms

maxresdefault.jpg

maxresdefault.jpg

50 ms

video-play.svg

video-play.svg

102 ms

dot-white-active.svg

dot-white-active.svg

97 ms

dot-white.svg

dot-white.svg

99 ms

Accessibility Review

klaverlily.nl accessibility score

64

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

ARIA input fields do not have accessible names

High

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

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

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.

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

klaverlily.nl best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

klaverlily.nl SEO score

97

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

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

klaverlily.nl

Open Graph data is detected on the main page of Klaver Lily. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: