Tools & Wizards About Us
ifleur.nl screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

ifleur.nl

Kunstbloem kopen? Kunstbloemen goedkoop en mooi - iFleur

Page Load Speed

2.4 sec in total

First Response

635 ms

Resources Loaded

1.6 sec

Page Rendered

181 ms

ifleur.nl screenshot

About Website

Click here to check amazing IFleur content. Otherwise, check out these important facts you probably never knew about ifleur.nl

De mooiste kunstbloemen, zijden bloemen en bloemdecoraties koopt u online bij iFleur.nl. Bekijk snel het uitgebreide aanbod.

Visit ifleur.nl

Key Findings

We analyzed Ifleur.nl page load time and found that the first response time was 635 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

ifleur.nl performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.304

39/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

ifleur.nl

635 ms

js

98 ms

modernizr-custom.webp-detection.min.js

106 ms

jquery-ui-1.9.2.custom.min.js

270 ms

slick.min.js

267 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 86% of them (24 requests) were addressed to the original Ifleur.nl, 7% (2 requests) were made to Maxcdn.bootstrapcdn.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (662 ms) belongs to the original domain Ifleur.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 378.5 kB (49%)

Content Size

768.9 kB

After Optimization

390.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifleur.nl main page is 768.9 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. HTML takes 444.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 353.9 kB

  • Original 444.6 kB
  • After minification 435.7 kB
  • After compression 90.7 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 353.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 2.5 kB

  • Original 134.9 kB
  • After minification 132.5 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. IFleur images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 20.5 kB

  • Original 129.8 kB
  • After minification 117.1 kB
  • After compression 109.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 20.5 kB or 16% of the original size.

CSS Optimization

-3%

Potential reduce by 1.6 kB

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

Requests Breakdown

Number of requests can be reduced by 22 (85%)

Requests Now

26

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ifleur.nl

ifleur.nl

635 ms

js

js

98 ms

modernizr-custom.webp-detection.min.js

modernizr-custom.webp-detection.min.js

106 ms

jquery-ui-1.9.2.custom.min.js

jquery-ui-1.9.2.custom.min.js

270 ms

slick.min.js

slick.min.js

267 ms

06bee8a581279e2c2a0a93e52456242a_jquery.matchHeight.js

06bee8a581279e2c2a0a93e52456242a_jquery.matchHeight.js

290 ms

3d6ad711a7946493f9aa5a67f0236cec_jquery.rating.js

3d6ad711a7946493f9aa5a67f0236cec_jquery.rating.js

291 ms

lightgallery.min.js

lightgallery.min.js

292 ms

lg-thumbnail.min.js

lg-thumbnail.min.js

293 ms

lg-video.min.js

lg-video.min.js

352 ms

lg-fullscreen.min.js

lg-fullscreen.min.js

353 ms

5a89ef1e1c0d1b64bf42758d7c6d9274_Generic.js

5a89ef1e1c0d1b64bf42758d7c6d9274_Generic.js

360 ms

protector.min.js

protector.min.js

368 ms

Vertoshop.js

Vertoshop.js

381 ms

xajax.js

xajax.js

384 ms

Scripts.parsed_192.js

Scripts.parsed_192.js

437 ms

Logo%20iFleur%20zijden%20kunstbloemen_nl.png

Logo%20iFleur%20zijden%20kunstbloemen_nl.png

440 ms

banner-kunstbloemen_nl.jpg

banner-kunstbloemen_nl.jpg

615 ms

css2

css2

59 ms

font-awesome.min.css

font-awesome.min.css

49 ms

Material-Icons.css

Material-Icons.css

454 ms

bootstrap.min.css

bootstrap.min.css

564 ms

jquery-ui-1.9.2.custom.min.css

jquery-ui-1.9.2.custom.min.css

474 ms

883f3a3e853ef667bce66b9c91609399_slick.css

883f3a3e853ef667bce66b9c91609399_slick.css

519 ms

357b11ed4d11e042b3709b8b1718c0ac_slick-theme.css

357b11ed4d11e042b3709b8b1718c0ac_slick-theme.css

525 ms

lightgallery.min.css

lightgallery.min.css

542 ms

15339b9078bc22aac42530c9f98a9cea_Generic.css

15339b9078bc22aac42530c9f98a9cea_Generic.css

662 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

14 ms

Accessibility Review

ifleur.nl accessibility score

89

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

ifleur.nl 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

SEO Factors

ifleur.nl SEO score

99

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

    EN

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifleur.nl can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Dutch language. Our system also found out that Ifleur.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

ifleur.nl

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