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.
Could not identify a known website platform (custom stack or unrecognised).
Can agents understand your content?
Only 1/44 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.
5 of 12 pages are missing <title> and/or <h1>: /groups/gitlab-org/-/issues, /groups/gitlab-org/-/packages, /groups/gitlab-org/-/epics, /groups/gitlab-org/developer-relations/contributor-success/mattias-testing/-/issues, /groups/gitlab-org/developer-relations/contributor-success/mattias-testing/-/packages.
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.
11 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /explore/projects (6w), /explore/groups (28w), /gitlab-org (13w), /groups/gitlab-org/-/issues (6w), /groups/gitlab-org/-/merge_requests (8w), /groups/gitlab-org/-/packages (6w), /groups/gitlab-org/-/epics (6w), /gitlab-org/developer-relations/contributor-success/mattias-testing (5w), /groups/gitlab-org/developer-relations/contributor-success/mattias-testing/-/issues (6w), /groups/gitlab-org/developer-relations/contributor-success/mattias-testing/-/merge_requests (8w), /groups/gitlab-org/developer-relations/contributor-success/mattias-testing/-/packages (6w).
Fix: Pre-render or server-render these pages so AI crawlers (which usually don't execute JS) can read them. Frameworks: Next.js Server Components, Nuxt SSR, Astro, or build-time prerendering.
Homepage returns text/markdown when requested.
Homepage server response contains 966 words of visible text — content is reachable without executing JavaScript.
Homepage contains ~1147 elements.
36 headings, no level skips.
Language declared as "en-US".
44 of 44 <img> tags have alt attributes.
161 internal links found.
All four landmark elements present (main, header, footer, nav).
Exactly one <h1> on the homepage.
Can agents actually operate the page?
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.
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.
2 of 13 agent-critical accessibility audits failed (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 accessibility score: 87/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.
818ms (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.
`[aria-*]` attributes match their roles passed.
Uses ARIA roles only on compatible elements 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.
Buttons have an accessible name passed.
Document has a `<title>` element passed.
Links have a discernible name passed.
1 of 1 visible interactive form fields have labels.
0.010 (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 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.
HSTS configured (max-age=31536000) but missing includeSubDomains.
Fix: Add `includeSubDomains` so subdomains inherit the policy.
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.
No `X-Content-Type-Options: nosniff` header.
Fix: Add `X-Content-Type-Options: nosniff` to prevent browsers (and some agents) from re-interpreting your responses as a different content type.
No X-Frame-Options header and no CSP frame-ancestors directive.
Fix: Add `X-Frame-Options: SAMEORIGIN` (or a CSP frame-ancestors directive) to prevent your site being framed by a phishing host.
/.well-known/oauth-authorization-server returns parseable JSON.
/.well-known/oauth-protected-resource returns parseable JSON.
cf-ray: a1eab4f0784d66ce-AMS (Cloudflare); Server: cloudflare
Homepage scheme is https:.
http://gitlab.com → https://about.gitlab.com/ (2 hops).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Valid for 112 more days (Nov 10 23:59:59 2026 GMT, issuer: Sectigo Public Server Authentication CA DV R36).
Server / X-Powered-By headers don't leak product version.