Website review, no card needed

gbh.fr logo

gbh.fr website review

Visit site (opens in a new tab)Reviewed 1 November 202633 issues · 76 checks

This review found 33 issues worth fixing on gbh.fr, 12 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
4.5 s2.6 sMay 9Oct 243.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20263.0 s
Jun 6, 20262.9 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.1 s
Jul 4, 20263.4 s
Jul 11, 20263.6 s
Jul 18, 20263.8 s
Jul 25, 20264.2 s
Aug 1, 20264.2 s
Aug 8, 20264.3 s
Aug 15, 20264.3 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.8 s
Oct 17, 20263.7 s
Oct 24, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
148 ms112 msMay 9Oct 24131 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026131 ms
May 16, 2026129 ms
May 23, 2026135 ms
May 30, 2026135 ms
Jun 6, 2026136 ms
Jun 13, 2026137 ms
Jun 20, 2026137 ms
Jun 27, 2026130 ms
Jul 4, 2026137 ms
Jul 11, 2026138 ms
Jul 18, 2026143 ms
Jul 25, 2026144 ms
Aug 1, 2026132 ms
Aug 8, 2026129 ms
Aug 15, 2026127 ms
Aug 22, 2026129 ms
Aug 29, 2026129 ms
Sep 5, 2026130 ms
Sep 12, 2026138 ms
Sep 19, 2026138 ms
Sep 26, 2026129 ms
Oct 3, 2026125 ms
Oct 10, 2026121 ms
Oct 17, 2026116 ms
Oct 24, 2026131 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 gbh.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gbh.fr at 0.4 s0.4 s
  2. gbh.fr at 0.8 s0.8 s
  3. gbh.fr at 1.2 s1.2 s
  4. gbh.fr at 1.6 s1.6 s
  5. gbh.fr at 2.0 s2.0 s
  6. gbh.fr at 2.4 s2.4 s
  7. gbh.fr at 2.8 s2.8 s
  8. gbh.fr at 3.1 s3.1 s

Speed

4 to fix50
  • Use efficient cache lifetimes

    4.5 s · 1.6 MB

    42 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

  • Improve image delivery

    3.8 s · 1.1 MB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 50

    50/100

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

  • Reduce unused JavaScript

    195 KiB

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

  • Reduce unused CSS

    150 ms · 33 KiB

    About 33 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Maps, AddToAny and Adobe TypeKit and others), adding 413 KiB and 131 ms of main-thread time.

  • Font display

    100 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 85 ms. During a long task the page ignores taps.

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • 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.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 232 ms of it running JavaScript. That is comfortably low.

  • Server response: 34 ms

    34 ms

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

Core Web Vitals

10 to fix67
  • 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.

  • Cumulative Layout Shift: 1.056

    1.056

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

  • Largest Contentful Paint: 6.9 s

    6.9 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

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

    +33%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Time to Interactive: 6.9 s

    6.9 s

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

  • Speed Index: 4.4 s

    4.4 s

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -5%

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

4 checks passed
  • Real-user INP: 136 ms

    136 ms

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

  • Real-user CLS: 0.08

    0.08

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 35 ms

    35 ms

    Scripts block the page for only 35 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix64
  • 6 images far larger than shown

    705 KiB

    6 images are downloaded at several times the size a phone draws them, for example header5_en.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 705 KiB.

  • 7 images in older formats

    7 images (1.4 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.

  • An image on the first screen is lazy-loaded

    header5_en.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.6 g of CO₂ per visit

    0.56 g

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

1 checks passed
  • Page weight: 2.0 MB in 55 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 55 requests on a phone: images 1.3 MB (18), scripts 473 KiB (22) and fonts 128 KiB (5). That is a lean page.

Accessibility

5 to fixGoogle 9194
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • All page content should be contained by landmarks (2 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 87 internal links, 28 external

    The homepage links to 87 pages on gbh.fr and 28 external pages.

5 checks passed
  • Meta description: 146 characters

    Your meta description is 146 characters: “GBH is present in the ultra-marine territories and in Africa in Automotive Distribution, Mass Distribution, Industrial …”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Cultivating the entrepreneurial spirit”.

  • Canonical URL set

    The canonical URL is http://www.gbh.fr/en.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.gbh.fr/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.gbh.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.

2 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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (633 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://www.gbh.fr/our-group, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://www.gbh.fr/en and https://www.gbh.fr/en/our-activities all use the title “Cultivating the entrepreneurial spirit”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.gbh.fr/en/news-press/press-contact and https://www.gbh.fr/en/sitemap have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.gbh.fr/fr has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    30 of 32 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67
  • No call to action on the first screen

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

  • No social proof

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

  • 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 285 words of copy

    The homepage carries about 285 words of visible text.

4 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Join us”, “Press contact” and “Contact”.

  • 1 short form

    A short form (1 field at most) is 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

  • 4 cookies set on arrival

    4

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

  • No consent tool detected

    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.

  • 4 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 gbh.fr, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Analytics
Google Tag Manager
Hosting
AWS

Company

Founded
1960
Headquarters
Le Lamentin

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on gbh.fr, including 14 speed issues, 3 SEO issues 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