Lefigaro

The page registers no tools via the WebMCP browser API (navigator.modelContext).

Fix: Expose your actions to AI agents with the WebMCP browser API: register tools via navigator.modelContext.registerTool. Optionally also publish a /.well-known/webmcp.json tool catalog as a discovery signpost.

Crawled 3 of 12 discovered pages beyond the homepage.

Lighthouse Agentic Browsing audits ran.

Could not identify a known website platform (custom stack or unrecognised).

Homepage ignored Accept: text/markdown and returned HTML.

Fix: Serve a markdown version of high-value pages when the client asks for text/markdown. AI summarisers, chatbots and IDE agents prefer markdown — fewer tokens, no DOM noise.

Cookie banner appears to overlay the page (fixed/sticky, dialog role) without a clearly-labelled reject affordance.

Fix: Offer a "Reject all" or "Continue without accepting" button alongside "Accept". Agents and non-JS crawlers that can't click through your banner read the page as empty.

Homepage contains ~4396 elements — well above the 1500-element budget.

Fix: Trim the homepage DOM: an AI agent has to read all of it before acting, and this page is several times over budget. Long product carousels, hidden modal markup and large tracker scripts are common culprits.

293/338 images have explicit width+height.

Fix: Add width and height to every <img>. Without them the browser doesn't know the aspect ratio and reflows the page on load (CLS).

Only 1 internal link on the homepage.

Fix: Add at least 5-10 internal links pointing to your top product, pricing, docs, blog and about pages so an AI agent can navigate to them from the homepage.

1 of 3 pages are missing <title> and/or <h1>: /contact.

Fix: Make sure every page sets a unique <title> and exactly one <h1>. The title is how an AI agent confirms it landed on the right page after navigating.

1 of 3 pages return <80 words of visible text — agents without JavaScript see an empty page: /contact (62w).

Fix: Pre-render or server-render these pages so AI crawlers (which usually don't execute JS) can read them. Frameworks: Next.js Server Components, Nuxt SSR, Astro, or build-time prerendering.

Homepage server response contains 8429 words of visible text — content is reachable without executing JavaScript.

117 headings, no level skips.

Language declared as "fr".

338 of 338 <img> tags have alt attributes.

All four landmark elements present (main, header, footer, nav).

Exactly one <h1> on the homepage.

4 of 17 agent-critical accessibility audits failed (Buttons do not have an accessible name, ARIA input fields do not have accessible names, `[aria-*]` attributes do not have valid values, Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.) — an agent may be unable to identify or operate the affected elements.

Fix: Fix the failing agent-accessibility audits listed below (accessible names on controls, valid ARIA roles/relationships, nothing interactive hidden from the tree).

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Give ARIA input fields an accessible name.

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Ensure ARIA roles that need specific children contain them (e.g. list → listitem).

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Fix invalid values on aria-* attributes.

Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.

Fix: Give every <button> discernible text or an aria-label so agents can identify it.

The page registers no tools via the navigator.modelContext browser API, so an AI agent has no structured way to operate it.

Fix: Expose your site’s actions to AI agents with the WebMCP browser API: call navigator.modelContext.registerTool({ name, description, inputSchema, execute }) from your page so an agent can invoke them. Implement it directly, or with a library like the @mcp-b polyfill (https://mcp-b.ai). Spec: https://github.com/webmachinelearning/webmcp.

Lighthouse accessibility score: 79/100. Agents read the page through its accessibility tree, so this is a proxy for how navigable your site is to an AI agent.

Fix: Resolve the failing accessibility audits below — each one removes an element or relationship an agent would otherwise be blind to.

0.150 (field data from CrUX, for this page). Needs improvement.

Fix: A layout that shifts while loading makes an AI agent mis-click the element it targeted. Eliminate CLS by setting explicit width/height on images and embeds, avoiding inserted content above existing content, and reserving space for ad slots.

`[aria-*]` attributes match their roles passed.

`button`, `link`, and `menuitem` elements have accessible names passed.

`[aria-hidden="true"]` is not present on the document `<body>` passed.

`[aria-hidden="true"]` elements do not contain focusable descendents passed.

`[role]`s have all required `[aria-*]` attributes passed.

`[role]`s are contained by their required parent element passed.

`[role]` values are valid passed.

ARIA toggle fields have accessible names passed.

`[aria-*]` attributes are valid and not misspelled passed.

Document has a `<title>` element passed.

ARIA IDs are unique passed.

`<frame>` or `<iframe>` elements have a title passed.

Links have a discernible name passed.

1 of 1 visible interactive form fields have labels.

238ms (field data from CrUX, for this page). Good.

No tool catalog was found at /.well-known/webmcp.json (or /.well-known/webmcp). The catalog is a community convention, not part of the WebMCP standard, so this does not affect WebMCP presence.

Fix: Consider also publishing a tool catalog at /.well-known/webmcp.json: a JSON document with a "spec" of "webmcp/0.1" and a "tools" array, where each tool declares a name and a clear description. It is a community convention (optional, not part of the WebMCP standard) that lets crawlers and agents discover your tools without executing JavaScript.

Found 5 http:// references in the homepage HTML — browsers will block these resources.

Fix: Update every http:// resource URL to https:// (or use protocol-relative `//`). Common offenders: image CDNs and legacy embed snippets.

/.well-known/oauth-authorization-server returned 404.

Fix: Publish /.well-known/oauth-authorization-server so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.

/.well-known/oauth-protected-resource returned 404.

Fix: Publish /.well-known/oauth-protected-resource so AI agents discovering your OAuth setup can negotiate flows automatically. Required if your site offers an authenticated API.

No Web Bot Auth signature headers — sites can't verify agent identity.

Fix: Web Bot Auth (IETF HTTP Message Signatures over Signature / Signature-Input) lets you cryptographically verify which agent is hitting you. Several CDNs offer turn-key support; otherwise skip until vendor support matures.

No Referrer-Policy header on the homepage.

Fix: Add `Referrer-Policy: strict-origin-when-cross-origin` so outbound links don't leak full URLs (including query strings) to third parties.

No `X-Content-Type-Options: nosniff` header.

Fix: Add `X-Content-Type-Options: nosniff` to prevent browsers (and some agents) from re-interpreting your responses as a different content type.

CSP header present.

max-age=31536000, includeSubDomains=true, preload=true.

Homepage scheme is https:.

http://lefigaro.fr → https://www.lefigaro.fr/ (2 hops).

No stack-trace markers in the first 5KB.

Valid for 158 more days (Feb 9 23:59:59 2027 GMT, issuer: DigiCert Global G3 TLS ECC SHA384 2020 CA1).

Server / X-Powered-By headers don't leak product version.

X-Frame-Options: sameorigin.