D

Poor for AI agents

Speed: Fail (a lab test of this page on a phone)Core Web Vitals, Google

Start here.

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

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

    A control is missing from what AI agents can read of the page.

    What to do Fix the accessibility problems this report lists for your home page, which are mostly buttons and fields with no label.

    Your web team · about a daySee the check

  2. Fail·Act

    AI agents can complete tasks when they visit your site (WebMCP)

    Your home page offers agents no tasks to complete through WebMCP.

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

    Your web team · about a daySee the check

  3. Fail·Act

    AI agents can complete tasks without visiting your site (MCP server)

    Your ARD catalog cannot be read: it is not valid JSON.

    What to do 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.

    Your web team · a few daysSee 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.

45

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 11 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. Google's Lighthouse checks it as an emerging convention, and the grade counts standards likely to be adopted.

    What we found: We found no /llms.txt on your site.

    • There is no /llms.txt (it answered 404).

    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.camdenliving.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: We found no /llms.txt on your site. Details: - There is no /llms.txt (it answered 404). 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/camdenliving-com/2026-11-20

    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. Google's Lighthouse checks it too, and the grade counts standards likely to be adopted, such as this draft.

    What we found: The site's ARD catalog doesn't follow the format AI agents expect.

    • The manifest is not valid JSON: Unexpected token '<', "<!DOCTYPE "... is not valid 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.camdenliving.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: The site's ARD catalog doesn't follow the format AI agents expect. Details: - The manifest is not valid JSON: Unexpected token '<', "<!DOCTYPE "... is not valid 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">. A catalog found only at the older /.well-known/ai-catalog.json does not count. 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/camdenliving-com/2026-11-20

    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: We asked your home page for Markdown and got none back.

    • Answered with text/html

    How to fix it

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

    Fix with AI

    My website https://www.camdenliving.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: We asked your home page for Markdown and got none back. Details: - Answered with text/html 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/camdenliving-com/2026-11-20

    Your web team · about a day
  • Every page has a summary for search resultsImportantFail

    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.

    What we found: The page has no summary for search results.

    How to fix it

    Write a one or two sentence summary of every page, different on each.

    Fix with AI

    My website https://www.camdenliving.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Every page has a summary for search results What the grader found: The page has no summary for search results. The fix, for a developer: Add <meta name="description" content="..."> to the head of every page, with a sentence or two unique to that page. Source: How to Write Meta Descriptions, Google: https://developers.google.com/search/docs/appearance/snippet; Document does not have a meta description, Chrome: https://developer.chrome.com/docs/lighthouse/seo/meta-description 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/camdenliving-com/2026-11-20

    Your web team · about an hour
  • Headings give each page a clear outlineImportantPartial

    Clear headings show search engines and agents how a page is laid out, so they find the part that answers a question, such as your opening hours. Google's guide to its AI features recommends them.

    What we found: A heading skips a level. The page has no main heading.

    • A heading of level 4 follows one of level 2: <h4 class="jsx-3fdbbc4e40dbb800 w-240px max-w-240px lg:w-272px lg:max-w-272px text-26">
    • The page has no heading of level one: <html lang="en" style="--chat-launcher-lift: 184px;">

    How to fix it

    Give each page one main heading and put the headings under it in order.

    Fix with AI

    My website https://www.camdenliving.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Headings give each page a clear outline What the grader found: A heading skips a level. The page has no main heading. Details: - A heading of level 4 follows one of level 2: <h4 class="jsx-3fdbbc4e40dbb800 w-240px max-w-240px lg:w-272px lg:max-w-272px text-26"> - The page has no heading of level one: <html lang="en" style="--chat-launcher-lift: 184px;"> The fix, for a developer: Use h1 once, then h2 to h6 without skipping a level, and remove or fill any heading element that has no text. Source: Optimizing your website for generative AI features on Google Search, Google: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide; Understanding Success Criterion 1.3.1: Info and Relationships, W3C: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.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/camdenliving-com/2026-11-20

    Your web team · about an hour
  • Each page marks its header, main content and footer (landmarks)ImportantPartial

    Agents and screen readers jump between a page's regions to reach the part they need, such as the main content past the navigation. Content outside every region, or two navigation regions with the same name, leaves them reading the page from the top.

    What we found: Some content sits outside every marked region of the page. A region has the same name as another region of its kind.

    • Its content sits outside every landmark: <a href="#" class="jsx-1224211768 flex flex-row items-center justify-center w-full text-white bg-blue skip-to-content-link">
    • 2 navigation landmarks share the name "log in submenu": <div role="navigation" aria-label="Log In submenu" class="dropdown-menu">

    How to fix it

    Mark each page's header, main content and footer as regions, and put everything on the page inside one.

    Fix with AI

    My website https://www.camdenliving.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Each page marks its header, main content and footer (landmarks) What the grader found: Some content sits outside every marked region of the page. A region has the same name as another region of its kind. Details: - Its content sits outside every landmark: <a href="#" class="jsx-1224211768 flex flex-row items-center justify-center w-full text-white bg-blue skip-to-content-link"> - 2 navigation landmarks share the name "log in submenu": <div role="navigation" aria-label="Log In submenu" class="dropdown-menu"> The fix, for a developer: Use one header, one main and one footer element at the top level of the page, keep every piece of content inside a landmark, and give landmarks of the same kind, such as two nav elements, different aria-labels. Source: Learn Accessibility: Content structure, Google: https://web.dev/learn/accessibility/structure; Understanding Success Criterion 1.3.1: Info and Relationships, W3C: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.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/camdenliving-com/2026-11-20

    Your web team · about a day
  • AI agents can tell what your images show (alt text)ImportantPartial

    Agents rely on an image's text description, called alt text, to know what it shows, the same description that lets people who cannot see the image use the page. Google calls alt text the most important attribute for describing an image.

    What we found: An image has a description that repeats the words beside it.

    • An image has a description that repeats the words beside it: <img class="bg-transparent ml-1 cursor-pointer" src="/icons/green/search.svg" alt="Search">

    How to fix it

    Add a short description to every meaningful image.

    Fix with AI

    My website https://www.camdenliving.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 your images show (alt text) What the grader found: An image has a description that repeats the words beside it. Details: - An image has a description that repeats the words beside it: <img class="bg-transparent ml-1 cursor-pointer" src="/icons/green/search.svg" alt="Search"> The fix, for a developer: Give each meaningful img an alt attribute that says what it shows, an empty alt="" to decorative images, and a text name to image buttons, svg graphics and objects. Source: Image SEO Best Practices, Google: https://developers.google.com/search/docs/appearance/google-images; Understanding Success Criterion 1.1.1: Non-text Content, W3C: https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.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/camdenliving-com/2026-11-20

    Your web team · a few days
  • 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.

  • 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.

  • Your lists and tables are built so agents can read themImportantPass

    Agents read a list or a table as one only when the page's code marks it as one. Otherwise your prices or opening hours reach them as loose lines. The same code lets people who use screen readers follow them, and WCAG requires it.

