D

Poor for AI agents

Speed: Pass (real visitors, last 28 days)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)

    Accessibility tree is not well-formed

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

    Your web team · about a daySee the check

  2. Fail·Read

    Headings give each page a clear outline

    Heading elements are not in a sequentially-descending order

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

    Your web team · about an hourSee the check

  3. Fail·Read

    Your lists and tables are built so agents can read them

    Lists do not contain only <li> elements and script supporting elements (<script> and <template>). List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements.

    What to do Build price lists, schedules and comparisons as real lists and tables.

    Your web team · a few daysSee the check

90

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 instructions to AI agents and search engines have no errors (robots.txt)ImportantFail

    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.

    What we found: robots.txt is not valid (1 error found)

    How to fix it

    Fix the errors Google's PageSpeed Insights lists in robots.txt.

    Fix with AI

    My website https://www.wellorymidcity.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 instructions to AI agents and search engines have no errors (robots.txt) What the grader found: robots.txt is not valid (1 error found) The fix, for a developer: Fix the robots.txt lines Lighthouse reports as invalid. PageSpeed Insights lists each one with its line number. Source: Robots.txt Introduction and Guide, Google: https://developers.google.com/search/docs/crawling-indexing/robots/intro; RFC 9309, Robots Exclusion Protocol, section 2.3.1, IETF: https://www.rfc-editor.org/rfc/rfc9309#section-2.3.1 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/wellorymidcity-com

    Your web team · about an hour

    Tested by Google LighthouseRobots.txt Introduction and Guide, Google

    Report an issue with this check
  • 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.

    Tested by CloudflareWeb fetch tool, Anthropic

    Report an issue with this check
  • 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.

    Tested by CloudflareOverview of OpenAI crawlers, OpenAI

    Report an issue with this check
  • 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.

    Tested by Google LighthouseAI features and your website, Google

    Report an issue with this check
  • 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.

    Tested by CloudflareBuild and submit a sitemap, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseInfluencing Title Links in Google Search, Google

    Report an issue with this check
  • 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.

    Tested by ClutchHow Google Search handles HTTP status codes, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseHow to Specify a Canonical with rel="canonical" and Other Methods, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseAvoid multiple page redirects, Chrome

    Report an issue with this check

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 · 5 of 11 goals pass

  • Headings give each page a clear outlineImportantFail

    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: Heading elements are not in a sequentially-descending order

    • Fix any of the following: Heading order invalid: <h4 class="widget-title">

    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.wellorymidcity.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: Heading elements are not in a sequentially-descending order Details: - Fix any of the following: Heading order invalid: <h4 class="widget-title"> 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/wellorymidcity-com

    Your web team · about an hour

    Tested by Google LighthouseOptimizing your website for generative AI features on Google Search, Google

    Report an issue with this check
  • Your lists and tables are built so agents can read themImportantFail

    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.

    What we found: Lists do not contain only <li> elements and script supporting elements (<script> and <template>). List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements.

    • Fix all of the following: List element has direct children that are not allowed: div: <ul class="splide__list">
    • Fix any of the following: List item does not have a <ul> or <ol> parent element. Ensure the <li> is a direct child of a <ul> or <ol>, or that the parent has role="list".: <li class="splide__slide carousel__item">

    How to fix it

    Build price lists, schedules and comparisons as real lists and tables.

    Fix with AI

    My website https://www.wellorymidcity.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 lists and tables are built so agents can read them What the grader found: Lists do not contain only <li> elements and script supporting elements (<script> and <template>). List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements. Details: - Fix all of the following: List element has direct children that are not allowed: div: <ul class="splide__list"> - Fix any of the following: List item does not have a <ul> or <ol> parent element. Ensure the <li> is a direct child of a <ul> or <ol>, or that the parent has role="list".: <li class="splide__slide carousel__item"> The fix, for a developer: Use ul, ol and dl with li, dt and dd children, and table markup with th header cells for tabular data, rather than line breaks and styled divs. Source: Rule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axe: https://dequeuniversity.com/rules/axe/4.13/list; 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/wellorymidcity-com

    Your web team · a few days

    Tested by Google LighthouseRule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axe

    Report an issue with this check
  • Your site has a short guide for AI agents (llms.txt)ImportantFail

    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.wellorymidcity.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/wellorymidcity-com

    Your web team · about an hour

    Tested by Google Lighthousellms.txt audit, Chrome

    Report an issue with this check
  • Your site tells AI agents everything they can do with it, in one place (ARD catalog)ImportantFail

    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.wellorymidcity.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/wellorymidcity-com

    Your web team · about a day

    Tested by Google LighthouseLighthouse agentic browsing scoring, Chrome

    Report an issue with this check
  • Your site sends AI agents a plain-text version of each page (Markdown)ImportantFail

    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.wellorymidcity.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/wellorymidcity-com

    Your web team · about a day

    Tested by CloudflareMarkdown for Agents, Cloudflare

    Report an issue with this check
  • Your site says how AI may use its content (Content Signals)ImportantFail

    Content Signals let you say, in one line, whether AI may use your content for answers, for training, or both. They follow AI Preferences, a proposal at the IETF, the body that sets internet standards.

    What we found: Cloudflare found no Content-Signal line in your robots.txt.

    • No Content Signals found in robots.txt

    How to fix it

    Decide whether your content may be used for search, AI answers and AI training, and ask the people who run your site to say so in robots.txt.

    Fix with AI

    My website https://www.wellorymidcity.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 says how AI may use its content (Content Signals) What the grader found: Cloudflare found no Content-Signal line in your robots.txt. Details: - No Content Signals found in robots.txt The fix, for a developer: Add a Content-Signal line to robots.txt under the user agents it covers, such as Content-Signal: search=yes, ai-input=yes, ai-train=no. Source: Content Signals, Content Signals: https://contentsignals.org/ 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/wellorymidcity-com

    Your web team · about an hour

    Tested by CloudflareContent Signals, Content Signals

    Report an issue with this check
  • 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.

    Tested by ClutchUnderstand JavaScript SEO basics, Google Search Central

    Report an issue with this check
  • Your site tells AI agents what your business is (structured data)ImportantPass

    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.

    Tested by ClutchIntro to structured data, Google

    Report an issue with this check
  • AI agents can tell what your images show (alt text)ImportantPass

    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.

    Tested by Google LighthouseImage SEO Best Practices, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseHow to Write Meta Descriptions, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseRule html-has-lang: <html> element must have a lang attribute, Deque axe

    Report an issue with this check
