D

Poor for AI agents

Speed: Fail (real visitors, last 28 days)Core Web Vitals, Google

Start here.

These hold your letter down the most
  1. Fail·Read

    Your site has a short guide for AI agents (llms.txt)

    Google's Lighthouse found no /llms.txt on your site.

    What to do Publish /llms.txt with your business name as its title and links to your most important pages.

    Your web team · about an hourSee the check

  2. Fail·Read

    Your site tells AI agents everything they can do with it, in one place (ARD catalog)

    Google's Lighthouse found no ARD catalog at /.well-known/ard.json.

    What to do Publish an ARD catalog that lists every tool and service agents can use, such as your MCP server.

    Your web team · about a daySee the check

  3. Fail·Read

    Your site sends AI agents a plain-text version of each page (Markdown)

    Cloudflare's scan asked your home page for Markdown and got none back.

    What to do Send each page as Markdown to agents that ask for it.

    Your web team · about a daySee the check

97

Find

Can AI agents and search engines get to your site and list its pages? If they can't find you, you're not in the conversation, and someone else gets recommended.

25% of your grade · 9 of 10 goals pass

  • Your site's security doesn't turn AI agents away (firewall)CriticalPass

    Many sites sit behind a firewall or bot-protection service that blocks automated visits. An agent stopped at the door reads nothing, so it answers from other sites. Claude's web fetch, for example, gets only what your site sends back.

  • Your site lets AI agents in (robots.txt)CriticalPass

    AI services send crawlers, robots that read sites for them. One your robots.txt blocks cannot use your pages, so answers about your business come from other sites. OpenAI, Anthropic and Perplexity each say their crawlers obey robots.txt.

  • Search engines may show your pages in their resultsCriticalPass

    A page search engines may not list is missing from Google's and Bing's results, and from AI answers built on them, such as Google's AI Overviews. Brave's search, which some AI agents use, follows Google's rules.

  • Your instructions to AI agents and search engines have no errors (robots.txt)ImportantPass

    Google's crawler skips any line of robots.txt it cannot read, so a rule you meant to set never applies. A page you wanted found may be left out, or one you wanted kept out may be read.

  • Your site lists its pages for search engines (XML sitemap)ImportantPass

    Google and Bing use a sitemap to find your pages, though neither promises to list every page in it. A page must be in Google's index to appear in its AI answers.

  • Your site says when a page does not exist (404)ImportantPass

    When a missing page says so, Google drops the address from search. When it answers like a normal page, Google flags a soft 404, and every mistyped address looks like a real page.

  • Every page has a titleImportantPass

    Google builds the link to your page in its results from the page's title, and may rewrite one that is missing, vague or repeated. A clear title keeps your own words in front of searchers.

  • A page that can be reached at more than one address names its main one (canonical)ImportantPass

    Google shows only one address for a page. When you name it, the page's standing stays in one place and searchers land on the version you chose, in their language. When you don't, Google guesses.

  • Your pages open without unnecessary redirectsImportantPass

    Each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds. Every visitor waits for every hop.

47

Read

Can agents quickly work out who you are and what you offer? An agent only spends so much effort on one site. If yours is hard to read, it moves on and recommends one that's easier.

