Website review, no card needed

gmh2i.com logo

gmh2i.com website review

Visit site (opens in a new tab)Reviewed 9 November 202633 issues · 75 checks

This review found 33 issues worth fixing on gmh2i.com, 11 of them high impact, across 75 checks. The most urgent: improve image delivery. 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

Full-page screenshot of gmh2i.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gmh2i.com at 0.7 s0.7 s
  2. gmh2i.com at 1.5 s1.5 s
  3. gmh2i.com at 2.2 s2.2 s
  4. gmh2i.com at 2.9 s2.9 s
  5. gmh2i.com at 3.6 s3.6 s
  6. gmh2i.com at 4.4 s4.4 s
  7. gmh2i.com at 5.1 s5.1 s
  8. gmh2i.com at 5.8 s5.8 s

Speed

5 to fix56
  • Improve image delivery

    3.0 s · 2.5 MB

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

  • Render-blocking requests

    2.2 s

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

  • Mobile performance score: 56

    56/100

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

  • Reduce unused CSS

    450 ms · 92 KiB

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

  • Reduce unused JavaScript

    300 ms · 61 KiB

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

  • 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 80 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    36 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (36 KiB).

  • Legacy JavaScript

    15 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (divisupply.com and Google Fonts), adding 89 KiB and 0 ms of main-thread time.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 103 ms

    103 ms

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

Core Web Vitals

6 to fix55
  • Largest Contentful Paint: 13.3 s

    13.3 s

    Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (5.4 s).

  • Speed Index: 11.6 s

    11.6 s

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

  • Time to Interactive: 13.8 s

    13.8 s

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

  • Cumulative Layout Shift: 0.183

    0.183

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 5 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 30 ms

    30 ms

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

Images and page weight

6 to fix33
  • 2 images over 500 KB

    2 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    2.0 MB

    2 images are downloaded at several times the size a phone draws them, for example MOCKUP-Site-2i_2025.png at 5,834 px wide, shown at 312 px. Resized copies would save about 2.0 MB.

  • Page weight: 3.3 MB in 56 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 56 requests on a phone: images 2.8 MB (23), scripts 189 KiB (11) and fonts 172 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (1.9 MB) is 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.

  • 1 image below the first screen load straight away

    1 image further down the page (1.9 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    IMAGE-HOME-1-_1_.webp 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.9 g of CO₂ per visit

    0.95 g

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

Accessibility

4 to fixGoogle 8695
  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

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

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

  • Zoom is disabled

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

  • 2 links without text

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 35 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 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 10085
  • Title is short (15 characters)

    Your title is only 15 characters: “Accueil - GMH2i”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Rationnalisez la gestion et le contrôle de l’accu…” and “Les solutions au servicede l’identification et de…”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 88 internal links, 6 external

    The homepage links to 88 pages on gmh2i.com and 6 external pages.

5 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “GMH 2i édite et intègre ses solutions logicielles standards et spécifiques pour simplifier la coordination des opératio…”.

  • Canonical URL set

    The canonical URL is https://gmh2i.com/.

  • Structured data in place

    Structured data found: Article, Organization, Person, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://tempo11.target-web.info/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (1 of 6 facts)

    Your Organization JSON-LD is missing url, logo, 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.

  • No llms.txt

    There is no https://gmh2i.com/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 (878 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix62
  • 1 linked page is broken

    Your homepage links to https://gmh2i.com/references, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://gmh2i.com/solutions and https://gmh2i.com/solutions/id-reader all use the title “Solutions - GMH2i”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://gmh2i.com/solutions and https://gmh2i.com/solutions/id-reader use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://gmh2i.com/solutions/id-reader, whose canonical is https://gmh2i.com/solutions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page slow to respond

    https://gmh2i.com/solutions took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Every page has a meta description

    All 14 pages that loaded have a meta description.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

    5 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://gmh2i.com/wp-content/themes/molti/style.css' because its MIME type ('text/html') i…”.

1 checks passed
  • 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 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.

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

    The homepage carries about 377 words of visible text.

4 checks passed
  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 customer or partner logo and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 gmh2i.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
OVHcloud

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 gmh2i.com, including 11 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