Website review, no card needed

kleegroup.com logo

kleegroup.com website review

Visit site (opens in a new tab)Reviewed 30 October 202618 issues · 70 checks

This review found 18 issues worth fixing on kleegroup.com, 2 of them high impact, across 70 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
918 ms530 msMay 9Oct 24807 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026628 ms
May 16, 2026631 ms
May 23, 2026655 ms
May 30, 2026704 ms
Jun 6, 2026720 ms
Jun 13, 2026715 ms
Jun 20, 2026623 ms
Jun 27, 2026647 ms
Jul 4, 2026640 ms
Jul 11, 2026594 ms
Jul 18, 2026656 ms
Jul 25, 2026575 ms
Aug 1, 2026582 ms
Aug 8, 2026719 ms
Aug 15, 2026770 ms
Aug 22, 2026807 ms
Aug 29, 2026873 ms
Sep 5, 2026870 ms
Sep 12, 2026677 ms
Sep 19, 2026672 ms
Sep 26, 2026641 ms
Oct 3, 2026611 ms
Oct 10, 2026678 ms
Oct 17, 2026791 ms
Oct 24, 2026807 ms
Real-visitor tap response (INP)75th percentile, phones
92 ms68 msMay 9Oct 2485 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202674 ms
May 16, 202675 ms
May 23, 202679 ms
May 30, 202674 ms
Jun 6, 202676 ms
Jun 13, 202677 ms
Jun 20, 202676 ms
Jun 27, 202676 ms
Jul 4, 202676 ms
Jul 11, 202676 ms
Jul 18, 202679 ms
Jul 25, 202678 ms
Aug 1, 202676 ms
Aug 8, 202678 ms
Aug 15, 202671 ms
Aug 22, 202671 ms
Aug 29, 202678 ms
Sep 5, 202689 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202686 ms
Oct 10, 202683 ms
Oct 17, 202685 ms
Oct 24, 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 kleegroup.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kleegroup.com at 0.4 s0.4 s
  2. kleegroup.com at 0.8 s0.8 s
  3. kleegroup.com at 1.1 s1.1 s
  4. kleegroup.com at 1.5 s1.5 s
  5. kleegroup.com at 1.9 s1.9 s
  6. kleegroup.com at 2.3 s2.3 s
  7. kleegroup.com at 2.6 s2.6 s
  8. kleegroup.com at 3.0 s3.0 s

Speed

2 to fix91
  • Render-blocking requests

    1.1 s

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

  • Font display

    750 ms

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

  • Improve image delivery

    250 ms · 37 KiB

    1 image could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Reduce unused CSS

    21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page.

  • 2 third-party services on the page

    2 third-party services load with your homepage (smart-data-systems.com and eqy.link), adding 12 KiB and 13 ms of main-thread time.

  • Use efficient cache lifetimes

    11 KiB

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

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.2 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest content (LCP) got 27% slower for real visitors

    +27%

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

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

  • Cumulative Layout Shift: 0.111

    0.111

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

  • 11 images without width and height

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

  • Tap response (INP) got 14% slower for real visitors

    +14%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 78 ms

    78 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

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

  • First Contentful Paint: 1.7 s

    1.7 s

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

  • Time to Interactive: 2.4 s

    2.4 s

    The page is fully interactive after 2.4 s.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

2 to fix86
  • An image on the first screen is lazy-loaded

    SITE WEB text and image (moyenne) (16).jpg.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).

  • 1 image far larger than shown

    7 KiB

    1 image is downloaded at several times the size a phone draws it, for example SITE WEB text and image (moyenne) (16).jpg.webp at 1,045 px wide, shown at 324 px. Resized copies would save about 7 KiB.

  • 1 image in older formats

    1 image (56 KiB) 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.

  • About 0.06 g of CO₂ per visit

    0.06 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.06 g of CO₂e: 7.8 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: 234 KiB in 22 requests

    234 KiB

    Your homepage downloads 234 KiB in 22 requests on a phone: images 136 KiB (11), scripts 41 KiB (6) and HTML 27 KiB (1). That is a lean page.

Accessibility

1 to fixGoogle 9699
  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 45 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: 45 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is long (82 characters)

    Your title is 82 characters, so Google will cut it off around 60: “Accueil | Klee Group : Créateur de solutions ! Conseil, Intégration, TMA, Software”.

  • 10 H1 headlines

    There are 10 <h1> headlines (“Créateur de solutions digitales métier”, “"La fabrication du code, angle mort de la souvera…” and “"Pari ETI : Patrice Bégay reçoit Frédéric Fritsch…”). One clear main headline is easier for people and search engines.

  • 49 internal links, 19 external

    The homepage links to 49 pages on kleegroup.com and 19 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Klee Group conçoit, développe et invente des solutions digitales métier sur-mesure. Nos experts et consultants accompag…”.

  • Canonical URL set

    The canonical URL is https://www.kleegroup.com/fr/accueil.

  • Structured data in place

    Structured data found: 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.kleegroup.com/default/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.kleegroup.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 (393 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://www.kleegroup.com/fr/rse, https://www.kleegroup.com/fr/contact, https://www.kleegroup.com/fr/recherche, https://www.kleegroup.com/fr/service/kleeai and https://www.kleegroup.com/fr/service/solutions-collaboratives-atlassian have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

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

  • 2 pages with very little text

    https://www.kleegroup.com/fr/recherche and https://www.kleegroup.com/en have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 405 words of visible text.

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact”.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 2 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Kleegroup

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 18 issues on kleegroup.com, including 6 speed issues, 2 SEO issues and 4 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