Can agents find your site and its capabilities?
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).
Can agents understand your content?
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 ~2046 elements — heavy.
Fix: Aim for under 1500 elements on the homepage. Heavier DOMs slow first paint and overflow some AI crawlers' parse buffers.
66 of 82 images have alt attributes (80%).
Fix: Add alt text to the remaining images. Empty alt="" is fine for purely-decorative graphics.
Only 9/82 images have width+height — large CLS risk.
Fix: Set width and height on every <img> so the browser reserves space before the image loads. A layout that shifts while loading makes an AI agent mis-click the element it targeted.
Missing landmark elements: main.
Found 14 <h1> tags. Most AI summarisers expect exactly one.
Fix: Demote the secondary H1s to H2 — keep H1 reserved for the page title.
Homepage server response contains 2963 words of visible text — content is reachable without executing JavaScript.
129 headings, no level skips.
Language declared as "en".
314 internal links found.
All 12 reachable key pages have both a <title> and <h1>.
All 12 pages return ≥80 words of visible text without JavaScript.
Can agents actually operate the page?
3 of 13 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) — 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 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](https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents) helps AI agents to navigate and interact with the page.
Lighthouse accessibility score: 83/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.
No autocomplete attributes on any data-collecting form field.
Fix: Add autocomplete hints (email, tel, name, etc.) so form-filling agents and browsers can populate fields without guessing.
No HTML5 validation hints (pattern / minlength / maxlength / min / max) on any data-collecting form input.
Fix: Publish input constraints via HTML attributes so agents and browsers can validate client-side.
0.168
`[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]` 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.
All 1 data-collecting forms reference errors via aria-describedby / aria-invalid.
2 of 2 visible interactive form fields have labels.
1/1 data-collecting forms mark required fields.
0.010 (field data from CrUX, for this page). Good.
233ms (field data from CrUX, for this page). Good.
1 form missing annotations
Lists the [WebMCP tools](https://developer.chrome.com/docs/ai/webmcp) 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.
Can agents safely transact?
/.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=63072000) but missing includeSubDomains.
Fix: Add `includeSubDomains` so subdomains inherit the policy.
x-served-by: cache-lhr-egwu1540061-LHR, cache-lhr-egw (Fastly / Varnish)
CSP header present.
Homepage scheme is https:.
http://independent.co.uk → https://www.independent.co.uk/ (2 hops).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Referrer-Policy: no-referrer-when-downgrade.
Valid for 199 more days (Mar 22 20:00:18 2027 GMT, issuer: GlobalSign Atlas R3 DV TLS CA 2026 Q1).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.