25% of your grade · 4 of 7 goals pass

  • Your site has a short guide for AI agents (llms.txt)CriticalFail

    llms.txt gives agents a short map of your site, so they reach your key pages without reading every one. Lighthouse checks it as an emerging convention, and the grade counts standards likely to be adopted.

    What we found: Google's Lighthouse found no /llms.txt on your site.

    How to fix it

    Publish /llms.txt with your business name as its title and links to your most important pages.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site has a short guide for AI agents (llms.txt) What the grader found: Google's Lighthouse found no /llms.txt on your site. The fix, for a developer: Serve a Markdown file at /llms.txt with a 200, and keep it clear of any rule that sends unknown paths to the home page or a firewall page. Start it with an H1 naming the site, then sections of links to key pages, as llmstxt.org describes. Source: llms.txt audit, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · about an hour
  • Your site tells AI agents everything they can do with it, in one place (ARD catalog)CriticalFail

    Agents read the catalog before they open a page, so they know straight away which of your services they can use, such as your MCP server. Lighthouse checks it, and the grade counts standards likely to be adopted, such as this draft.

    What we found: Google's Lighthouse found no ARD catalog at /.well-known/ard.json.

    How to fix it

    Publish an ARD catalog that lists every tool and service agents can use, such as your MCP server.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site tells AI agents everything they can do with it, in one place (ARD catalog) What the grader found: Google's Lighthouse found no ARD catalog at /.well-known/ard.json. The fix, for a developer: Serve JSON at /.well-known/ard.json with an entries list that follows the ARD schema: each entry has a urn:air: identifier, a displayName, a type and a url. An MCP server's entry has the type application/mcp-server-card+json and points at its server card, at /mcp/server-card. Link it from every page with <link rel="ard" href="/.well-known/ard.json">. Lighthouse warns about a catalog found only at the older /.well-known/ai-catalog.json. Source: Lighthouse agentic browsing scoring, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/scoring; Agentic Resource Discovery specification, agenticresourcediscovery.org: https://agenticresourcediscovery.org/spec/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · about a day
  • Your site sends AI agents a plain-text version of each page (Markdown)CriticalFail

    Agents read Markdown faster and more accurately than a full web page, and it costs them fewer tokens, the units AI services count text in. Cloudflare calls Markdown the common language of agents.

    What we found: Cloudflare's scan asked your home page for Markdown and got none back.

    • Site does not support Markdown for Agents

    How to fix it

    Send each page as Markdown to agents that ask for it.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site sends AI agents a plain-text version of each page (Markdown) What the grader found: Cloudflare's scan asked your home page for Markdown and got none back. Details: - Site does not support Markdown for Agents The fix, for a developer: Answer a request whose Accept header names text/markdown with the page's content as Markdown and Content-Type: text/markdown. Cloudflare can convert pages at its edge, or the server can render the Markdown itself. Source: Markdown for Agents, Cloudflare: https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · about a day
  • AI agents can read your text without running scriptsCriticalPass

    Many agents read only the page your server sends and run none of its scripts. If your text appears only after scripts run, those agents see an empty page and answer from other sites. Claude's web fetch is one of them.

  • Your site tells AI agents what your business is (structured data)CriticalPass

    Structured data saves agents and search engines from guessing your type of business and contact details from the page. Google says it gives explicit clues about what a page means. Bing says it may help and promises nothing.

  • Every page has a summary for search resultsImportantPass

    Google may show your summary under the page's title in its results, and asks for a different one on every page. Without one, it picks a snippet from the page, which may be a line you would never choose.

  • Your pages say which language they are inImportantPass

    A declared language tells software how to read your page, from the voice a screen reader uses to the language a translation starts from. WCAG, the accessibility standard most laws point to, requires it.

41

Act

Can agents do what a customer asks, such as book, reserve, enquire or search? When someone asks an agent to act for them and your site doesn't let it, the agent acts on a site that does.

