Lemonde

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

Homepage contains ~4780 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.

Detected 1 heading level skip (e.g. h2 → h4).

Fix: Tighten the heading order so each level only steps down by one. Skipped levels confuse both screen-readers and AI structural extractors.

195/198 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).

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

Language declared as "fr".

198 of 198 <img> tags have alt attributes.

29 internal links found.

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

Exactly one <h1> on the homepage.

All 12 reachable key pages have both a <title> and <h1>.

All 12 pages return ≥80 words of visible text without JavaScript.

5 of 15 agent-critical accessibility audits failed (Buttons do not have an accessible name, Links do not have a discernible name, `<frame>` or `<iframe>` elements do not have a title, Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children., `[role]`s are not contained by their required parent element) — 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: 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: Ensure ARIA child roles are nested inside their required parent role.

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.

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

Fix: Add a title to every <iframe> so agents can identify embedded content.

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

Fix: Give every link discernible text (avoid bare icons / "click here") so agents know where it goes.

A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

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: 68/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.

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

Uses ARIA roles only on compatible elements 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]` values are valid passed.

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

`[aria-*]` attributes have valid values passed.

Document has a `<title>` element passed.

ARIA IDs are unique passed.

1 of 1 visible interactive form fields have labels.

0

0.100 (field data from CrUX) — good.

276ms (field data from CrUX) — good.

1 form missing annotations

Lists the [WebMCP tools](http://goo.gle/webmcp-docs) registered at the time of analysis.

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.

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

HSTS configured (max-age=31557600) but missing includeSubDomains.

Fix: Add `includeSubDomains` so subdomains inherit the policy.

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.

x-served-by: cache-lcy-eglc8600075-LCY, cache-lcy-egl (Fastly / Varnish)

CSP header present.

Homepage scheme is https:.

http://lemonde.fr → https://www.lemonde.fr/ (1 hop).

No stack-trace markers in the first 5KB.

Homepage HTML references no http:// resources.

Valid for 56 more days (Sep 16 08:42:55 2026 GMT, issuer: YR1).

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

X-Content-Type-Options: nosniff.

X-Frame-Options: SAMEORIGIN.