A

Ready for AI agents

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

Start here.

These hold your letter down the most
  1. Partial·Performance

    Your server answers quickly

    The server took 937 ms to start answering the home page. Document request latency.

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

    Your web team · about a daySee the check

  2. Partial·Performance

    Your main content shows up quickly on phones

    The page takes 2.3 s to show anything. Lab test on a phone.

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

    Your web team · a week or moreSee the check

  3. Partial·Performance

    Images are sent at the size they are shown

    Improve image delivery. An image is stretched or squashed.

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

    Your web team · about a daySee the check

100

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

98

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

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

    • A heading of level 5 follows one of level 2: <h5 class="type-fine-head text-foreground" id="hn-agencies-r1-h">

    How to fix it

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

    Fix with AI

    My website https://clutch.io/ 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. Details: - A heading of level 5 follows one of level 2: <h5 class="type-fine-head text-foreground" id="hn-agencies-r1-h"> 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/clutch-io/2026-11-20

    Your web team · about an hour
  • 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 site has a short guide for AI agents (llms.txt)CriticalPass

    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.

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

    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.

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

    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.

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

  • Each page marks its header, main content and footer (landmarks)ImportantPass

    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.

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

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

100

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

  • 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 see your site's buttons and fields (accessibility tree)CriticalPass

    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.

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

    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.

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

    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.

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

  • Hidden labels on your buttons and fields are accurate (ARIA)ImportantPass

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

  • Your text stands out clearly from its backgroundImportantPass

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

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

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

  • AI agents can move around your pages without a mouseImportantPass

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

90

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 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 page takes 2.3 s to show anything. Lab test on a phone.

    • In the longest chain, 1047 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://clutch.io/ 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 page takes 2.3 s to show anything. Lab test on a phone. Details: - In the longest chain, 1047 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/clutch-io/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.

    • Could be 61 KiB smaller: more compression, sized for the box it shows in: <img src="/media/6cba12c0714afffc61c3f32d03c94200-768x432.webp" alt="Halstead Yards at golden hour: the wood-clad building on its corner" width="768" height="432" srcset="/media/6cba12c0714afffc61c3f…
    • Shown at 2356 × 1620 (1.45), its file is 750 × 515 (1.46): <img src="/media/4848cf51dae3dcb4ea13220c947c00f6-2356x1620.webp" alt="Halstead Yards' home page under its ask" width="2356" height="1620" srcset="/media/4848cf51dae3dcb4ea13220c947c00f6-2356x1620-64…

    How to fix it

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

    Fix with AI

    My website https://clutch.io/ 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. Details: - Could be 61 KiB smaller: more compression, sized for the box it shows in: <img src="/media/6cba12c0714afffc61c3f32d03c94200-768x432.webp" alt="Halstead Yards at golden hour: the wood-clad building on its corner" width="768" height="432" srcset="/media/6cba12c0714afffc61c3f… - Shown at 2356 × 1620 (1.45), its file is 750 × 515 (1.46): <img src="/media/4848cf51dae3dcb4ea13220c947c00f6-2356x1620.webp" alt="Halstead Yards' home page under its ask" width="2356" height="1620" srcset="/media/4848cf51dae3dcb4ea13220c947c00f6-2356x1620-64… 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/clutch-io/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: Minify CSS (5 KiB to save).

    • 5 KiB of 26 KiB would go: <style>

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://clutch.io/ 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: Minify CSS (5 KiB to save). Details: - 5 KiB of 26 KiB would go: <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/clutch-io/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: The server took 937 ms to start answering the home page. Document request latency.

    • First byte after 937 ms
    • Server responded slowly (observed 937 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://clutch.io/ 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: The server took 937 ms to start answering the home page. Document request latency. Details: - First byte after 937 ms - Server responded slowly (observed 937 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/clutch-io/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.

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

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

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

Find me a company that builds a website my customers and their AI assistants can use to ask questions and book things, and that keeps the site up to date.

Find

Did a search lead the agent to you?

  1. Searched“agency builds websites AI assistant chatbot booking managed updates”

    • chatbotkit.com
    • yourwebsite.agency
    • closebot.com
  2. Searched“website for AI agents booking MCP small business web design”

    • ecomerfymcp.com
    • web-mcp.net
    • mountainhomemarketing.com
  3. Openedyourwebsite.agency

  4. Openedmountainhomemarketing.com/agent-ready-websites

  5. Openedecomerfymcp.com/mcp-website-development

Find failed

Search led the agent to yourwebsite.agency, mountainhomemarketing.com and ecomerfymcp.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 toclutch.io

    It could read the page right away: 1,004 words

Read passed

Your site answered what the shopper asked.

The agent's answer

Clutch (clutch.io) fits your request well on paper. I read only its homepage, so I can't yet confirm pricing, customer results, or how the product works in practice.

Why it fits

  • Customers asking questions: The site describes a "concierge" that answers each visitor. It says Clutch builds a site people and AI agents can find, read and act on, and an agent runs it with you.
  • AI assistants booking things: The homepage gives an example where ChatGPT finds halsteadyards.com, reads its WebMCP tools, checks tour times and books one. This is a demo scenario, not a verified customer result.
  • Keeping the site current: The owner can request changes in plain language. In the example, the owner asks to add a holiday catering item, and the site reports Added a Holiday trays card to Catering. Changes go live only after approval, and the example shows "Live on halsteadyards.com." The site also describes a weekly report sent by text.

What the site says

  • It targets multifamily communities, restaurants, single locations, and property portfolios.
  • It lists a "Free to try" offer, and its sign-up link goes to a waiting list page.
  • It names some customers: Camden Property Trust, Shipley Do-Nuts, Fajita Pete's, PropMatic, and Saivory.

Next step Go to https://clutch.io/waiting-list (the "Sign up" link) and check whether the free trial fits your business type. Before committing, check the pricing page (linked from the site, not yet read) and ask whether your booking system and ask-anything features work with your tools.

Pages I relied on: https://clutch.io/ (homepage only).

Act

Could the agent do the shopper's next step?

The shopper's next request: “Build me a site like that and set it up so AI assistants can book for my customers.”

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

    Your site offers AI agents a tool that does it

Act passed

An agent can do it for the shopper, right on your site.

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

  1. Find

    Nothing on your site held search back. Other sites ranked higher for this request.

  2. Read

    Passed. A few checks could still be stronger.

  3. Act

    Nothing to fix.

These sites are competing with you

SiteLetterFindReadActPerformance
clutch.ioYour site · built in ClutchAFind100Read98Act100Performance90
yourwebsite.agencyOpened by the AI agent
mountainhomemarketing.comOpened by the AI agent
ecomerfymcp.comOpened by the AI agent

See clutch.io rebuilt, without these issues