44

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 · 4 of 10 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-*] attributes match their roles: <span tabindex="0" class="flex min-w-max" aria-expanded="false">
    • Links have a discernible name: <a id="primary-navigation-comparison-list-button-mobile" href="/unit-comparison">
    • Elements with role="none" or role="presentation" do not have conflicts: <img class="bg-transparent cursor-pointer" src="/icons/blue/list_empty.svg" alt="">

    How to fix it

    Fix the accessibility problems this report lists for your home page, which are mostly buttons and fields with no label.

    Fix with AI

    My website https://www.camdenliving.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-*] attributes match their roles: <span tabindex="0" class="flex min-w-max" aria-expanded="false"> - Links have a discernible name: <a id="primary-navigation-comparison-list-button-mobile" href="/unit-comparison"> - Elements with role="none" or role="presentation" do not have conflicts: <img class="bg-transparent cursor-pointer" src="/icons/blue/list_empty.svg" alt=""> 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. The report 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/camdenliving-com/2026-11-20

    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.camdenliving.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/camdenliving-com/2026-11-20

    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 ARD catalog cannot be read: it is not valid JSON.

    • A body that does not parse as JSON

    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.camdenliving.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 ARD catalog cannot be read: it is not valid JSON. Details: - A body that does not parse as JSON 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/camdenliving-com/2026-11-20

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

    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.

    What we found: An element has ARIA labels its role doesn't allow. An element is marked as decoration but can still be clicked or named.

    • aria-expanded is not allowed on role generic: <span tabindex="0" class="flex min-w-max" aria-expanded="false">
    • It is marked as decoration, but Chrome exposes it as img: <img class="bg-transparent cursor-pointer" src="/icons/blue/list_empty.svg" alt="">

    How to fix it

    Fix the ARIA errors this report lists and use standard buttons and fields where they exist.

    Fix with AI

    My website https://www.camdenliving.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Hidden labels on your buttons and fields are accurate (ARIA) What the grader found: An element has ARIA labels its role doesn't allow. An element is marked as decoration but can still be clicked or named. Details: - aria-expanded is not allowed on role generic: <span tabindex="0" class="flex min-w-max" aria-expanded="false"> - It is marked as decoration, but Chrome exposes it as img: <img class="bg-transparent cursor-pointer" src="/icons/blue/list_empty.svg" alt=""> The fix, for a developer: Use native elements first, give each ARIA role its required attributes and children, remove attributes the role does not allow, and keep ids unique. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents; Accessible Rich Internet Applications (WAI-ARIA) 1.2, W3C: https://www.w3.org/TR/wai-aria-1.2/ 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/camdenliving-com/2026-11-20

    Your web team · a few days
  • Buttons and links are big enough for an agent to clickImportantPartial

    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.

    What we found: A button or link is too small, or too close to another, to tap.

    • A target of 31 by 17 pixels, closer than 24 pixels' room to another: <a id="footer-blog-link" class="mr-6 font-bold cursor-pointer" target="_self" rel="noreferrer" href="/blog">

    How to fix it

    Make small buttons and tightly packed links bigger on phones.

    Fix with AI

    My website https://www.camdenliving.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Buttons and links are big enough for an agent to click What the grader found: A button or link is too small, or too close to another, to tap. Details: - A target of 31 by 17 pixels, closer than 24 pixels' room to another: <a id="footer-blog-link" class="mr-6 font-bold cursor-pointer" target="_self" rel="noreferrer" href="/blog"> The fix, for a developer: Make each target at least 24 by 24 CSS pixels, or leave enough space around smaller ones, and aim for around 48 pixels. Set width=device-width in the viewport tag so taps answer at once. Source: Accessible tap targets, Google: https://web.dev/articles/accessible-tap-targets; Understanding Success Criterion 2.5.8: Target Size (Minimum), W3C: https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.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/camdenliving-com/2026-11-20

    Your web team · about an hour
  • AI agents can tell what every form field asks forCriticalPass

    An agent fills in a form by reading each field's label. Without one it is left guessing, so the enquiry or booking is never sent. Labels serve people who use screen readers the same way, and Chrome says missing ones can block agents.

  • AI agents can tell what custom controls are, such as date pickersImportantPass

    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.

  • 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.

  • 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.

79

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 · 4 of 10 goals pass

  • 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: The main content takes 3.4 s to show. The page takes 4.5 s to fill in. Lab test on a phone.

    • fetchpriority=high should be applied: <img class="bg-transparent object-cover w-full lg:h-full" src="https://images.ctfassets.net/pg6xj64qk0kh/7anGRaRXyMyfWDKhkGf86B/853aa010d9d7af206295284ec8b90d76/Fortune-Accolades-2026-100_Best_Compan…
    • Holds the first paint
    • In the longest chain, 195 ms from the first request

    How to fix it

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

    Fix with AI

    My website https://www.camdenliving.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: The main content takes 3.4 s to show. The page takes 4.5 s to fill in. Lab test on a phone. Details: - fetchpriority=high should be applied: <img class="bg-transparent object-cover w-full lg:h-full" src="https://images.ctfassets.net/pg6xj64qk0kh/7anGRaRXyMyfWDKhkGf86B/853aa010d9d7af206295284ec8b90d76/Fortune-Accolades-2026-100_Best_Compan… - Holds the first paint - In the longest chain, 195 ms from the first request The fix, for a developer: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. The report 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/camdenliving-com/2026-11-20

    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. An image is stretched or squashed. An image has no set size, so the page jumps as it loads.

    • Could be 42 KiB smaller: more compression: <img class="bg-transparent object-cover w-full h-48" src="https://images.ctfassets.net/pg6xj64qk0kh/4kLKwBJNFGxGO9zWeL9tR6/27f60d5e420ca5fecf9fbc3a0d001922/IMG_4626__1_.jpeg?w=326" alt="Camden logo">, from ctfassets.net
    • Shown at 120 × 120 (1.00), its file is 592 × 395 (1.50): <img class="bg-transparent object-cover w-full h-full sm:rounded" src="https://images.ctfassets.net/pg6xj64qk0kh/6ndqgdxyac693GxYnuc52e/3e6a9f301852dc2550e96c5527fce326/Couple_on_patio.jpg?w=296" alt…, from ctfassets.net
    • An image has no set size, so the page jumps as it loads: <img class="bg-transparent cursor-pointer" src="/icons/blue/menu.svg" alt="Open Menu">

    How to fix it

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

    Fix with AI

    My website https://www.camdenliving.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. An image is stretched or squashed. An image has no set size, so the page jumps as it loads. Details: - Could be 42 KiB smaller: more compression: <img class="bg-transparent object-cover w-full h-48" src="https://images.ctfassets.net/pg6xj64qk0kh/4kLKwBJNFGxGO9zWeL9tR6/27f60d5e420ca5fecf9fbc3a0d001922/IMG_4626__1_.jpeg?w=326" alt="Camden logo">, from ctfassets.net - Shown at 120 × 120 (1.00), its file is 592 × 395 (1.50): <img class="bg-transparent object-cover w-full h-full sm:rounded" src="https://images.ctfassets.net/pg6xj64qk0kh/6ndqgdxyac693GxYnuc52e/3e6a9f301852dc2550e96c5527fce326/Couple_on_patio.jpg?w=296" alt…, from ctfassets.net 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/camdenliving-com/2026-11-20

    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: Avoids enormous network payloads (2,742 KiB). Reduce unused JavaScript (712 KiB unused). Reduce unused CSS (18 KiB unused). Legacy JavaScript.

    • 357 KiB
    • 190 KiB of 315 KiB unused
    • 18 KiB of 20 KiB unused: <style id="onetrust-style">

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://www.camdenliving.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: Avoids enormous network payloads (2,742 KiB). Reduce unused JavaScript (712 KiB unused). Reduce unused CSS (18 KiB unused). Legacy JavaScript. Details: - 357 KiB - 190 KiB of 315 KiB unused - 18 KiB of 20 KiB unused: <style id="onetrust-style"> The fix, for a developer: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. The report 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/camdenliving-com/2026-11-20

    Your web team · a few days
  • Return visits load fasterImportantPartial

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

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://www.camdenliving.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 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/camdenliving-com/2026-11-20

    Your web team · about an hour
  • 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 (5 errors). The page has problems Chrome lists in its Issues panel. A large script has no working source map. The page sets cookies for other companies.

    • /_next/static/css/ae3cbd25a43f8ea7.css: Failed to load resource: the server responded with a status of 502 ()
    • Cookie: https://googleads.g.doubleclick.net/pagead/viewthroughconversion/16860181565/?random=1795169488177&cv=11&fst=1795169488177&bg=ffffff&guid=ON&async=1&en=gtag.config&gtm=45je6bi0h2v887167241za20ozb71308765zd71308765xecxf1&gcd=13l3l3l3l1l1&dma=0&tag_exp=115616986~115938466~115938468~120213116~120385422~120469145~120469153~121246026~121246034~123322202~123785232&u_w=412&u_h=823&url=https%3A%2F%2Fwww.camdenliving.com%2F&rcb=7&frm=0&tiba=Luxury%20Apartments%20for%20Rent%20-%20camdenliving.com&hn=www.googleadservices.com&npa=0&pscdl=noapi&auid=1396071224.1795169488&uaa=&uab=64&uafvl=Chromium%3B158.0.8127.36%7CNot.A%252FBrand%3B24.0.0.0%7CGoogle%2520Chrome%3B158.0.8127.36&uamb=1&uam=moto%20g%20power%20(2022)&uap=Android&uapv=11.0&uaw=0&data=event%3Dgtag.config&ept=9&rfmt=3&fmt=4, from Google/Doubleclick Ads
    • /_next/static/chunks/pages/_app-7249796cc440c998.js (1300 KiB) names no source map.

    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.camdenliving.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 (5 errors). The page has problems Chrome lists in its Issues panel. A large script has no working source map. The page sets cookies for other companies. Details: - /_next/static/css/ae3cbd25a43f8ea7.css: Failed to load resource: the server responded with a status of 502 () 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/camdenliving-com/2026-11-20

    Your web team · a few days
  • Your server answers quicklyImportantPartial

    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.

    What we found: Document request latency.

    • Had redirects (1 redirects, +85 ms)

    How to fix it

    Speed up its first response, for example with a CDN in front of it.

    Fix with AI

    My website https://www.camdenliving.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 server answers quickly What the grader found: Document request latency. Details: - Had redirects (1 redirects, +85 ms) The fix, for a developer: Serve the page through a CDN or edge network over HTTP/2 or HTTP/3, compress text with gzip or Brotli, cache the document at the edge, and avoid redirects. Source: Reduce server response times (TTFB), Chrome: https://developer.chrome.com/docs/lighthouse/performance/server-response-time 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/camdenliving-com/2026-11-20

    Your web team · about a day
  • 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.