25% of your grade · 5 of 9 goals pass

  • AI agents can see your site's buttons and fields (accessibility tree)CriticalFail

    Agents find what they can click or fill in through the accessibility tree, the browser's list of a page's controls. A control missing from it does not exist for an agent, so it cannot book, buy or send an enquiry. Screen readers use the same tree.

    What we found: A control is missing from what AI agents can read of the page.

    • ARIA dialog and alertdialog nodes should have an accessible name: <div id="popUpWindowDialog_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow" class="popUpWindowDialog" role="dialog" aria-modal="true" aria-labelledby="popUpWindowHeader_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow">

    How to fix it

    Fix the accessibility problems Google's PageSpeed Insights lists for your home page, which are mostly buttons and fields with no label.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can see your site's buttons and fields (accessibility tree) What the grader found: A control is missing from what AI agents can read of the page. Details: - ARIA dialog and alertdialog nodes should have an accessible name: <div id="popUpWindowDialog_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow" class="popUpWindowDialog" role="dialog" aria-modal="true" aria-labelledby="popUpWindowHeader_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow"> The fix, for a developer: Give every button, link and field an accessible name, associate each field with a label, and remove invalid ARIA roles and attributes. PageSpeed lists the elements that fail. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · about a day
  • AI agents can complete tasks when they visit your site (WebMCP)CriticalFail

    Your site can tell agents what it lets a customer do, for example book a tour, reserve a table, ask a question, or search what's available. An agent can then do it for them, start to finish. Without that, the agent can only read your pages and send the customer to do it themselves, or do it on another site that lets it.

    How to fix it

    Let agents do every task a customer can do on your site, through WebMCP.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can complete tasks when they visit your site (WebMCP) What the grader found: Your home page offers agents no tasks to complete through WebMCP. The fix, for a developer: Register a WebMCP tool for every task a customer can do as the page loads: call document.modelContext.registerTool() with a name, a description, an input schema and an execute function, or add toolname and tooldescription attributes to the form. A name is 1 to 128 letters, digits, _, - or . Source: WebMCP for developers, Chrome: https://developer.chrome.com/docs/ai/webmcp; WebMCP, Draft Community Group Report, W3C Web Machine Learning Community Group: https://webmachinelearning.github.io/webmcp/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · about a day
  • AI agents can complete tasks without visiting your site (MCP server)CriticalFail

    Some agents never open a web page. They connect to a business directly and work from there. Giving them a way in means your site can be searched and booked by those agents too.

    What we found: Your site has no ARD catalog at /.well-known/ard.json, where agents look for an MCP server.

    • /.well-known/ard.json answers 404

    How to fix it

    Give agents a way to do every task a customer can do on your site without visiting it: an MCP server, listed in the site's ARD catalog.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can complete tasks without visiting your site (MCP server) What the grader found: Your site has no ARD catalog at /.well-known/ard.json, where agents look for an MCP server. Details: - /.well-known/ard.json answers 404 The fix, for a developer: Serve the MCP server card at /mcp/server-card, as the server card extension places it, and list it in /.well-known/ard.json as an entry with a urn:air: identifier, a displayName, the type application/mcp-server-card+json and the card's URL. Source: SEP-2127: MCP Server Cards, Model Context Protocol: https://modelcontextprotocol.io/seps/2127-mcp-server-cards; Agentic Resource Discovery specification, agenticresourcediscovery.org: https://agenticresourcediscovery.org/spec/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · a few days
  • AI agents can tell what custom controls are, such as date pickersImportantFail

    A custom date picker or slider is invisible to an agent unless its code gives it a name, so the agent cannot choose a date or set a price range. The same name tells people who use screen readers what the control is.

    What we found: A pop-up window has no name an AI agent can read.

    • Fix any of the following: aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute: <div id="popUpWindowDialog_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow" class="popUpWindowDialog" role="dialog" aria-modal="true" aria-labelledby="popUpWindowHeader_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow">

    How to fix it

    Name every custom control, such as date pickers, sliders and pop-up windows.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can tell what custom controls are, such as date pickers What the grader found: A pop-up window has no name an AI agent can read. Details: - Fix any of the following: aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute: <div id="popUpWindowDialog_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow" class="popUpWindowDialog" role="dialog" aria-modal="true" aria-labelledby="popUpWindowHeader_p_lt_zoneTop_rpWebpart_PopUp_PopUpWindow"> The fix, for a developer: Give each element with an ARIA control role an accessible name through aria-label or aria-labelledby. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents; Understanding Success Criterion 4.1.2: Name, Role, Value, W3C: https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · a few days
  • Hidden labels on your buttons and fields are accurate (ARIA)ImportantPass

    Agents trust these labels. A wrong one tells an agent a control is something it is not, such as a button marked as a heading, so it clicks the wrong thing or nothing. Screen readers trust them too, so people with disabilities are misled the same way.

  • Your text stands out clearly from its backgroundImportantPass

    Some agents look at a page as a picture, as people do, and pale text is easy for both to miss. The same contrast lets people with low vision read it. WCAG, the accessibility standard most laws point to, sets how much contrast text needs.

  • Buttons and links are big enough for an agent to clickImportantPass

    Agents that click where a button sits, as a person does, miss small or crowded targets, and so do people on phones and people with limited movement. Google's web.dev recommends targets of about 48 pixels, and WCAG sets a minimum of 24.

  • AI agents can move around your pages without a mouseImportantPass

    Agents move through a page from control to control, as keyboard users do. A page that skips controls or refreshes on its own keeps them from the button they need. WCAG requires every function to work from a keyboard, which people with disabilities rely on.

