Website review, no card needed

lafrenchtech.gouv.fr logo

lafrenchtech.gouv.fr website review

Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 70 checks

This review found 33 issues worth fixing on lafrenchtech.gouv.fr, 14 of them high impact, across 70 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

Real-visitor load time (LCP)75th percentile, phones
4.0 s1.6 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20261.9 s
Jul 11, 20262.0 s
Jul 18, 20262.5 s
Jul 25, 20262.8 s
Aug 8, 20263.4 s
Aug 15, 20263.5 s
Aug 29, 20263.7 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20263.2 s
Oct 17, 20263.2 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
111 ms83 msMay 9Oct 2498 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026102 ms
May 16, 202695 ms
May 23, 202697 ms
May 30, 202697 ms
Jun 6, 202697 ms
Jun 13, 202697 ms
Jun 20, 202687 ms
Jun 27, 202686 ms
Jul 4, 202686 ms
Jul 11, 202686 ms
Jul 18, 202694 ms
Jul 25, 2026101 ms
Aug 8, 2026103 ms
Aug 15, 2026108 ms
Aug 29, 202688 ms
Sep 5, 2026100 ms
Sep 12, 202696 ms
Sep 19, 2026100 ms
Sep 26, 2026101 ms
Oct 3, 2026101 ms
Oct 10, 2026102 ms
Oct 17, 2026100 ms
Oct 24, 202698 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 lafrenchtech.gouv.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lafrenchtech.gouv.fr at 1.0 s1.0 s
  2. lafrenchtech.gouv.fr at 2.0 s2.0 s
  3. lafrenchtech.gouv.fr at 3.0 s3.0 s
  4. lafrenchtech.gouv.fr at 4.1 s4.1 s
  5. lafrenchtech.gouv.fr at 5.1 s5.1 s
  6. lafrenchtech.gouv.fr at 6.1 s6.1 s
  7. lafrenchtech.gouv.fr at 7.1 s7.1 s
  8. lafrenchtech.gouv.fr at 8.1 s8.1 s

Speed

6 to fix60
  • Improve image delivery

    5.8 s · 6.0 MB

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

  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    5.8 MB

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused CSS

    750 ms · 133 KiB

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

  • Reduce unused JavaScript

    450 ms · 121 KiB

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

  • Minify JavaScript

    17 KiB

    17 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: 1.0 s

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

  • Server response: 158 ms

    158 ms

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

Core Web Vitals

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

  • Speed Index: 16.3 s

    16.3 s

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

  • Largest Contentful Paint: 9.4 s

    9.4 s

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

  • Time to Interactive: 9.4 s

    9.4 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

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

    +52%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Tap response (INP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user INP: 108 ms

    108 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.004

    0.004

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

  • 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

5 to fix18
  • Page weight: 7.5 MB in 55 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 55 requests on a phone: images 6.9 MB (30), scripts 261 KiB (12) and fonts 169 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.3 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    943 KiB

    2 images are downloaded at several times the size a phone draws them, for example FT_Newsletter_Panneau-Site.jpg at 1,333 px wide, shown at 356 px. Resized copies would save about 943 KiB.

  • 8 images in older formats

    8 images (4.5 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.

  • 2 images below the first screen load straight away

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

  • About 2.1 g of CO₂ per visit

    2.11 g

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

Accessibility

3 to fixGoogle 10095
  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 4 images without alt text

    4 images have no alt text, which hurts accessibility and image search.

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

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

  • Headings skip levels

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

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 2 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 9284
  • Title is short (22 characters)

    Your title is only 22 characters: “La mission French Tech”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Accompagner et promouvoir l’écosystème des start-…” and “Pour ne rien rater de la French Tech : abonnez-vo…”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: url points at a different host (https://bo-lft.bercy.actimage.net/fr/)”.

  • 53 internal links, 12 external

    The homepage links to 53 pages on lafrenchtech.gouv.fr and 12 external pages.

5 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “La mission French Tech est chargée de soutenir la structuration et la croissance de l’écosystème des start-up française…”.

  • Canonical URL set

    The canonical URL is https://lafrenchtech.gouv.fr/fr/.

  • 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://lafrenchtech.gouv.fr/sitemap_index.xml.

AI search readiness

100
3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 3 pages share a title

    /, https://lafrenchtech.gouv.fr/fr and https://lafrenchtech.gouv.fr/en all use the title “La mission French Tech”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://lafrenchtech.gouv.fr/fr/nous-contacter, https://lafrenchtech.gouv.fr/fr/espace-presse, https://lafrenchtech.gouv.fr/fr/presentation, https://lafrenchtech.gouv.fr/fr/notre-equipe, https://lafrenchtech.gouv.fr/fr/actualites and https://lafrenchtech.gouv.fr/fr/quest-ce-que-l-ecosysteme-french-tech and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page slow to respond

    https://lafrenchtech.gouv.fr/fr/programme/french-tech-2030 took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 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.

  • Canonical URLs point to themselves

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

  • 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

1 to fixGoogle 10093
  • 5 small tap targets

    5 of 20 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

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.

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

    The homepage carries about 759 words of visible text.

2 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Présentation de l'écosystème start-up”, “Les données sur l’écosystème start-up” and “Les offres d'emploi des start-up”.

  • 2 short forms

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

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

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 lafrenchtech.gouv.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
WordPress
Framework
jQuery
Hosting
Imperva

Company

Employees
32
Founded
2013
Headquarters
Station F

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 lafrenchtech.gouv.fr, including 15 speed issues, 3 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