From an awareness page to a science-backed platform — adaptive pathways, subscription billing, and an AI assistant.

Key findings

• Your evidence layer is genuinely strong: INSERM/Nnoaham/Touboul/Özdemir citations, a “verified 2 June 2026” stamp, HAS/CNGOF references and a 24-reference bibliography.
• Clean information architecture: a seven-item menu maps one-to-one to pages, single H1s, unique page descriptions and six structured-data blocks on the homepage.
• Register mixing on public pages: the pricing FAQ and one plan bullet in the informal “tu”, a “Prête à transformer ton bien-être ?” heading over a formal “vous” body, the about-page story in “tu” (29 “tu” strings vs 150 “vous”).

Recommendations

• Unify the address register: the formal “vous” on all public marketing pages, the informal “tu” reserved for the logged-in app — fix the pricing FAQ, plan bullets and about-page story first.
• Lock terminology sitewide: Besoin/Envie as the only pathway pair and one acronym (TNM) for non-drug therapies, then sweep the homepage, comparison table and foundations page.

Key findings

• Hardcoded colours in inline styles eliminated: 27–80 per page on 2 June, now 0 raw colour values across all 7 pages — every inline colour routes through your design tokens.
• Duplicate sage resolved: a single sage value (#556654) defines the green everywhere; the old #4A7C59 returns zero hits in the served HTML and the stylesheet.
• A two-layer token architecture with meaning-based aliases (status, surface, per-pathway icon tokens) and a Tailwind bridge drawing on the same colour values.

Recommendations

• Fix the gold-on-light text contrast: darken the link gold to around #8a6d1f, or switch article links and the hover state to sage (6.15:1 on white).
• Adopt the corner-radius tokens everywhere: replace raw 20px, 24px and other one-off values with the radius tokens, and add a larger radius token if 24px is intentional.

Key findings

• The top of the page answers who and what: an audience-specific subtitle under 'Reprenez le contrôle de votre bien-être' with a dual call to action, backed by a sourced four-stat evidence band.
• Friction is handled across the site: a no-card 7-day trial button on every page, a 30-day money-back guarantee, Stripe named, and a one-step route to sign-up.
• Differentiation is explicit: a 10-feature comparison against generic wellness apps, information sites and inaction, plus a dedicated evidence page.

Recommendations

• Reconcile the trial promise: one sentence defining exactly what the 7-day trial includes, used identically on the pricing page, the contact FAQ and the hero.
• Source or replace the proof numbers: add sample size and survey date to the 94% claim, reconcile '15+ therapists' with the five named practitioners, and date the 200+ sessions count.

Key findings

• Security scores 96 out of 100, up from 30 on the old site.
• The Content-Security-Policy is active and restrictive — it was confirmed live by blocking an external script during the audit.
• HSTS runs for two years with preload, framing is denied, content-type sniffing is off, the referrer policy is strict, and the permissions policy locks down camera, microphone, location and payment.

Recommendations

• Move to a nonce-based Content-Security-Policy via the Next.js middleware to drop the remaining inline execution — eval is already removed. Test that the page still loads.
• Confirm the full header set live with a security-header checker before launch.

Key findings

• An llms.txt file is present and well-formed: an English overview, nine key pages with descriptions, and explicit audience and language notes — a direct map for AI crawlers.
• Your medical-page schema names the condition “Endométriose” with an audience and a speakable block targeting the homepage answer — entity clarity engines can resolve directly.
• The homepage stat band cites named sources (WHO 2025, INSERM cohort, Nnoaham et al. 2011) under an “Informations vérifiées le 2 juin 2026” stamp, with a medical disclaimer — quotable, dated, attributed claims.

Recommendations

• Emit each schema block exactly once per page (the FAQ on the pricing page, the breadcrumb on articles).
• Seed the three missing text keys (the skip-link label and the two service titles) so no template internals show in the visible text.