1.8 sec in total
51 ms
1.4 sec
298 ms
Welcome to fertiligene.com homepage info - get ready to check Fertiligene best content right away, or after learning these important things about fertiligene.com
« Ferti, Ferti, Fertiligène » … Plus de 15 ans déjà que cette ritournelle accompagne les publicités de la marque… Mais cela fait bien plus longtemps (30 ans !) que Fertiligène dispense ses conseils a...
Visit fertiligene.comWe analyzed Fertiligene.com page load time and found that the first response time was 51 ms and then it took 1.7 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.
fertiligene.com performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value9.6 s
0/100
25%
Value7.3 s
29/100
10%
Value6,700 ms
0/100
30%
Value0.023
100/100
15%
Value23.8 s
1/100
10%
51 ms
253 ms
84 ms
171 ms
169 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fertiligene.com, 73% (49 requests) were made to Lapausejardin.fr and 4% (3 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (512 ms) relates to the external source Lapausejardin.fr.
Page size can be reduced by 871.5 kB (57%)
1.5 MB
664.4 kB
In fact, the total size of Fertiligene.com main page is 1.5 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. Javascripts take 903.3 kB which makes up the majority of the site volume.
Potential reduce by 31.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 31.8 kB or 77% of the original size.
Potential reduce by 10.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. Fertiligene images are well optimized though.
Potential reduce by 616.2 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 616.2 kB or 68% of the original size.
Potential reduce by 212.9 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. Fertiligene.com needs all CSS files to be minified and compressed as it can save up to 212.9 kB or 84% of the original size.
Number of requests can be reduced by 34 (58%)
59
25
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fertiligene. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
fertiligene.com
51 ms
fertiligene
253 ms
css_fwmyaQ94GYCgLOhxI65OkA88tGta-ImMjPBVZWMpCgU.css
84 ms
css_SY72-aTfciewq3b-XV5E2E0mEOszVBqfambQhclGUGc.css
171 ms
css_suth5HOFpnEETaZCjS34IgRTMNYEm9iLcVqPDR1do2Q.css
169 ms
css
26 ms
css_tqJ35hJ1PX0mhU84cebQl8AA4MOPEQwGumGhP4-Ioh4.css
246 ms
js_0gj6QcpfRH2jzTbCQqf7kEkm4MXY0UA_sRhwPc8jC1o.js
276 ms
js_6_eJ0bghsmepxp682HHRhLenGnM9jsi3YVtrs5pvASw.js
275 ms
js_st8IGg4lLvdTYW4ejMyJe6X_JeqUCyQQne9qHhBLEsU.js
170 ms
js_WJIqUcaRuGKh4EHoKofhC-TyXEMr3AASb57rLow8NTA.js
312 ms
js_V2vdFa4_dhrmMV8EEk96PXqLoF02abGun0cS0OtCKHg.js
321 ms
js_g5h9j0jgDUpbOCNrZSnhDeRogVrog3bsLPSjDUAam4k.js
326 ms
TAG_passage.js
167 ms
require.js
362 ms
js_mXyjX56ZvPA0dddbJtx2TzxjBfQUabo1mu4NXgEzYbw.js
363 ms
js_li5UmeNFLCvxgMRYbuWzmEvNq1677X7MDRQTo_OpfHA.js
364 ms
js_mq_iaKIjU8ux4kOehVHul1VFsR6FIVJYcnp-2UC9HF0.js
363 ms
js_WaJdWEH8ppwLgtnUW0EwS-weVJjVzlTpQCPV6L1in8E.js
364 ms
post-widget.js
153 ms
fr_ns0001_1_.jpg
328 ms
gamme_terreau_fertiligene.jpg
148 ms
desherbant-fertiligene-tube-lpg.jpg
147 ms
gamme-aceta-fruits-legumes-fertiligene-lpj.jpg
228 ms
paillage-magic-potager-lpj.jpg
227 ms
engrais_gazon_reverdissant_green_max_80m2_8108_fertiligene.jpg
227 ms
patch_magic_1kg_9375_fertiligene.jpg
226 ms
terreau_magic_universel_compresse_17l_8463_fertiligene.jpg
225 ms
terreau_horticole_70l_9639_fertiligene.jpg
260 ms
desherbant_anti-repousse_cours_allees_terrasses_240m2_9142_fertiligene.jpg
262 ms
insecticide_systemique_350ml_9531_fertiligene.jpg
263 ms
paillage_magic_17l_8907_fertiligene.jpg
262 ms
gtm.js
139 ms
logo_LPJ.png
239 ms
arrow-up.svg
303 ms
arrow-left.svg
308 ms
pastille-new_small.png
316 ms
social-google-plus.svg
309 ms
social-pinterest.svg
313 ms
social-facebook.svg
378 ms
social-youtube.svg
383 ms
social-twitter.svg
387 ms
quick-form-submit.svg
388 ms
brands.png
387 ms
common.js
27 ms
util.js
28 ms
geocoder.js
23 ms
drupal-error.png
272 ms
fertiligene
345 ms
2D2466_4_0.woff
506 ms
2D2466_5_0.woff
512 ms
MViwy4K6e56oHcyeMzjbCQ.ttf
73 ms
F-uvpIj1hF17IDyvQvI50Q.ttf
73 ms
main.js
343 ms
analytics.js
54 ms
253 ms
AuthenticationService.Authenticate
40 ms
GeocodeService.Search
45 ms
collect
24 ms
collect
75 ms
jquery.min.js
64 ms
responsivenav.js
87 ms
modernizr-2.8.3.min.js
87 ms
responsive-slider.js
172 ms
cookie.js
91 ms
icon32-sprite.svg
130 ms
status
51 ms
fertiligene.com 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.
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
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.
fertiligene.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fertiligene.com 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
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fertiligene.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Fertiligene.com 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.
fertiligene.com
Open Graph data is detected on the main page of Fertiligene. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: