greenyellow.com website review

14 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.4 s faster on a phone.

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

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

5 third-party services load with your homepage (Usercentrics CMP, Google Tag Manager and Matomo and others), adding 5.5 MB and 441 ms of main-thread time.

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

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

Azure Web Services costs a phone 0 ms of main-thread work and 5.2 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.

Usercentrics CMP costs a phone 310 ms of main-thread work and 192 KiB 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.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).

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

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.

Real visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.

Your largest element takes 35.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Accueil Activez votre bouclier énergétique, grâce aux offre…”.

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

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

The first text or image appears after 3.8 s on a phone. Good is under 1.8 s.

Real visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 85 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.2 MB in 141 requests on a phone: images 5.2 MB (37), other files 755 KiB (12) and scripts 662 KiB (53). Under 2 MB keeps phones on slow connections fast.

6 images (612 KiB) 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

2 images have no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

Your title is 103 characters, so Google will cut it off around 60: “GreenYellow » Partenaire industriel, orchestrateur de la décarbonation et de l'électrific…”.

Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.

There is no robots.txt at greenyellow.com/robots.txt, the first file search crawlers ask for.

The homepage links to 128 pages on greenyellow.com and 24 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.greenyellow.com/notre-organisation is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.greenyellow.com/notre-organisation/partenariats/rexel has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.greenyellow.com/presse-fr, https://www.greenyellow.com/notre-organisation/partenariats/schneider-electric, https://www.greenyellow.com/notre-organisation/partenariats/rexel, https://www.greenyellow.com/actionnariat, https://www.greenyellow.com/notre-organisation/notre-equipe-dirigeante and https://www.greenyellow.com/notre-organisation/otmane-hajji and 1 other took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 13 fields (8 required). Every extra field lowers completion.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 436 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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