plantspetitsfruits.com website review

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

The page has 3,407 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

28 images could be 999 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

About 546 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (Shopify, Google Tag Manager and Google CDN and others), adding 4.0 MB and 362 ms of main-thread time.

Shopify costs a phone 209 ms of main-thread work and 3.7 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 2.8 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

5 long tasks block the main thread while loading, the longest for 225 ms. During a long task the page ignores taps.

14 files are served with short cache lifetimes, so returning visitors download them again (222 KiB).

About 37 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

36 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

7 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 16.9 s. Good is under 3.8 s.

Visually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

The layout shifts by 0.139 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your homepage downloads 7.2 MB in 344 requests on a phone: images 4.8 MB (138), scripts 1.3 MB (86) and other files 916 KiB (85). Under 2 MB keeps phones on slow connections fast.

24 images are downloaded at several times the size a phone draws them, for example ALV-UjXE67m4KOEqdCxKDIhbIv_rlOlTIXUkikrem4oPdjqxfUOFnJR_ at 512 px wide, shown at 39 px. Resized copies would save about 1.6 MB.

31 images (2.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

12 images further down the page (826 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.04 g of CO₂e: 244.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

171 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

Your title is 86 characters, so Google will cut it off around 60: “Soft fruit Plant Wholesale Supplier Producer Price EU – Bairiverse - Econome à Légumes”.

Structured data found (LocalBusiness, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

Your <h1> is empty.

The homepage links to 137 pages on plantspetitsfruits.com and 2 external pages.

https://plantspetitsfruits.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://plantspetitsfruits.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://plantspetitsfruits.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://plantspetitsfruits.com/en/collections/nos-petits-fruits-vente-en-ligne, https://plantspetitsfruits.com/en/collections/nos-petits-fruits-vente-sur-devis, https://plantspetitsfruits.com/en/collections/petits-fruits-conditionnements-ideals-pour-la-plantation, https://plantspetitsfruits.com/en/collections/petits-fruits-conditionnements-ideals-pour-le-rempotage-et-lelevage-de-plants and https://plantspetitsfruits.com/en/collections/petits-fruits-conditionnements-ideals-pour-la-revente-en-pepinieres-et-jardineries use the same meta description. A description written for each page earns more clicks.

https://plantspetitsfruits.com/customer_authentication/redirect, https://plantspetitsfruits.com/en/collections/petits-fruits-conditionnements-ideals-pour-la-plantation, https://plantspetitsfruits.com/en/collections/petits-fruits-conditionnements-ideals-pour-le-rempotage-et-lelevage-de-plants, https://plantspetitsfruits.com/en/collections/petits-fruits-conditionnements-ideals-pour-la-revente-en-pepinieres-et-jardineries, https://plantspetitsfruits.com/en/collections/framboisiers-bio-et-conventionnels-de-qualite-pour-maraichers-professionnels and https://plantspetitsfruits.com/en/collections/nos-myrtilliers-bio-et-conventionnels-de-qualite-pour-maraichers-professionnels and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css?family=' from origin 'https://plantspetitsfruits.com' has…”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 1,843 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.