35

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 · 1 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: Accessibility tree is not well-formed

    • Elements must only use supported ARIA attributes: <span class="underline text-ll-announcements-bar-text pl-2 cursor-pointer" data-ll-accouncement-expand="" data-ll-special-expand="" aria-haspopup="dialog" aria-controls="ll-announcements-details" aria-expanded="false">
    • Buttons must have discernible text: <button class="splide__arrow arrow splide__arrow--prev">

    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.wellorymidcity.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: Accessibility tree is not well-formed Details: - Elements must only use supported ARIA attributes: <span class="underline text-ll-announcements-bar-text pl-2 cursor-pointer" data-ll-accouncement-expand="" data-ll-special-expand="" aria-haspopup="dialog" aria-controls="ll-announcements-details" aria-expanded="false"> - Buttons must have discernible text: <button class="splide__arrow arrow splide__arrow--prev"> 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/wellorymidcity-com

    Your web team · about a day

    Tested by Google LighthouseAccessibility for agents, Chrome

    Report an issue with this check
  • AI agents can complete tasks when they visit your site (WebMCP)ImportantFail

    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.wellorymidcity.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/wellorymidcity-com

    Your web team · about a day

    Tested by Google LighthouseCloudflareWebMCP for developers, Chrome

    Report an issue with this check
  • AI agents can complete tasks without visiting your site (MCP server)ImportantFail

    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 403

    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.wellorymidcity.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 403 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/wellorymidcity-com

    Your web team · a few days

    Tested by ClutchSEP-2127: MCP Server Cards, Model Context Protocol

    Report an issue with this check
  • Videos and embedded content have text AI agents can readImportantFail

    An agent cannot watch a video or see inside embedded content. Captions and titles tell it what is there, such as directions in a map or a booking form from another service, as they do for people who are deaf or blind.

    What we found: <frame> or <iframe> elements do not have a title

    • Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation": <iframe loading="lazy" src="about:blank" allowfullscreen="" allow="fullscreen; geolocation" width="100%" style="min-height: 90dvh; max-height: 90dvh;" data-rocket-lazyload="fitvidscompatible" data-lazy-src="https://viewer.mapme.com/midcitydistrictmap">

    How to fix it

    Add captions to your videos and a title to every embedded map, form and player.

    Fix with AI

    My website https://www.wellorymidcity.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Videos and embedded content have text AI agents can read What the grader found: <frame> or <iframe> elements do not have a title Details: - Fix any of the following: Element has no title attribute 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's default semantics were not overridden with role="none" or role="presentation": <iframe loading="lazy" src="about:blank" allowfullscreen="" allow="fullscreen; geolocation" width="100%" style="min-height: 90dvh; max-height: 90dvh;" data-rocket-lazyload="fitvidscompatible" data-lazy-src="https://viewer.mapme.com/midcitydistrictmap"> The fix, for a developer: Add a captions track to each video and a title attribute to each iframe and frame. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents; Understanding Success Criterion 1.2.2: Captions (Prerecorded), W3C: https://www.w3.org/WAI/WCAG22/Understanding/captions-prerecorded.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/wellorymidcity-com

    Your web team · a few days

    Tested by Google LighthouseAccessibility for agents, Chrome

    Report an issue with this check
  • 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: [aria-*] attributes do not match their roles.

    • Fix all of the following: ARIA attribute is not allowed: aria-expanded="false": <span class="underline text-ll-announcements-bar-text pl-2 cursor-pointer" data-ll-accouncement-expand="" data-ll-special-expand="" aria-haspopup="dialog" aria-controls="ll-announcements-details" aria-expanded="false">

    How to fix it

    Fix the ARIA errors Google's PageSpeed Insights lists and use standard buttons and fields where they exist.

    Fix with AI

    My website https://www.wellorymidcity.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: [aria-*] attributes do not match their roles. Details: - Fix all of the following: ARIA attribute is not allowed: aria-expanded="false": <span class="underline text-ll-announcements-bar-text pl-2 cursor-pointer" data-ll-accouncement-expand="" data-ll-special-expand="" aria-haspopup="dialog" aria-controls="ll-announcements-details" aria-expanded="false"> 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: Rule aria-roles: ARIA roles used must conform to valid values, Deque axe: https://dequeuniversity.com/rules/axe/4.13/aria-roles; 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/wellorymidcity-com

    Your web team · a few days

    Tested by Google LighthouseRule aria-roles: ARIA roles used must conform to valid values, Deque axe

    Report an issue with this check
  • Your text stands out clearly from its backgroundImportantPartial

    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.

    What we found: Background and foreground colors do not have a sufficient contrast ratio.

    • Fix any of the following: Element has insufficient color contrast of 2.76 (foreground color: #ffffff, background color: #b1977e, font size: 9.8pt (13px), font weight: bold). Expected contrast ratio of 4.5:1: <span>

    How to fix it

    Darken pale text, underline links inside paragraphs and let visitors zoom.

    Fix with AI

    My website https://www.wellorymidcity.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 text stands out clearly from its background What the grader found: Background and foreground colors do not have a sufficient contrast ratio. Details: - Fix any of the following: Element has insufficient color contrast of 2.76 (foreground color: #ffffff, background color: #b1977e, font size: 9.8pt (13px), font weight: bold). Expected contrast ratio of 4.5:1: <span> The fix, for a developer: Reach a contrast ratio of 4.5 to 1 for normal text, mark links in text with more than color, and leave user-scalable and maximum-scale out of the viewport tag. Source: Rule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe: https://dequeuniversity.com/rules/axe/4.13/color-contrast; Understanding Success Criterion 1.4.3: Contrast (Minimum), W3C: https://www.w3.org/WAI/WCAG22/Understanding/contrast-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/wellorymidcity-com

    Your web team · about a day

    Tested by Google LighthouseRule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe

    Report an issue with this check
  • 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: Touch targets do not have sufficient size or spacing.

    • Fix any of the following: Target has insufficient size (111px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20.8px instead of at least 24px.: <a target="_blank" href="https://wellorymidcity.securecafe.com/residentservices/wellory/userlogin.a…" aria-label="Open this area in a new tab" role="button">

    How to fix it

    Make small buttons and tightly packed links bigger on phones.

    Fix with AI

    My website https://www.wellorymidcity.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: Touch targets do not have sufficient size or spacing. Details: - Fix any of the following: Target has insufficient size (111px by 21px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 20.8px instead of at least 24px.: <a target="_blank" href="https://wellorymidcity.securecafe.com/residentservices/wellory/userlogin.a…" aria-label="Open this area in a new tab" role="button"> 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/wellorymidcity-com

    Your web team · about an hour

    Tested by Google LighthouseAccessible tap targets, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseAccessibility for agents, Chrome

    Report an issue with this check
  • Your site tells AI agents about its other servicesImportantNot yet

    Each one tells agents about a service they can use, such as an API for checking stock. Few businesses that sell to the public need them yet, so they earn bonus points and never cost any.

    What we found: Your home page sends no Link headers that point agents to these files. Your site has no API catalog. Your site has no Agent Skills index. Your site has no A2A agent card.

    • No Link headers found on target page
    • API Catalog returned status 403
    • Agent Skills index returned status 403

    How to fix it

    Ask the people who run your site which of these fit your business, such as an API catalog if you offer an API.

    Fix with AI

    My website https://www.wellorymidcity.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 about its other services What the grader found: Your home page sends no Link headers that point agents to these files. Your site has no API catalog. Your site has no Agent Skills index. Your site has no A2A agent card. Details: - No Link headers found on target page - API Catalog returned status 403 - Agent Skills index returned status 403 The fix, for a developer: Publish the files that fit: an API catalog at /.well-known/api-catalog, an Agent Skills index, an A2A agent card at /.well-known/agent-card.json, and Link headers on the home page that point to them. Source: RFC 8288, Web Linking, IETF: https://www.rfc-editor.org/rfc/rfc8288; RFC 9727, api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs, IETF: https://www.rfc-editor.org/rfc/rfc9727 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/wellorymidcity-com

    Your web team · about a day

    Tested by CloudflareRFC 8288, Web Linking, IETF

    Report an issue with this check
91

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

  • Your main content shows up quickly on phonesImportantPartial

    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: First Contentful Paint is 2.1 s for real visitors of this page, last 28 days, which Google rates needs improvement. Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone.

    • Network dependency tree

    How to fix it

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

    Fix with AI

    My website https://www.wellorymidcity.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: First Contentful Paint is 2.1 s for real visitors of this page, last 28 days, which Google rates needs improvement. Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone. Details: - Network dependency tree 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/wellorymidcity-com

    Your web team · a week or more

    Tested by Google LighthouseWeb Vitals, Google

    Report an issue with this check
  • 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 (Est savings of 130 ms).

    • Network Round Trip Times (0 ms)
    • Server Backend Latencies (30 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.wellorymidcity.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 (Est savings of 130 ms). Details: - Network Round Trip Times (0 ms) - Server Backend Latencies (30 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/wellorymidcity-com

    Your web team · about a day

    Tested by Google LighthouseReduce server response times (TTFB), Chrome

    Report an issue with this check
  • 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 161 KiB).

    • Improve image delivery (Est savings of 161 KiB): <img decoding="async" width="1920" height="1280" src="https://wellorymidcity.b-cdn.net/wp-content/uploads/2026/02/shoootin-photo…" class="cards__list-item-img entered lazyloaded" alt="shoootin photo 31" data-lazy-src="https://wellorymidcity.b-cdn.net/wp-content/uploads/2026/02/shoootin-photo…" data-ll-status="loaded">, from b-cdn.net

    How to fix it

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

    Fix with AI

    My website https://www.wellorymidcity.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 161 KiB). Details: - Improve image delivery (Est savings of 161 KiB): <img decoding="async" width="1920" height="1280" src="https://wellorymidcity.b-cdn.net/wp-content/uploads/2026/02/shoootin-photo…" class="cards__list-item-img entered lazyloaded" alt="shoootin photo 31" data-lazy-src="https://wellorymidcity.b-cdn.net/wp-content/uploads/2026/02/shoootin-photo…" data-ll-status="loaded">, from b-cdn.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/wellorymidcity-com

    Your web team · about a day

    Tested by Google LighthouseProperly size images, Chrome

    Report an issue with this check
  • 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: Reduce unused CSS (Est savings of 18 KiB).

    • Reduce unused CSS (Est savings of 18 KiB), from b-cdn.net

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://www.wellorymidcity.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: Reduce unused CSS (Est savings of 18 KiB). Details: - Reduce unused CSS (Est savings of 18 KiB), from b-cdn.net 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/wellorymidcity-com

    Your web team · a few days

    Tested by Google LighthouseAvoid enormous network payloads, Chrome

    Report an issue with this check
  • Your site responds quickly to taps and clicksImportantPass

    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.

    Tested by Google LighthouseTotal Blocking Time (TBT), Google

    Report an issue with this check
  • Your pages stay still while they loadImportantPass

    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.

    Tested by Google LighthouseWeb Vitals, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseWhy HTTPS matters, Google

    Report an issue with this check
  • Return visits load fasterImportantPass

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

    Tested by Google LighthousePrevent unnecessary network requests with the HTTP Cache, Google

    Report an issue with this check
  • Your pages load without errorsImportantPass

    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.

    Tested by Google LighthouseBrowser errors were logged to the console, Chrome

    Report an issue with this check
  • 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.

    Tested by Google LighthouseRequests the geolocation permission on page load, Chrome

    Report an issue with this check

Fix it,

or see it rebuilt

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

An AI agent searched “luxury apartments huntsville al”, like 590 people a month.

This scan graded the site on its own. Grade it again and an AI agent shops for it too, with a search your site already ranks for, and shows where it got through and where it stopped.

See wellorymidcity.com rebuilt, without these issues

131st of 159 residence sites graded so far. See the board.

How we grade