3.1 sec in total
280 ms
2.5 sec
280 ms
Welcome to floro.nl homepage info - get ready to check Floro best content for Netherlands right away, or after learning these important things about floro.nl
Via digitale innovatie helpen wij organisaties om de manier waarop zij online communiceren, verkopen, service verlenen en georganiseerd zijn te verbeteren
Visit floro.nlWe analyzed Floro.nl page load time and found that the first response time was 280 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
floro.nl performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value3.5 s
65/100
25%
Value13.6 s
2/100
10%
Value14,510 ms
0/100
30%
Value0
100/100
15%
Value30.0 s
0/100
10%
280 ms
740 ms
188 ms
66 ms
546 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 34% of them (12 requests) were addressed to the original Floro.nl, 29% (10 requests) were made to Use.typekit.net and 9% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (740 ms) belongs to the original domain Floro.nl.
Page size can be reduced by 682.1 kB (62%)
1.1 MB
417.0 kB
In fact, the total size of Floro.nl main page is 1.1 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. 35% of websites need less resources to load. Javascripts take 576.8 kB which makes up the majority of the site volume.
Potential reduce by 17.3 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 17.3 kB or 66% of the original size.
Potential reduce by 22.7 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. Obviously, Floro needs image optimization as it can save up to 22.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 382.4 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 382.4 kB or 66% of the original size.
Potential reduce by 259.8 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. Floro.nl needs all CSS files to be minified and compressed as it can save up to 259.8 kB or 90% of the original size.
Number of requests can be reduced by 12 (50%)
24
12
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floro. 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 7 to 1 for CSS and as a result speed up the page load time.
floro.nl
280 ms
www.floro.nl
740 ms
wrapped.css
188 ms
css
66 ms
wrapped.js
546 ms
hgl6vpa.js
234 ms
font-awesome.css
272 ms
animate.css
278 ms
css
77 ms
css
90 ms
ga.js
118 ms
j.php
117 ms
www.floro.nl
57 ms
arrow-down.png
186 ms
ajax.php
151 ms
kfX1T12CQgPculvVnjUu3RdRaLoyIyY3FFWvv4yPrsIffOaAggMmeMJ6Mk6f5Mb.woff
67 ms
_hLamr2qmahKDeqtBZ6aMBUfknb5p0Yao2TjypkYCRIffOzAggMmeMJ6Mk6f5Mw.woff
67 ms
xqOJHTQXG7RERN1MbBVVWg8czVG9nOkv3x2yf82eNGJffHzAggMmeMJ6Mk6f5MI.woff
118 ms
zvAajjeesqdZfnJOoq7z1JLQYm4vdLTS5mN9I9VH38wffwYAggMmeMJ6Mk6f5MS.woff
147 ms
45XkiDQJX8Xk3pNlEYa6lLIlW6DFBwQEDJjulzpSoDJffHDAggMmeMJ6Mk6f5MC.woff
155 ms
TPVEX8UCKXENc2yt5wEycRHA-QoIzRI7mro69Bf_AcvffODAggMmeMJ6Mk6f5MX.woff
177 ms
y93niMs6ZMB6Rz-dN9DqimcNtYIs5efQIfig5ebAAkqffO_AggMmeMJ6Mk6f5Mt.woff
178 ms
j4WMpF4tOy60tf9jJZAxCmszS5tzGcyWKeq8eDACARMffwOAggMmeMJ6Mk6f5gI.woff
169 ms
WidgetScript
435 ms
__utm.gif
58 ms
v.gif
44 ms
fontawesome-webfont.woff
367 ms
p.gif
125 ms
containersquare_61646d86.jpg&resolution=600x600&quality=90
580 ms
placeit-klijssen_34d37d9d.jpg&resolution=300x300&quality=95
263 ms
speakers_ff1f78bc.jpg&resolution=300x300&quality=95
237 ms
_WidgetJPCB0
98 ms
_WidgetJPCB1.js
34 ms
jquery.min.js
61 ms
147285691458255940421.js
8 ms
floro.nl accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
floro.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
Page has valid source maps
floro.nl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
NL
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Floro.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 Floro.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.
floro.nl
Open Graph data is detected on the main page of Floro. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: