REWE · Agent Readiness · Agent Checker

Discoverability

Can agents find your site and its capabilities?

failWebMCP / agent-protocol tools discoveredAgent manifests

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.

warnKey pages discoveredKey pages crawl

Discovered 12 candidate pages but none were reachable.

Fix: Make sure the pages linked from your sitemap and navigation return HTTP 200 to non-browser clients — agents fetch them the same way our crawler does.

infoWebsite platformplatform

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

Understanding

Can agents understand your content?

failHTML readiness checks ranStructured data & HTML

Homepage returned 403 — couldn't analyse structure.

warnMarkdown content negotiationOpen agent protocols

Homepage returned 403 for Accept: text/markdown.

warnHomepage content is server-renderedCrawlability (Google)

Homepage returned 403.

Operability

Can agents actually operate the page?

failLinks do not have a discernible nameAccessibility

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.

failWebMCP tools registered with the browserWebMCP tools

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.

warnAccessibility tree is agent-navigableAccessibility

1 of 15 agent-critical accessibility audits failed (Links do not have a discernible 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).

warnTime to First BytePerformance

822ms (field data from CrUX) — needs improvement.

Fix: Every request an AI agent makes pays this server latency, and agents make many requests per task. Reduce TTFB with edge caching, a CDN, and shipping less server-side work per request.

pass`[aria-*]` attributes match their rolesAccessibility

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

passUses ARIA roles only on compatible elementsAccessibility

Uses ARIA roles only on compatible elements passed.

pass`button`, `link`, and `menuitem` elements have accessible namesAccessibility

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

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

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

pass`[aria-hidden="true"]` elements do not contain focusable descendentsAccessibility

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

pass`[role]`s have all required `[aria-*]` attributesAccessibility

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

passElements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.Accessibility

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. passed.

pass`[role]`s are contained by their required parent elementAccessibility

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

pass`[role]` values are validAccessibility

`[role]` values are valid passed.

pass`[aria-*]` attributes are valid and not misspelledAccessibility

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

pass`[aria-*]` attributes have valid valuesAccessibility

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

passButtons have an accessible nameAccessibility

Buttons have an accessible name passed.

passDocument has a `<title>` elementAccessibility

Document has a `<title>` element passed.

passARIA IDs are uniqueAccessibility

ARIA IDs are unique passed.

passOverall accessibility scoreAccessibility

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

passCumulative Layout ShiftPerformance

0.010 (field data from CrUX) — good.

infoTool catalog signpost publishedWebMCP tools

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.

Trust & Security

Can agents safely transact?

warnOAuth authorization server metadataOpen agent protocols

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

warnOAuth protected-resource metadataOpen agent protocols

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

warnWeb Bot Auth signature headerOpen agent protocols

Homepage returned 403.

warnContent-Security-Policy headerSecurity & trust

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.

warnHTTP Strict-Transport-Security headerSecurity & trust

HSTS max-age=15552000 is below six months.

Fix: Raise max-age to at least 15768000 (six months). The HSTS preload list requires 31536000 (one year).

warnHomepage shows no error outputSecurity & trust

Homepage returned 403 — couldn't scan for error markers.

warnNo mixed-content referencesSecurity & trust

Homepage returned 403 — couldn't scan for mixed content.

passCDN detectedSecurity & trust

cf-ray: a1eb772c3fb9312a-AMS (Cloudflare); Server: cloudflare

passSite is served over HTTPSSecurity & trust

Homepage scheme is https:.

passhttp:// redirects to https://Security & trust

http://rewe.de → https://www.rewe.de/ (1 hop).

passReferrer-Policy headerSecurity & trust

Referrer-Policy: same-origin.

passTLS certificate is not near expirySecurity & trust

Valid for 66 more days (Sep 25 23:31:35 2026 GMT, issuer: YR1).

passNo tech-stack disclosure in headersSecurity & trust

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

passMIME-sniff protectionSecurity & trust

X-Content-Type-Options: nosniff.

passClick-jacking protectionSecurity & trust

X-Frame-Options: SAMEORIGIN.