73

Performance

Does your site answer fast? Agents work against the clock, and so do people. A slow site costs them time, and they give that time to a faster one.

Speed comes from real visitors of your page over the last 28 days when Google has their numbers, and from a test on a phone when it does not.

25% of your grade · 5 of 10 goals pass

  • Return visits load fasterImportantFail

    Downloading every file again on each visit is slow and costly. When browsers keep the files, returning visitors see your page sooner.

    What we found: Use efficient cache lifetimes (Est savings of 835 KiB)

    • Use efficient cache lifetimes (Est savings of 835 KiB), from Google Maps
    • Use efficient cache lifetimes (Est savings of 835 KiB), from Facebook
    • Use efficient cache lifetimes (Est savings of 835 KiB), from Facebook

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Return visits load faster What the grader found: Use efficient cache lifetimes (Est savings of 835 KiB) Details: - Use efficient cache lifetimes (Est savings of 835 KiB), from Google Maps - Use efficient cache lifetimes (Est savings of 835 KiB), from Facebook - Use efficient cache lifetimes (Est savings of 835 KiB), from Facebook The fix, for a developer: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag. Source: Prevent unnecessary network requests with the HTTP Cache, Google: https://web.dev/articles/http-cache Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · about an hour
  • Your main content shows up quickly on phonesCriticalPartial

    Visitors leave pages that are slow to show anything, and Google uses this speed in ranking. It is called Largest Contentful Paint, one of Google's three Core Web Vitals.

    What we found: Largest Contentful Paint is 3.0 s for real visitors of this page, last 28 days, which Google rates needs improvement. First Contentful Paint is 2.7 s for real visitors of this page, last 28 days, which Google rates needs improvement. The page takes 10.0 s to fill in. Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone.

    • LCP request discovery
    • LCP breakdown
    • Render-blocking requests (Est savings of 4,040 ms)

    How to fix it

    Make the first screen load faster on phones, starting with its biggest image.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your main content shows up quickly on phones What the grader found: Largest Contentful Paint is 3.0 s for real visitors of this page, last 28 days, which Google rates needs improvement. First Contentful Paint is 2.7 s for real visitors of this page, last 28 days, which Google rates needs improvement. The page takes 10.0 s to fill in. Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone. Details: - LCP request discovery - LCP breakdown - Render-blocking requests (Est savings of 4,040 ms) The fix, for a developer: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. PageSpeed lists what holds it back. Source: Web Vitals, Google: https://web.dev/articles/vitals; Largest Contentful Paint (LCP), Google: https://web.dev/articles/lcp Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · a week or more
  • Images are sent at the size they are shownImportantPartial

    An image bigger than the space it fills wastes data and slows the page, most of all on a phone connection. Smaller images mean a faster page for every visitor.

    What we found: Improve image delivery (Est savings of 146 KiB). An image has no set size, so the page jumps as it loads.

    • Improve image delivery (Est savings of 146 KiB): <li id="accordionImg2" data-llclass="ll-img" class="ll-img">, from myleasestar.com
    • An image has no set size, so the page jumps as it loads.: <img src="https://capi.myleasestar.com/v2/dimg/79320873/400x400/79320873.png" alt="The Henry">, from myleasestar.com

    How to fix it

    Resize and compress your images before they go on the page.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Images are sent at the size they are shown What the grader found: Improve image delivery (Est savings of 146 KiB). An image has no set size, so the page jumps as it loads. Details: - Improve image delivery (Est savings of 146 KiB): <li id="accordionImg2" data-llclass="ll-img" class="ll-img">, from myleasestar.com - An image has no set size, so the page jumps as it loads.: <img src="https://capi.myleasestar.com/v2/dimg/79320873/400x400/79320873.png" alt="The Henry">, from myleasestar.com The fix, for a developer: Serve several sizes with srcset and sizes, use a modern format such as WebP or AVIF, and keep each image's width and height in the proportion it is shown. Source: Properly size images, Chrome: https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · about a day
  • Your pages are light to downloadImportantPartial

    Heavy pages take longer to load and cost visitors on mobile data real money. Chrome says large downloads are closely tied to long load times.

    What we found: Avoid enormous network payloads (Total size was 3,392 KiB). Reduce unused JavaScript (Est savings of 922 KiB). Reduce unused CSS (Est savings of 59 KiB). Minify JavaScript (Est savings of 57 KiB). Minify CSS (Est savings of 12 KiB). Legacy JavaScript (Est savings of 40 KiB).

    • Avoid enormous network payloads (Total size was 3,392 KiB), from Google Maps
    • Reduce unused JavaScript (Est savings of 922 KiB), from Google Maps
    • Minify JavaScript (Est savings of 57 KiB), from hy.ly

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages are light to download What the grader found: Avoid enormous network payloads (Total size was 3,392 KiB). Reduce unused JavaScript (Est savings of 922 KiB). Reduce unused CSS (Est savings of 59 KiB). Minify JavaScript (Est savings of 57 KiB). Minify CSS (Est savings of 12 KiB). Legacy JavaScript (Est savings of 40 KiB). Details: - Avoid enormous network payloads (Total size was 3,392 KiB), from Google Maps - Reduce unused JavaScript (Est savings of 922 KiB), from Google Maps - Minify JavaScript (Est savings of 57 KiB), from hy.ly The fix, for a developer: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. PageSpeed lists the files by size. Source: Avoid enormous network payloads, Chrome: https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · a few days
  • Your pages load without errorsImportantPartial

    An error in the browser often means part of your page is broken, such as a form that will not send. Chrome says each one is a problem to resolve.

    What we found: Browser errors were logged to the console. The page uses browser features that are being removed.

    • Failed to load resource: net::ERR_TIMED_OUT

    How to fix it

    Open the page in a browser's developer tools and clear the errors it lists.

    Fix with AI

    My website https://www.thehenrydenver.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages load without errors What the grader found: Browser errors were logged to the console. The page uses browser features that are being removed. Details: - Failed to load resource: net::ERR_TIMED_OUT The fix, for a developer: Fix each console error and browser issue, replace deprecated APIs, publish source maps for your scripts, and start the document with a doctype and a charset. Source: Browser errors were logged to the console, Chrome: https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/thehenrydenver-com

    Your web team · a few days
  • Your site responds quickly to taps and clicksCriticalPass

    A page that freezes after a tap feels broken, so visitors tap again or leave. Google rates a reaction under 200 milliseconds as good and counts it among its Core Web Vitals.

  • Your pages stay still while they loadCriticalPass

    When content jumps as a page loads, visitors tap the wrong thing, such as a link that moved under their finger. Google counts layout shift among its three Core Web Vitals.

  • Your site loads over a secure connectionImportantPass

    A secure connection stops others reading or changing what passes between your site and its visitors. Browsers mark pages without one as not secure, and Google counts it in page experience.

  • Your site does not ask visitors for permissions as they arriveImportantPass

    People distrust or are confused by a page that asks for their location the moment it opens. A field that blocks pasting makes a form harder to fill in.

  • Your server answers quicklyImportantPass

    Every visitor and agent waits for your server's first response before anything else can load. Chrome says a CDN, a network of servers close to your visitors, cuts that wait.

Fix it,

or see it rebuilt

These 13 fixes add up to about five weeks of your web team's time.

  • Send to your agency

    An email with what is wrong and a link to this report, so whoever runs the site has every fix and its line for the web team.

    Send to your agency
  • Explore with your AI

    Your own AI reads the report and tells you how to fix each issue and the effort each takes. It gets this, and nothing else:

    Read the Agent Grader report for thehenrydenver.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/thehenrydenver-com Then tell me how to fix each issue it lists, in order, and the effort each one takes, in plain words I can pass to my web team.

    Fix with AI

    Read the Agent Grader report for thehenrydenver.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/thehenrydenver-com Then tell me how to fix each issue it lists, in order, and the effort each one takes, in plain words I can pass to my web team.

  • See your site rebuilt

    Clutch rebuilds thehenrydenver.com from its address, and the new site doesn't have these issues. Free to preview, $39 a month once it goes live.

    See your site rebuilt

See if AI chooses you

A shopper's AI agent

Shopper in Denver, CO

Find me luxury apartments in Denver with studios or one or two bedrooms, a pool, a pet park, and a location near parks and good restaurants.

Find

Did a search lead the agent to you?

  1. Searched“luxury apartments Denver pool pet park studio one two bedroom”

    • viceroyobservatorypark.com
    • lorianapts.com
    • dylanrino.com
  2. Searched“Denver luxury apartments near parks restaurants pool dog park”

    • highlinepointe.com
    • apartmentlist.com
    • amli.com
  3. Openedamli.com/apartments/denver/golden-triangle-apartments/amli-golden-triangle

  4. Openedviceroyobservatorypark.com

  5. Openedlivecoda.com

