Tools & Wizards About Us
plantesetjardins.com screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

plantesetjardins.com

Jardinerie Gamm vert - Plantes, animalerie & outils de jardinage - Gamm vert

Page Load Speed

4.6 sec in total

First Response

964 ms

Resources Loaded

3 sec

Page Rendered

634 ms

plantesetjardins.com screenshot

About Website

Visit plantesetjardins.com now to see the best up-to-date Plantes Etjardins content and also check out these interesting facts you probably never knew about plantesetjardins.com

Jardinerie en ligne : vente de plantes, outils de jardinage, tondeuses à gazon, abris, serres, salon de jardin, accessoires animaux. Retrouvez tous nos conseils d'experts pour fleurir, entretenir et a...

Visit plantesetjardins.com

Key Findings

We analyzed Plantesetjardins.com page load time and found that the first response time was 964 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

plantesetjardins.com performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

www.gammvert.fr

964 ms

gtm-script.js

249 ms

entry.7DlJMKrn.css

563 ms

default.CBlHkN7J.css

406 ms

EnsArticleCategorySelector.CSxgugQ6.css

328 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Plantesetjardins.com, 3% (1 request) were made to Assets.gammvert.fr. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Gammvert.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 200.8 kB (77%)

Content Size

260.6 kB

After Optimization

59.9 kB

  • HTML
  • Images

In fact, the total size of Plantesetjardins.com main page is 260.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. 20% of websites need less resources to load. HTML takes 258.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 200.7 kB

  • Original 258.4 kB
  • After minification 254.6 kB
  • After compression 57.7 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 200.7 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 24 B

  • Original 2.2 kB
  • After minification 2.2 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. Plantes Etjardins images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 22 (85%)

Requests Now

26

After Optimization

4

  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantes Etjardins. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.gammvert.fr

www.gammvert.fr

964 ms

gtm-script.js

gtm-script.js

249 ms

entry.7DlJMKrn.css

entry.7DlJMKrn.css

563 ms

default.CBlHkN7J.css

default.CBlHkN7J.css

406 ms

EnsArticleCategorySelector.CSxgugQ6.css

EnsArticleCategorySelector.CSxgugQ6.css

328 ms

DsEnsCard.BdFGTgj-.css

DsEnsCard.BdFGTgj-.css

330 ms

EnsArticle.B24FTrsF.css

EnsArticle.B24FTrsF.css

342 ms

DsEnsPaginationNoScript.BI2Hk85D.css

DsEnsPaginationNoScript.BI2Hk85D.css

410 ms

DsEnsSeo.CMTiPRAe.css

DsEnsSeo.CMTiPRAe.css

411 ms

DsEnsNavigationHorizontal.DmXg2i18.css

DsEnsNavigationHorizontal.DmXg2i18.css

424 ms

DsEnsBackgroundHeader.DrodtJaW.css

DsEnsBackgroundHeader.DrodtJaW.css

487 ms

DsEnsContent.CrM5pqsA.css

DsEnsContent.CrM5pqsA.css

490 ms

DsEnsSlideshow.CuFSGJwf.css

DsEnsSlideshow.CuFSGJwf.css

491 ms

EnsGlobalAlert.DN15TqR7.css

EnsGlobalAlert.DN15TqR7.css

505 ms

EnsFooter.B5Vzqzz5.css

EnsFooter.B5Vzqzz5.css

551 ms

footer-injection.DFkKMNLJ.css

footer-injection.DFkKMNLJ.css

568 ms

DsEnsNoResults.tDsMi68p.css

DsEnsNoResults.tDsMi68p.css

570 ms

EnsStoreLocatorCardSchedule.D20kTfKX.css

EnsStoreLocatorCardSchedule.D20kTfKX.css

572 ms

EnsStoreLocatorWarningModal.BRwT-TZM.css

EnsStoreLocatorWarningModal.BRwT-TZM.css

589 ms

DsEnsRichtext.BJU_F1XW.css

DsEnsRichtext.BJU_F1XW.css

631 ms

main-navigation-injection.BeLBYerJ.css

main-navigation-injection.BeLBYerJ.css

641 ms

home-injection.CBXUKfYJ.css

home-injection.CBXUKfYJ.css

649 ms

EnsStoreLocatorModal.B31HadVf.css

EnsStoreLocatorModal.B31HadVf.css

650 ms

EnsStoreLocatorCard.B8DKKbyW.css

EnsStoreLocatorCard.B8DKKbyW.css

652 ms

common-spotlight.CLKsL-2u.css

common-spotlight.CLKsL-2u.css

672 ms

By5F4Ffx.js

By5F4Ffx.js

2213 ms

logo-gamm-vert-mobile.png.png

logo-gamm-vert-mobile.png.png

32 ms

Poppins-Bold.BruXqHNc.woff

Poppins-Bold.BruXqHNc.woff

160 ms

Poppins-Regular.DGtWxk2d.woff

Poppins-Regular.DGtWxk2d.woff

241 ms

Accessibility Review

plantesetjardins.com accessibility score

77

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

plantesetjardins.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

plantesetjardins.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantesetjardins.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 Plantesetjardins.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.

Social Sharing Optimization

plantesetjardins.com

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: