8.6 sec in total
743 ms
7.2 sec
562 ms
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.nlWe analyzed Ifleur.nl page load time and found that the first response time was 743 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ifleur.nl performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value6.3 s
10/100
25%
Value4.7 s
69/100
10%
Value360 ms
72/100
30%
Value0.834
4/100
15%
Value6.8 s
55/100
10%
743 ms
757 ms
961 ms
497 ms
499 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 76% of them (39 requests) were addressed to the original Ifleur.nl, 12% (6 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Ifleur.nl.
Page size can be reduced by 512.8 kB (15%)
3.4 MB
2.9 MB
In fact, the total size of Ifleur.nl main page is 3.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. 25% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 22.2 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. This page needs HTML code to be minified as it can gain 7.5 kB, which is 29% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 22.2 kB or 85% of the original size.
Potential reduce by 140.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.
Potential reduce by 139.9 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 139.9 kB or 67% of the original size.
Potential reduce by 210.3 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 needs all CSS files to be minified and compressed as it can save up to 210.3 kB or 85% of the original size.
Number of requests can be reduced by 15 (36%)
42
27
The browser has sent 42 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 7 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
ifleur.nl
743 ms
www.ifleur.nl
757 ms
bootstrap.min.css
961 ms
font-awesome.min.css
497 ms
prettyPhoto.css
499 ms
price-range.css
317 ms
animate.css
870 ms
main.css
832 ms
responsive.css
2845 ms
jquery.js
2919 ms
bootstrap.min.js
2743 ms
jquery.scrollUp.min.js
2560 ms
price-range.js
2645 ms
jquery.prettyPhoto.js
2742 ms
main.js
2757 ms
css
22 ms
css
34 ms
css
43 ms
analytics.js
72 ms
logo.png
218 ms
searchicon.png
336 ms
daarom.png
377 ms
iDeal.png
377 ms
visamastercard.png
625 ms
Pioenroos%20in%20glas,%20roze.jpg
604 ms
Bloemstuk,%20paars-roze.jpg
959 ms
Landelijk%20bloemstuk,%20licht.jpg
1030 ms
Bloemstuk%20orchidee,%2045cm.jpg
1265 ms
Bloemstuk%20orchidee,%2045cm.jpg
1345 ms
Bloemstuk%20orchidee,%2045cm.jpg
2628 ms
Fleurig%20bloemstukje,%20per%20stuk%20.jpg
1742 ms
Landelijk%20tafelstukje,%20wit-roze.jpg
1688 ms
Bloemstuk%20foambloemen.jpg
1912 ms
Orchidee%20Plant,%2050cm.jpg
2339 ms
Tafelstuk,%20roze-paars.jpg
2300 ms
hotelneslogo.jpg
2531 ms
hollandcasino.jpg
2530 ms
logo_breda.gif
2341 ms
jaapeden-logo.png
2591 ms
raadhuys.jpg
2781 ms
try-out.jpg
2602 ms
winkel.jpg
3047 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
16 ms
vzIUHo9z-oJ4WgkpPOtg1_esZW2xOQ-xsNqO47m55DA.woff
15 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
16 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
16 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
17 ms
fontawesome-webfont.woff
2985 ms
EAqh528fFdbUek8UOky4sA.woff
15 ms
collect
15 ms
collect
55 ms
ifleur.nl accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ifleur.nl best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
ifleur.nl SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
NL
ISO-8859-1
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 iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ifleur.nl
Open Graph description is not detected on the main page of IFleur. 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: