3.6 sec in total
241 ms
3.2 sec
231 ms
Visit florum.fr now to see the best up-to-date Florum content for France and also check out these interesting facts you probably never knew about florum.fr
Florum, acheter plantes et végétaux pour vos jardins, le meilleur choix, la meilleure qualité pour l'achat jardin. Florum.
Visit florum.frWe analyzed Florum.fr page load time and found that the first response time was 241 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
florum.fr performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value9.1 s
1/100
25%
Value7.4 s
27/100
10%
Value240 ms
86/100
30%
Value0.201
62/100
15%
Value8.8 s
35/100
10%
241 ms
541 ms
78 ms
155 ms
158 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 83% of them (52 requests) were addressed to the original Florum.fr, 8% (5 requests) were made to Static.florum.fr and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Static.florum.fr.
Page size can be reduced by 333.3 kB (50%)
666.7 kB
333.4 kB
In fact, the total size of Florum.fr main page is 666.7 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. 40% of websites need less resources to load. Images take 276.5 kB which makes up the majority of the site volume.
Potential reduce by 88.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 30.6 kB, which is 31% 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 88.2 kB or 88% of the original size.
Potential reduce by 29.6 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, Florum needs image optimization as it can save up to 29.6 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 163.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 163.5 kB or 72% of the original size.
Potential reduce by 52.0 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. Florum.fr needs all CSS files to be minified and compressed as it can save up to 52.0 kB or 85% of the original size.
Number of requests can be reduced by 13 (23%)
57
44
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Florum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
florum.fr
241 ms
www.florum.fr
541 ms
reset.css
78 ms
text.css
155 ms
960_24_col.css
158 ms
florum.css
161 ms
jquery.megamenu.css
156 ms
slidedeck.skin.css
162 ms
jquery.fancybox.css
161 ms
jquery.modalbox.css
231 ms
lib.js
386 ms
prototype.js
317 ms
opcheckout.js
236 ms
jquery.modalbox-basic.css
79 ms
jquery.modalbox-skin-default.css
79 ms
ga.js
16 ms
analytics.js
17 ms
11000photos.jpg
956 ms
h_fond.png
131 ms
logo_Florum.png
134 ms
garanties.png
134 ms
nophoto_SQUARE.gif
134 ms
3421-Azalea-mollis-Persil.jpg
135 ms
3401-Azalea-White-Lady.jpg
135 ms
3386-Azalea-Macrostemon.jpg
155 ms
9694-Azalea-Hino-Crimson.jpg
158 ms
13343-Rosa-Kadora-.jpg
158 ms
13342-Rosa-Audacieuse-21-.jpg
156 ms
13341-Rosa-Jubile-Laperriere-150-ans-.jpg
159 ms
13340-Rosa-Parfum-Royal-.jpg
158 ms
13339-Rosa-Sacem-.jpg
231 ms
13338-Rosa-Souvenir-de-Josephine-.jpg
233 ms
13337-Rosa-Isalia-.jpg
234 ms
13336-Rosa-Plein-Sud-.jpg
234 ms
13335-Rosa-Johan-Jongkind-.jpg
235 ms
13334-Rosa-Xpert-.jpg
234 ms
13333-Rosa-Bobino-.jpg
308 ms
13332-Rosa-Bertrand-Amoussou-.jpg
310 ms
bottomservices.png
311 ms
bnp.jpg
311 ms
paypal.gif
312 ms
colissimo48.gif
313 ms
cc.png
385 ms
Bonnes_affaire_fruitiers_2015-small.jpg
951 ms
Bonnes_affaire_palmier_436.jpg
1132 ms
Bonnes_affaire_camelia_small.jpg
1797 ms
Bonnes_affaire_rosiers_2015-small.jpg
1953 ms
myaccountwidget
585 ms
panier_bground.png
379 ms
1037 ms
fond_input_search.png
359 ms
fond_input_search_button.png
360 ms
fond_input_nl.png
419 ms
newsletter_input_search_button.png
420 ms
collect
52 ms
38 ms
__utm.gif
13 ms
bg_shadows_left.png
338 ms
bg_shadows_right.png
339 ms
ajax-loader.gif
412 ms
house20.jpg
413 ms
18 ms
heart.png
79 ms
florum.fr accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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>).
florum.fr 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
florum.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Image elements do not have [alt] attributes
FR
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Florum.fr can be misinterpreted by Google and other search engines. Our service has detected that French 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 Florum.fr 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.
florum.fr
Open Graph description is not detected on the main page of Florum. 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: