1.9 sec in total
187 ms
1.6 sec
190 ms
Click here to check amazing Mauvaise Herbe content. Otherwise, check out these important facts you probably never knew about mauvaise-herbe.fr
Un site pour en apprendre plus sur les mauvaises herbes : Les reconnaître ? Apprendre ce qu'elle nous indique sur l'état du jardin et des sols, etc...
Visit mauvaise-herbe.frWe analyzed Mauvaise-herbe.fr page load time and found that the first response time was 187 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.
mauvaise-herbe.fr performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.3 s
41/100
25%
Value4.4 s
74/100
10%
Value10 ms
100/100
30%
Value0.133
81/100
15%
Value5.5 s
70/100
10%
187 ms
278 ms
194 ms
162 ms
168 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that 84% of them (31 requests) were addressed to the original Mauvaise-herbe.fr, 5% (2 requests) were made to Google-analytics.com and 5% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (517 ms) belongs to the original domain Mauvaise-herbe.fr.
Page size can be reduced by 254.7 kB (59%)
434.6 kB
179.8 kB
In fact, the total size of Mauvaise-herbe.fr main page is 434.6 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. Javascripts take 268.4 kB which makes up the majority of the site volume.
Potential reduce by 12.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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 12% 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 12.8 kB or 72% of the original size.
Potential reduce by 14.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. Obviously, Mauvaise Herbe needs image optimization as it can save up to 14.5 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 170.8 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 170.8 kB or 64% of the original size.
Potential reduce by 56.7 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. Mauvaise-herbe.fr needs all CSS files to be minified and compressed as it can save up to 56.7 kB or 80% of the original size.
Number of requests can be reduced by 23 (70%)
33
10
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mauvaise Herbe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
mauvaise-herbe.fr
187 ms
www.mauvaise-herbe.fr
278 ms
wp-emoji-release.min.js
194 ms
styles.css
162 ms
prettyPhoto.css
168 ms
style.css
177 ms
colorbox.css
180 ms
jquery.js
517 ms
jquery-migrate.min.js
250 ms
jquery.prettyPhoto.js
341 ms
settings.prettyPhoto.js
277 ms
jquery.form.min.js
359 ms
scripts.js
285 ms
jquery.colorbox.1.5.9.js
416 ms
css
27 ms
reset.css
192 ms
template.css
200 ms
settings.css
251 ms
button.css
275 ms
icons.css
283 ms
widget.css
289 ms
blog.css
323 ms
comments.css
333 ms
forms.css
364 ms
main.css
372 ms
ga.js
61 ms
background.png
272 ms
social.png
112 ms
menu.lateral.bkg.png
94 ms
menu.top.bkg.png
95 ms
menu.bottom.bkg.png
90 ms
content.icons.png
107 ms
search.png
180 ms
piwik.js
497 ms
YDAoLskQQ5MOAgvHUQCcLbvy90DtE_Pg_qiF9bHvTzw.ttf
24 ms
UyYrYy3ltEffJV9QueSi4UpeNX8RPf6i6WQfJWyCWEs.ttf
25 ms
__utm.gif
12 ms
mauvaise-herbe.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.
mauvaise-herbe.fr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
mauvaise-herbe.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Mauvaise-herbe.fr 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 Mauvaise-herbe.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.
mauvaise-herbe.fr
Open Graph description is not detected on the main page of Mauvaise Herbe. 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: