Website review, no card needed

missionconseil.com logo

missionconseil.com website review

Visit site (opens in a new tab)Reviewed 21 October 202633 issues · 78 checks

This review found 33 issues worth fixing on missionconseil.com, 12 of them high impact, across 78 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

Full-page screenshot of missionconseil.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. missionconseil.com at 0.5 s0.5 s
  2. missionconseil.com at 1.0 s1.0 s
  3. missionconseil.com at 1.5 s1.5 s
  4. missionconseil.com at 2.0 s2.0 s
  5. missionconseil.com at 2.5 s2.5 s
  6. missionconseil.com at 3.0 s3.0 s
  7. missionconseil.com at 3.5 s3.5 s
  8. missionconseil.com at 4.0 s4.0 s

Speed

9 to fix63
  • Use efficient cache lifetimes

    31.3 s · 7.3 MB

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

  • Improve image delivery

    23.4 s · 5.5 MB

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

  • Render-blocking requests

    3.0 s

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

  • Reduce unused JavaScript

    1.2 s · 335 KiB

    About 335 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63 (desktop: 90). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    600 ms · 121 KiB

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

  • Font display

    550 ms

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

  • Google Maps adds 260 ms

    260 ms

    Google Maps costs a phone 260 ms of main-thread work and 475 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.

  • Main-thread work: 2.1 s

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Maps, Other Google APIs/SDKs and missionconseilgroupe.com), adding 494 KiB and 261 ms of main-thread time.

  • Legacy JavaScript

    250 ms · 11 KiB

    Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 3 long tasks on the main thread

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

  • Phones get a much slower page than desktops

    Desktop scores 90 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 102 ms

    102 ms

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

Core Web Vitals

4 to fix67
  • Largest Contentful Paint: 36.5 s

    36.5 s

    Your largest element takes 36.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “With more than 25 years of successful events, Mission Conse…”.

  • Time to Interactive: 36.5 s

    36.5 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • 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
  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 23 ms

    23 ms

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

Images and page weight

1 to fix70
  • Page weight: 7.8 MB in 100 requests

    7.8 MB

    Your homepage downloads 7.8 MB in 100 requests on a phone: images 6.1 MB (15), fonts 775 KiB (9) and scripts 740 KiB (41). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (78 KiB) 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.

  • 2 images below the first screen load straight away

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

  • About 2.2 g of CO₂ per visit

    2.21 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

6 to fixGoogle 8792
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

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

SEO

4 to fixGoogle 9273
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 7 internal links, 1 external

    The homepage links to 7 pages on missionconseil.com and 1 external page.

4 checks passed
  • Title: 43 characters

    Your title is a healthy 43 characters: “MISSION CONSEIL – INSTITUTIONELLEMENT VOTRE”.

  • Canonical URL set

    The canonical URL is https://www.missionconseil.com/.

  • 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.missionconseil.com/wp-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.missionconseil.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 (343 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.missionconseil.com/mission-conseil declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.missionconseil.com/mission-conseil all use the title “MISSION CONSEIL – INSTITUTIONELLEMENT VOTRE”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.missionconseil.com/mission-conseil has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.missionconseil.com/mission-conseil has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 internal page checked

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

3 checks passed
  • Linked pages load

    All 1 page we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

2 to fixGoogle 8891
  • 2 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No analytics detected

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 321 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”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us”, “LEARN MORE” and “START TODAY”.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks and 4 customer or partner logos.

  • Phone number on the homepage

    Your phone number is on the homepage.

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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 missionconseil.com, 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

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 missionconseil.com, including 13 speed issues, 4 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