Can agents find your site and its capabilities?
Crawled 2 of 12 discovered pages beyond the homepage.
Lighthouse Agentic Browsing audits ran.
Built on WordPress.
Can agents understand your content?
Only 18 of 36 images have alt attributes (50%).
Fix: Add alt text to every <img>. Screen readers and AI vision models both rely on it to caption images.
No <h1> tag found on the homepage.
Fix: Add exactly one <h1> that names the page. AI summarisers use it as the document title.
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 ~3106 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.
Only 3/36 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: nav.
Homepage server response contains 2094 words of visible text — content is reachable without executing JavaScript.
39 headings, no level skips.
Language declared as "en".
281 internal links found.
All 2 reachable key pages have both a <title> and <h1>.
All 2 pages return ≥80 words of visible text without JavaScript.
Can agents actually operate the page?
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.
Only 4 of 8 visible interactive form fields have labels.
Fix: Associate every input with a label. Form-filling agents (and screen readers) need it to know what to type into each field.
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.
1 of 10 agent-critical accessibility audits failed (Buttons do not have an accessible name) — 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 accessibility score: 80/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.
`[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.
Links have a discernible name passed.
0.091
0.040 (field data from CrUX) — good.
298ms (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.
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.
No Content-Security-Policy header on the homepage.
Fix: Add a Content-Security-Policy. Even a strict default-src directive cuts XSS blast radius dramatically. Start in report-only mode to find violations.
http://rottentomatoes.com redirects to http://www.rottentomatoes.com/ — never reaching https.
Fix: Redirect every http:// request to the https:// equivalent of the same URL.
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.
max-age=31536000, includeSubDomains=true, preload=false.
Homepage scheme is https:.
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 89 more days (Oct 18 23:59:59 2026 GMT, issuer: DigiCert Global G3 TLS ECC SHA384 2020 CA1).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.