Find failed

Search led the agent to amli.com, viceroyobservatorypark.com and livecoda.com, never to you. A real shopper's agent would have stopped there, so we sent ours to your site to see the rest.

Read

Did your site answer the shopper's question?

  1. We sent the agent tothehenrydenver.com

    It could read the page right away: 839 words

Read passed

Your site answered what the shopper asked.

The agent's answer

The Henry is a good fit on the points the shopper named, though my read was limited to its homepage. I did not open its floor plans, amenities, or neighborhood pages, so I can't confirm specific prices, unit sizes, or nearby restaurants.

Why it fits

  • Unit types: The site describes studios, 1 & 2 bedroom apartments with high-end amenities throughout.
  • Pool and pet park: It mentions a premier pool area that spans over an acre and a private yoga studio and a private pet park.
  • Parks: The location is tree-lined streets lead to verdant parks and playfields.
  • Dining/nightlife: The homepage doesn't name any restaurants. It says the area has the funky charm of S. Pearl St. as its cultural spine, so the shopper should check restaurant options nearby themselves.
  • Luxury: The site calls its 403 luxury units of inspired architecture and lists designer fixtures, stainless appliances, and open floor plans.

What the site says

  • Address: 201 East Mississippi Avenue, Denver, CO 80209, in the Platt Park neighborhood.
  • A current offer: Up to $1,000 Off Base Rent + 3 Months Free Parking on Select Units. The fine print says Speak to a leasing agent for details.
  • The site notes that terms apply; fees excluded. Offer may change.

Next steps

  • Check availability on the site's floor plans page: https://www.thehenrydenver.com/Floor-plans.aspx
  • Call (720) 702-4748. The listed hours are Monday: 10:00AM to 6:00PM, with Saturday 10:00AM to 5:00PM and Sunday 11:00AM to 5:00PM.
  • Ask a leasing agent about the current offer's terms and which units qualify, since the homepage says it applies only to select units.

Pages relied on

Act

Could the agent do the shopper's next step?

The shopper's next request: “Schedule a tour of a one-bedroom apartment this week and check what's available and what the move-in specials are.”

  1. Looked for a way to do it on your site

    Your site offers AI agents no way to do it

Act failed

The agent couldn't do it, so the shopper is left with a form, a phone number or a contact page.

The shopper's agent didn't find you, got its answer from your site and couldn't act for the shopper.

  1. Find

    Other sites ranked higher for this request, and your report found checks that hold search back.

  2. Read

    Passed. A few checks could still be stronger.

  3. Act

    Let AI agents do the shopper's next step on your site.

These sites are competing with you

SiteLetterFindReadActPerformance
thehenrydenver.comBuilt in ClutchAFindPassesReadPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
thehenrydenver.comDFind97Read47Act41Performance73
amli.comOpened by the AI agentCFind100Read68Act68Performance79
Passes 3 goals you don't
  • Your site sends AI agents a plain-text version of each page (Markdown)
  • AI agents can see your site's buttons and fields (accessibility tree)
viceroyobservatorypark.comOpened by the AI agent
livecoda.comOpened by the AI agent

See thehenrydenver.com rebuilt, without these issues

8th of 12 residence sites graded so far. See the board.

How we grade