Website review, no card needed

groupe-gilbert.fr logo

groupe-gilbert.fr website review

Visit site (opens in a new tab)Reviewed 4 November 202643 issues · 83 checks

This review found 43 issues worth fixing on groupe-gilbert.fr, 10 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s1.4 sMay 16Oct 313.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.5 s
Oct 10, 20262.5 s
Oct 17, 20262.5 s
Oct 24, 20262.8 s
Oct 31, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
96 ms80 msMay 16Oct 3185 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202693 ms
May 23, 202688 ms
May 30, 202682 ms
Jun 6, 202682 ms
Jun 13, 202687 ms
Jun 20, 202682 ms
Jun 27, 202687 ms
Jul 4, 202685 ms
Jul 11, 202685 ms
Jul 18, 202689 ms
Jul 25, 202689 ms
Aug 1, 202691 ms
Aug 8, 202689 ms
Aug 15, 202688 ms
Aug 22, 202687 ms
Aug 29, 202685 ms
Sep 5, 202689 ms
Sep 12, 202691 ms
Sep 19, 202694 ms
Sep 26, 202690 ms
Oct 3, 202693 ms
Oct 10, 202688 ms
Oct 17, 202686 ms
Oct 24, 202689 ms
Oct 31, 202685 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of groupe-gilbert.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. groupe-gilbert.fr at 1.6 s1.6 s
  2. groupe-gilbert.fr at 3.1 s3.1 s
  3. groupe-gilbert.fr at 4.7 s4.7 s
  4. groupe-gilbert.fr at 6.3 s6.3 s
  5. groupe-gilbert.fr at 7.9 s7.9 s
  6. groupe-gilbert.fr at 9.4 s9.4 s
  7. groupe-gilbert.fr at 11.0 s11.0 s
  8. groupe-gilbert.fr at 12.6 s12.6 s

Speed

12 to fix67
  • Render-blocking requests

    1.8 s

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

  • Improve image delivery

    350 ms · 1.9 MB

    25 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Mobile performance score: 67

    67/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (ZenDesk, Didomi and Google Tag Manager and others), adding 838 KiB and 626 ms of main-thread time.

  • Font display

    700 ms

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

  • Use efficient cache lifetimes

    546 KiB

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

  • Reduce unused JavaScript

    488 KiB

    About 488 KiB of JavaScript is downloaded but never used on this page.

  • ZenDesk adds 333 ms

    333 ms

    ZenDesk costs a phone 333 ms of main-thread work and 402 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.

  • Reduce unused CSS

    300 ms · 68 KiB

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

  • 7 long tasks on the main thread

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

  • Main-thread work: 3.3 s

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

  • 2,840 HTML elements

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

  • Legacy JavaScript

    10 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 97 ms

    97 ms

    Your server sent the HTML in 97 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    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-user FCP: 3.6 s

    3.6 s

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

  • Real-user TTFB: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Time to Interactive: 22.3 s

    22.3 s

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

  • Speed Index: 13.3 s

    13.3 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

  • Real-user CLS: 0.17

    0.17

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

  • Largest content (LCP) got 79% slower for real visitors

    +79%

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

  • 74 images without width and height

    74 images have no width and height attributes, so the layout jumps as each one loads.

  • Total Blocking Time: 560 ms

    560 ms

    Scripts block taps and scrolling for 560 ms in total while the page loads. Good is under 200 ms.

  • Cumulative Layout Shift: 0.14

    0.14

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -4%

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

2 checks passed
  • Real-user INP: 94 ms

    94 ms

    Real visitors wait 94 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest Contentful Paint: 2.4 s

    2.4 s

    Your largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.

Images and page weight

4 to fix43
  • Page weight: 5.9 MB in 157 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 157 requests on a phone: images 4.7 MB (112), scripts 982 KiB (27) and fonts 149 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 23 images in older formats

    23 images (1.6 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.

  • 14 images below the first screen load straight away

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

  • 3 images far larger than shown

    327 KiB

    3 images are downloaded at several times the size a phone draws them, for example lel-logo_p2152_2023-1-scaled.jpg at 2,560 px wide, shown at 100 px. Resized copies would save about 327 KiB.

  • About 1.7 g of CO₂ per visit

    1.67 g

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

Accessibility

7 to fixGoogle 7591
  • Certain ARIA roles must contain particular children (1 element)

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

  • 22 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 63 links without text

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

  • 8 text elements with low contrast

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

  • 1 tap target too small

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

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 45 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is long (211 characters)

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

  • 325 internal links, 13 external

    The homepage links to 325 pages on groupe-gilbert.fr and 13 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “La santé commence avec vous”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Gilbert : groupe pharmaceutique et cosmétique”.

  • Canonical URL set

    The canonical URL is https://www.groupe-gilbert.fr/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.groupe-gilbert.fr/sitemap.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • Some text only appears after JavaScript runs

    57%

    The HTML your server sends has 3,282 of the 5,761 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://www.groupe-gilbert.fr/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

1 to fix95
  • 7 pages without a meta description

    https://www.groupe-gilbert.fr/groupe/gouvernance, https://www.groupe-gilbert.fr/groupe/sponsoring, https://www.groupe-gilbert.fr/mecenat, https://www.groupe-gilbert.fr/engagements, https://www.groupe-gilbert.fr/activite/pharmaceutique and https://www.groupe-gilbert.fr/faconnage/notre-expertise-cosmetique-sur-mesure and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://www.groupe-gilbert.fr/groupe/nos-marques, https://www.groupe-gilbert.fr/engagements and https://www.groupe-gilbert.fr/activite/cosmetique took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'getBoundingClientRect')”.

  • 4 distorted images

    4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    13 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No risk reducer

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

  • About 5,761 words of copy

    The homepage carries about 5,761 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More →”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 2 cookies set on arrival

    2

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

  • 6 other companies contacted

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

1 checks passed
  • Consent tool: Didomi

    A consent management tool (Didomi) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at groupe-gilbert.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
OVHcloud

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on groupe-gilbert.fr, including 24 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25