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.
Couldn't analyse the homepage: The server returned a bot-protection challenge page (matched "/_incapsula_resource") instead of your site. AI agents are likely served the same challenge.
Fix: Allow well-behaved crawlers (or our User-Agent) through your CDN/WAF bot-management rules and re-run — server-side fetchers and some AI crawlers are otherwise served a challenge instead of your content.
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?
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.
Couldn't analyse the homepage: The server returned a bot-protection challenge page (matched "/_incapsula_resource") instead of your site. AI agents are likely served the same challenge.
Fix: Your CDN/WAF served our scanner a bot-protection challenge instead of the page, so its content could not be analysed. Allow well-behaved crawlers (or our User-Agent) through your bot-management rules and re-run. AI agents that drive a real browser may still reach the page, but server-side fetchers (and some AI crawlers) will see the same challenge.
10 of 12 pages are missing <title> and/or <h1>: /personal/products-services/mobile, /personal/products-services/mobile/right-phone-plan/iphone, /personal/products-services/mobile/right-phone-plan/vivo, /personal/products-services/mobile/trade-in, /personal/products-services/mobile/trade-in/mobile-trade-in-tncs, /personal/products-services/mobile/phone, /personal/products-services/mobile/phone/iphone, /personal/products-services/mobile/postpaid-plans, /personal/products-services/mobile/postpaid-plans/silver, /personal/products-services/mobile/postpaid-plans/comboxo.
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.
1 of 12 pages return <80 words of visible text — agents without JavaScript see an empty page: /personal/products-services/mobile/trade-in/mobile-trade-in-tncs (45w).
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.
Can agents actually operate the page?
Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.
Fix: Give ARIA buttons/links/menuitems an accessible name.
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.
1.040 (field data from CrUX) — poor.
Fix: A layout that shifts while loading makes an AI agent mis-click the element it targeted. Eliminate CLS by setting explicit width/height on images and embeds, avoiding inserted content above existing content, and reserving space for ad slots.
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 9 agent-critical accessibility audits failed (`button`, `link`, and `menuitem` elements do not have accessible names., `[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: 73/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-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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children. passed.
`[role]` values are valid passed.
Document has a `<title>` element passed.
Links have a discernible name passed.
442ms (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?
/.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.
Certificate expires in 22 days (Aug 13 04:06:55 2026 GMT).
Fix: Renew within the week — automated renewal (Let's Encrypt + cron / certbot) avoids manual outages.
x-amz-cf-id: bvgqQ7IUnGtZV7_9tW1BVo-PrgfhmA9mgC5SpGNH (AWS CloudFront)
CSP header present.
max-age=31536000, includeSubDomains=true, preload=true.
Homepage scheme is https:.
http://singtel.com → https://www.singtel.com/ (2 hops).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Referrer-Policy: strict-origin-when-cross-origin, strict-origin-when-cross-origin.
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
CSP frame-ancestors directive present.