Toyota

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.

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

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 ~3488 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 0/78 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.

5 of 12 pages are missing <title> and/or <h1>: /, /accessories, /avalon, /brand, /configurator.

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.

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

Detected 1 cookie-banner element but none look agent-hostile (small, dismissible, or offer a reject option).

18 headings, no level skips.

Language declared as "en".

78 of 78 <img> tags have alt attributes.

243 internal links found.

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

4 of 14 agent-critical accessibility audits failed (Buttons do not have an accessible name, Links do not have a discernible name, 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: Give every link discernible text (avoid bare icons / "click here") so agents know where it goes.

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

5 of 7 visible interactive form fields have labels.

Fix: Associate every input with a label — either wrap it in <label>, link via for/id, or set aria-label / aria-labelledby.

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

Uses ARIA roles only on compatible elements 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.

0.000 (field data from CrUX) — good.

215ms (field data from CrUX) — 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.

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

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

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=31536000) but missing includeSubDomains.

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

x-amz-cf-id: sM6GKIoYPk3Aa5xfkMABs8EHB9qFDsUZppoOL4Xq (AWS CloudFront)

CSP header present.

Homepage scheme is https:.

http://toyota.com → https://www.toyota.com/ (1 hop).

No stack-trace markers in the first 5KB.

Homepage HTML references no http:// resources.

Referrer-Policy: strict-origin-when-cross-origin.

Valid for 78 more days (Oct 7 23:59:59 2026 GMT, issuer: Amazon RSA 2048 M04).

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

X-Content-Type-Options: nosniff.

X-Frame-Options: SAMEORIGIN.