Website review, no card needed

clemenceconsulting.fr logo

clemenceconsulting.fr website review

Visit site (opens in a new tab)Reviewed 11 November 202628 issues · 71 checks

This review found 28 issues worth fixing on clemenceconsulting.fr, 8 of them high impact, across 71 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

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

How it loaded on a phone

  1. clemenceconsulting.fr at 0.4 s0.4 s
  2. clemenceconsulting.fr at 0.8 s0.8 s
  3. clemenceconsulting.fr at 1.3 s1.3 s
  4. clemenceconsulting.fr at 1.7 s1.7 s
  5. clemenceconsulting.fr at 2.1 s2.1 s
  6. clemenceconsulting.fr at 2.5 s2.5 s
  7. clemenceconsulting.fr at 3.0 s3.0 s
  8. clemenceconsulting.fr at 3.4 s3.4 s

Speed

7 to fix72
  • Render-blocking requests

    2.4 s

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

  • Google CDN adds 1.0 s

    1.0 s

    Google CDN costs a phone 1.0 s of main-thread work and 1.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and WordPress Site Stats and others), adding 2.1 MB and 1.2 s of main-thread time.

  • Reduce unused JavaScript

    150 ms · 1,016 KiB

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

  • Reduce unused CSS

    900 ms · 181 KiB

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

  • Mobile performance score: 72

    72/100

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

  • Main-thread work: 3.5 s

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

  • 15 long tasks on the main thread

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

  • Font display

    150 ms

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

  • Improve image delivery

    67 KiB

    2 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Minify JavaScript

    6 KiB

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

1 checks passed
  • Server response: 111 ms

    111 ms

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

Core Web Vitals

5 to fix76
  • Time to Interactive: 16.8 s

    16.8 s

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

  • Total Blocking Time: 729 ms

    729 ms

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

  • Speed Index: 5.7 s

    5.7 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 1 image without width and height

    1 image 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.

2 checks passed
  • Largest Contentful Paint: 2.3 s

    2.3 s

    Your largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Nous croyons que le partage de vos enjeux, les données et d…”.

  • Cumulative Layout Shift: 0.082

    0.082

    The layout barely moves while loading (CLS 0.082, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 67 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 67 requests on a phone: scripts 1.9 MB (26), other files 709 KiB (3) and stylesheets 358 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (86 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 1.0 g of CO₂ per visit

    0.99 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9093
  • 1 button without a name

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

    All page content should be contained by landmarks: 3 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.

  • 10 form fields without a label

    10 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

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

SEO

3 to fixGoogle 10078
  • No H1 headline

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

  • Title is short (29 characters)

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

  • Meta description is long (273 characters)

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

  • 80 internal links, 0 external

    The homepage links to 80 pages on clemenceconsulting.fr and 0 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://www.clemenceconsulting.fr/fr/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, 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.clemenceconsulting.fr/sitemap.xml.

AI search readiness

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

    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.

  • No llms.txt

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

Other pages

3 to fix83
  • 2 pages share a title

    https://www.clemenceconsulting.fr/fr and https://www.clemenceconsulting.fr/en all use the title “Accueil - Clemence Consulting”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://www.clemenceconsulting.fr/fr/actualites, https://www.clemenceconsulting.fr/fr/actualites/newsletter, https://www.clemenceconsulting.fr/fr/business-performance, https://www.clemenceconsulting.fr/fr/business-model-innovation, https://www.clemenceconsulting.fr/fr/creation-doffres-de-services-digitales and https://www.clemenceconsulting.fr/fr/data-et-performance and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.clemenceconsulting.fr/fr/actualites, https://www.clemenceconsulting.fr/fr/actualites/newsletter, https://www.clemenceconsulting.fr/fr/business-performance, https://www.clemenceconsulting.fr/fr/business-model-innovation, https://www.clemenceconsulting.fr/fr/creation-doffres-de-services-digitales and https://www.clemenceconsulting.fr/fr/data-et-performance and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.clemenceconsulting.fr/fr/paroles-d-experts has 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 29 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 9693
  • 2 small tap targets

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 analytics detected

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

  • 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 1,478 words of copy

    The homepage carries about 1,478 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: “[email protected]”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “[email protected]”.

  • 2 short forms

    2 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 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.

  • 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
  • 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 clemenceconsulting.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 © 2024.

Stack

CMS
WordPress
Framework
jQuery
Hosting
IONOS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on clemenceconsulting.fr, including 12 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