Fix it,

or see it rebuilt

These 20 fixes add up to about seven 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 camdenliving.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/camdenliving-com/2026-11-20 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 camdenliving.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/camdenliving-com/2026-11-20 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 camdenliving.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 Charlotte, North Carolina

Find me luxury apartments for rent near downtown with a pool and gym, and tell me what they cost.

Find

Did a search lead the agent to you?

  1. Searched“luxury apartments uptown Charlotte pool gym rent prices”

    • maac.com
    • apartmenthomeliving.com
    • apartments.com
  2. Searched“luxury apartments near downtown Charlotte NC pool fitness center”

    • maac.com
    • uptown550.com
    • liveascentuptown.com
  3. Openeduptown550.com

  4. Openedliveascentuptown.com/amenities

  5. Openedmaac.com/north-carolina/charlotte/maa-uptown

Find failed

Search led the agent to uptown550.com, liveascentuptown.com and maac.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 tocamdenliving.com

    It could read the page right away: 551 words

Read partly passed

The agent read your site, but what it found there didn't answer what the shopper asked.

The agent's answer

I read the Camden homepage, and it is a partial fit for your request. It lists one Charlotte community with a price, but the homepage doesn't confirm a pool, a gym, or a downtown location for it.

Why it may fit: Camden is a luxury apartment operator, and its homepage features Camden Blakeney, 1 - 3 bedrooms starting at $1,649. Its link goes to a Charlotte-specific page (https://www.camdenliving.com/apartments/charlotte-nc/camden-blakeney).

What the site says about your criteria:

  • Price: The only price on the homepage is the Camden Blakeney starting rate of $1,649 for 1 to 3 bedrooms. The homepage doesn't say whether that is monthly or what it includes, so confirm it on the property page.
  • Pool: The homepage has no pool listing for Charlotte. A testimonial mentions a resort-style swimming pool, but it comes from a Dallas resident about the Camden Design District, so it doesn't apply to Charlotte.
  • Gym: I found no mention of a fitness center on the homepage.
  • Near downtown: The homepage doesn't give the Blakeney address or neighborhood, so I can't confirm proximity to downtown Charlotte.
  • Blog: A post titled Luxury Living in Charlotte at Camden Blakeney Apartments exists, but I didn't open it, so I can't report what it says.

Next step: Open the Camden Blakeney Charlotte page and check the amenities list for a pool, gym, address, and current rents. If those details aren't there, call Camden's leasing line at 713-354-2500 (the number on the site, which may be a general line) and ask about the pool, gym, distance to downtown, and the rent for the unit size you need.

Pages I relied on: https://camdenliving.com/ (homepage only). I did not read the Camden Blakeney property page or the blog, so the amenity, location, and pricing details above are unverified.

Act

Could the agent do the shopper's next step?

The shopper's next request: “Book a tour of one of those apartments for this weekend and start an application.”

  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, read your site but didn't get its answer there 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

    Say what you offer, where and for how much, in plain words on your pages.

  3. Act

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

These sites are competing with you

SiteLetterFindReadActPerformance
camdenliving.comBuilt in ClutchAFindPassesReadPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
camdenliving.comDFind97Read45Act44Performance79
uptown550.comOpened by the AI agent
liveascentuptown.comOpened by the AI agent
maac.comOpened by the AI agent

See camdenliving.com rebuilt, without these issues

1st of 2 residence sites graded so far. See the board.

How we grade