Can agents find your site and its capabilities?
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.
Built on Webflow.
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.
Only 0/39 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: header.
12 of 12 pages are missing <title> and/or <h1>: /sitemap/2026-07-21/users/sitemap-users-00000000.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000001.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000002.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000003.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000004.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000005.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000006.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000007.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000040.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000041.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000042.xml.gz, /sitemap/2026-07-21/users/sitemap-users-00000043.xml.gz.
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 531 words of visible text — content is reachable without executing JavaScript.
Homepage contains ~558 elements.
6 headings, no level skips.
Language declared as "en".
39 of 39 <img> tags have alt attributes.
27 internal links found.
Exactly one <h1> on the homepage.
All 12 pages return ≥80 words of visible text without JavaScript.
Can agents actually operate the page?
3 of 16 agent-critical accessibility audits failed (Links do not have a discernible name, Input buttons do not have discernible text., `[aria-*]` attributes do not match their roles) — 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: Remove ARIA attributes that aren't allowed on the element's role.
Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.
Fix: Give <input type="button|submit"> controls a value or accessible name.
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: 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.
0/1 data-collecting forms expose errors via ARIA attributes.
Fix: Wire inputs to their error containers with `aria-describedby` and toggle `aria-invalid` on validation failure. Agents that can't see styled error text rely on these attributes.
`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.
ARIA input fields have accessible names passed.
`[role]`s have all required `[aria-*]` attributes passed.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. passed.
`[role]`s are contained by their required parent element passed.
`[role]` values are valid passed.
ARIA toggle fields have accessible names passed.
`[aria-*]` attributes are valid and not misspelled passed.
`[aria-*]` attributes have valid values passed.
Buttons have an accessible name passed.
Document has a `<title>` element passed.
7 of 7 visible interactive form fields have labels.
1/1 data-collecting forms mark required fields.
All 1 data-collecting forms include pattern/min/max constraints.
0.100 (field data from CrUX) — good.
584ms (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.
Can agents safely transact?
No Strict-Transport-Security header on the homepage.
Fix: Add `Strict-Transport-Security: max-age=15768000; includeSubDomains` so browsers and agents refuse to downgrade to http for at least six months.
/.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.
x-amz-cf-id: 8GUMYur9S8IQzA8_y6iiiGeOBIBkJE5ve27fhPnI (AWS CloudFront)
Homepage scheme is https:.
http://flickr.com → https://flickr.com/ (1 hop).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Referrer-Policy: same-origin.
Valid for 165 more days (Jan 2 23:59:59 2027 GMT, issuer: Amazon RSA 2048 M01).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.