Can agents find your site and its capabilities?
Per llmstxt.org, follow the H1 with a "> short summary" blockquote.
Fix: Add a "> One-sentence description of your site." blockquote under the H1.
The site registers callable WebMCP tools with the browser at runtime, so an AI agent can operate the page through them.
Found a parseable Agent Skills index at https://render.com/.well-known/agent-skills/index.json.
Found a Markdown guide at /AGENTS.md.
Found a parseable Linkset at https://render.com/.well-known/api-catalog.
Found https://render.com/llms.txt.
Found at least one "[name](url)" markdown link.
First line is a top-level "# Title" heading.
Crawled 12 of 12 discovered pages beyond the homepage.
If your llms.txt file does not follow recommendations, large language models may not be able to understand how you want your website to be crawled or used for training. The [llms.txt](https://llmstxt.org/) file should be a Markdown file containing at least one H1 header.
Lighthouse Agentic Browsing audits ran.
Could not identify a known website platform (custom stack or unrecognised).
Can agents understand your content?
Only 6/54 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.
Homepage returns text/markdown when requested.
Homepage server response contains 746 words of visible text — content is reachable without executing JavaScript.
Homepage contains ~1389 elements.
28 headings, no level skips.
Language declared as "en".
54 of 54 <img> tags have alt attributes.
74 internal links found.
All four landmark elements present (main, header, footer, nav).
Exactly one <h1> on the homepage.
All 12 reachable key pages have both a <title> and <h1>.
All 12 pages return ≥80 words of visible text without JavaScript.
Can agents actually operate the page?
Lighthouse flagged this audit — agents may be unable to perceive or operate the affected elements.
Fix: Don't place focusable/interactive elements inside aria-hidden="true" containers.
A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.
1 of 10 agent-critical accessibility audits failed (`[aria-hidden="true"]` elements contain focusable descendents) — 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: 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.
0.120 (field data from CrUX) — needs improvement.
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.
`[aria-*]` attributes match their roles passed.
`[aria-hidden="true"]` is not present on the document `<body>` 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.
0.001
Valid [WebMCP schemas](http://goo.gle/webmcp-docs) are required for AI agents to understand and interact with tools correctly. Please fix any errors or warnings reported by the browser.
777ms (field data from CrUX) — good.
5 tool(s) registered via the WebMCP browser API (navigator.modelContext).
All 5 registered tool(s) declare a name, description, and an object inputSchema.
Lists the [WebMCP tools](http://goo.gle/webmcp-docs) registered at the time of analysis.
5 tool(s) published at /.well-known/webmcp.json (spec webmcp/0.1). The catalog is a community convention signpost, not part of the WebMCP standard.
5: render.docs.search, render.docs.get-markdown, render.llms.get-index, render.blog.get-index, render.articles.get-index
All 5 tool(s) declare a name and description.
5: render.docs.search, render.docs.get-markdown, render.llms.get-index, render.blog.get-index, render.articles.get-index
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.
cf-ray: a1eac209092e66db-AMS (Cloudflare); Server: cloudflare
CSP header present.
max-age=31536000, includeSubDomains=true, preload=true.
Homepage scheme is https:.
http://render.com → https://render.com/ (1 hop).
No stack-trace markers in the first 5KB.
Homepage HTML references no http:// resources.
Referrer-Policy: same-origin.
Valid for 31 more days (Aug 21 19:26:00 2026 GMT, issuer: WE1).
Server / X-Powered-By headers don't leak product version.
X-Content-Type-Options: nosniff.
X-Frame-Options: SAMEORIGIN.