C

Hard for AI agents to use

Speed: Fail (Google's lab run of this page)Core Web Vitals, Google

Start here.

These hold your letter down the most
  1. 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

  2. Fail·Act

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

    Google's Lighthouse finds your ARD catalog invalid, so agents cannot rely on it to find your MCP server.

    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

  3. Partial·Performance

    Your main content shows up quickly on phones

    Largest Contentful Paint (11.1 s). Speed Index (8.4 s). Lab test on a phone: too few real visitors to measure it.

    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

95

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 says when a page does not exist (404)ImportantFail

    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.

    What we found: An address that does not exist answers 200 with a normal page.

    • Status 200

    How to fix it

    Make a mistyped address show a page that says it was not found, with a 404 status behind it.

    Fix with AI

    My website https://www.thelextacoma.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 when a page does not exist (404) What the grader found: An address that does not exist answers 200 with a normal page. Details: - Status 200 The fix, for a developer: Return 404 (or 410 for a page that is gone) for unknown routes. A single-page app needs its server to answer unknown paths with the not-found page and a 404 status, since a redirect to the home page makes every address look real. Source: How Google Search handles HTTP status codes, Google: https://developers.google.com/crawling/docs/troubleshooting/http-status-codes; RFC 9110, section 15.5.5 404 Not Found, IETF: https://www.rfc-editor.org/rfc/rfc9110#section-15.5.5 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/thelextacoma-com

    Your web team · about an hour

    Tested by ClutchHow Google Search handles HTTP status codes, 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 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.

    Tested by Google LighthouseRobots.txt Introduction and Guide, 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
  • 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 · 8 of 11 goals pass

  • 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: ARD manifest is invalid

    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.thelextacoma.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: ARD manifest is invalid 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/thelextacoma-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.thelextacoma.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/thelextacoma-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.thelextacoma.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/thelextacoma-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
  • Headings give each page a clear outlineImportantPass

    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.

    Tested by Google LighthouseOptimizing your website for generative AI features on Google Search, 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
  • 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.

    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)ImportantPass

    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.

    Tested by Google Lighthousellms.txt audit, Chrome

    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
71

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

  • 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.thelextacoma.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/thelextacoma-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: Google's Lighthouse finds your ARD catalog invalid, so agents cannot rely on it to find your MCP server.

    • Lighthouse's ard-schema audit fails

    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.thelextacoma.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: Google's Lighthouse finds your ARD catalog invalid, so agents cannot rely on it to find your MCP server. Details: - Lighthouse's ard-schema audit fails 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/thelextacoma-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 class="instagram-media instagram-media-rendered" id="instagram-embed-0" src="https://www.instagram.com/thelextacoma/embed/?cr=1&amp;v=14&amp;wp=661&amp;rd=https%3A…" allowtransparency="true" allowfullscreen="true" frameborder="0" height="446" data-instgrm-payload-id="instagram-media-payload-0" scrolling="no" style="background: white; max-width: 540px; width: calc(100% - 2px);">

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

    Your web team · a few days

    Tested by Google LighthouseAccessibility for agents, Chrome

    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.53 (foreground color: #9ca3af, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1: <p class="font-body text-xs text-gray-400">

    How to fix it

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

    Fix with AI

    My website https://www.thelextacoma.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.53 (foreground color: #9ca3af, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1: <p class="font-body text-xs text-gray-400"> 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/thelextacoma-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
  • 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.

    Tested by Google LighthouseAccessibility for agents, Chrome

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

    Tested by Google LighthouseAccessibility for agents, Chrome

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

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

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

    Tested by Google LighthouseAccessible tap targets, Google

    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.

    • Link headers present but no agent-useful relation types found
    • API Catalog returned HTML instead of JSON
    • Agent Skills index returned HTML instead of JSON

    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.thelextacoma.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: - Link headers present but no agent-useful relation types found - API Catalog returned HTML instead of JSON - Agent Skills index returned HTML instead of JSON 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/thelextacoma-com

    Your web team · about a day

    Tested by CloudflareRFC 8288, Web Linking, IETF

    Report an issue with this check
66

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 · 3 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: Largest Contentful Paint (11.1 s). Speed Index (8.4 s). Lab test on a phone: too few real visitors to measure it.

    • Render-blocking requests (Est savings of 730 ms)
    • 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.thelextacoma.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your main content shows up quickly on phones What the grader found: Largest Contentful Paint (11.1 s). Speed Index (8.4 s). Lab test on a phone: too few real visitors to measure it. Details: - Render-blocking requests (Est savings of 730 ms) - 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/thelextacoma-com

    Your web team · a week or more

    Tested by Google LighthouseWeb Vitals, Google

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

    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.

    What we found: Total Blocking Time (480 ms)

    • Reduce JavaScript execution time (1.6 s)
    • Minimize main-thread work (3.1 s)
    • Avoid long main-thread tasks (11 long tasks found), from omni.cafe

    How to fix it

    Remove scripts the page does not need, since they keep it busy.

    Fix with AI

    My website https://www.thelextacoma.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 responds quickly to taps and clicks What the grader found: Total Blocking Time (480 ms) Details: - Reduce JavaScript execution time (1.6 s) - Minimize main-thread work (3.1 s) - Avoid long main-thread tasks (11 long tasks found), from omni.cafe The fix, for a developer: Split long tasks and defer scripts that are not needed to start. PageSpeed lists the costliest scripts. Source: Total Blocking Time (TBT), Google: https://web.dev/articles/tbt; Lighthouse performance scoring, Chrome: https://developer.chrome.com/docs/lighthouse/performance/performance-scoring 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/thelextacoma-com

    Your web team · a week or more

    Tested by Google LighthouseTotal Blocking Time (TBT), Google

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

    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.

    What we found: Cumulative Layout Shift (0.119)

    • Layout shift culprits
    • Avoid large layout shifts (15 layout shifts found): <button class="sob-reopen" aria-label="Show special offers" style="opacity: 0; pointer-events: none;">
    • Avoid non-composited animations (5 animated elements found): <div id="buttonContainer" class="chat-autoresponderWrapper fade-in ng-star-inserted" data-selenium-id="chat_ButtonContainer">

    How to fix it

    Stop content from moving as images and fonts load.

    Fix with AI

    My website https://www.thelextacoma.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 stay still while they load What the grader found: Cumulative Layout Shift (0.119) Details: - Layout shift culprits - Avoid large layout shifts (15 layout shifts found): <button class="sob-reopen" aria-label="Show special offers" style="opacity: 0; pointer-events: none;"> - Avoid non-composited animations (5 animated elements found): <div id="buttonContainer" class="chat-autoresponderWrapper fade-in ng-star-inserted" data-selenium-id="chat_ButtonContainer"> The fix, for a developer: Set width and height on images and embeds, reserve space for late content, and use font-display with a matching fallback font. Source: Web Vitals, Google: https://web.dev/articles/vitals; Cumulative Layout Shift (CLS), Google: https://web.dev/articles/cls 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/thelextacoma-com

    Your web team · about a day

    Tested by Google LighthouseWeb Vitals, Google

    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 162 KiB). Image elements do not have explicit width and height.

    • Improve image delivery (Est savings of 162 KiB): <img src="https://media.multihub.io/cdn-cgi/image/format=auto,w=960/property/6767906…" srcset="https://media.multihub.io/cdn-cgi/image/format=auto,w=160/property/6767906…" sizes="100vw" alt="Property hero image" loading="eager" fetchpriority="high" class="w-full h-full object-cover" style="animation: 30s ease-in-out 0s infinite alternate none running heroKenBurns…;">, from multihub.io
    • Image elements do not have explicit width and height: <img src="/assets/repli_white-BirIi_dg.svg" alt="Repli Logo" height="36" class="h-9 w-auto">

    How to fix it

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

    Fix with AI

    My website https://www.thelextacoma.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 162 KiB). Image elements do not have explicit width and height. Details: - Improve image delivery (Est savings of 162 KiB): <img src="https://media.multihub.io/cdn-cgi/image/format=auto,w=960/property/6767906…" srcset="https://media.multihub.io/cdn-cgi/image/format=auto,w=160/property/6767906…" sizes="100vw" alt="Property hero image" loading="eager" fetchpriority="high" class="w-full h-full object-cover" style="animation: 30s ease-in-out 0s infinite alternate none running heroKenBurns…;">, from multihub.io - Image elements do not have explicit width and height: <img src="/assets/repli_white-BirIi_dg.svg" alt="Repli Logo" height="36" class="h-9 w-auto"> 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/thelextacoma-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: Avoid enormous network payloads (Total size was 5,075 KiB). Reduce unused JavaScript (Est savings of 722 KiB). Reduce unused CSS (Est savings of 47 KiB). Minify JavaScript (Est savings of 24 KiB). Duplicated JavaScript (Est savings of 6 KiB).

    • Avoid enormous network payloads (Total size was 5,075 KiB), from omni.cafe
    • Reduce unused JavaScript (Est savings of 722 KiB), from omni.cafe
    • Reduce unused CSS (Est savings of 47 KiB), from omni.cafe

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://www.thelextacoma.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages are light to download What the grader found: Avoid enormous network payloads (Total size was 5,075 KiB). Reduce unused JavaScript (Est savings of 722 KiB). Reduce unused CSS (Est savings of 47 KiB). Minify JavaScript (Est savings of 24 KiB). Duplicated JavaScript (Est savings of 6 KiB). Details: - Avoid enormous network payloads (Total size was 5,075 KiB), from omni.cafe - Reduce unused JavaScript (Est savings of 722 KiB), from omni.cafe - Reduce unused CSS (Est savings of 47 KiB), from omni.cafe 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/thelextacoma-com

    Your web team · a few days

    Tested by Google LighthouseAvoid enormous network payloads, Chrome

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

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

    • Use efficient cache lifetimes (Est savings of 430 KiB), from omni.cafe
    • Use efficient cache lifetimes (Est savings of 430 KiB), from omni.cafe
    • Use efficient cache lifetimes (Est savings of 430 KiB), from repli360.com

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://www.thelextacoma.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Return visits load faster What the grader found: Use efficient cache lifetimes (Est savings of 430 KiB) Details: - Use efficient cache lifetimes (Est savings of 430 KiB), from omni.cafe - Use efficient cache lifetimes (Est savings of 430 KiB), from omni.cafe - Use efficient cache lifetimes (Est savings of 430 KiB), from repli360.com 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/thelextacoma-com

    Your web team · about an hour

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

    Report an issue with this check
  • 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. Issues were logged in the Issues panel in Chrome Devtools. Uses third-party cookies (1 cookie found).

    • Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at Ea (/assets/index-BBz6aQeN.js:6:4905) at Jl (/assets/index-BBz6aQeN.js:8:45372) at Ll (/assets/index-BBz6aQeN.js:8:39579) at Fl (/assets/index-BBz6aQeN.js:8:39507) at Pl (/assets/index-BBz6aQeN.js:8:39361) at xl (/assets/index-BBz6aQeN.js:8:34458) at x (/assets/index-BBz6aQeN.js:1:9330) at MessagePort.O (/assets/index-BBz6aQeN.js:1:9689)
    • Uses third-party cookies (1 cookie found), from omni.cafe

    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.thelextacoma.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. Issues were logged in the Issues panel in Chrome Devtools. Uses third-party cookies (1 cookie found). Details: - Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at Ea (/assets/index-BBz6aQeN.js:6:4905) at Jl (/assets/index-BBz6aQeN.js:8:45372) at Ll (/assets/index-BBz6aQeN.js:8:39579) at Fl (/assets/index-BBz6aQeN.js:8:39507) at Pl (/assets/index-BBz6aQeN.js:8:39361) at xl (/assets/index-BBz6aQeN.js:8:34458) at x (/assets/index-BBz6aQeN.js:1:9330) at MessagePort.O (/assets/index-BBz6aQeN.js:1:9689) - Uses third-party cookies (1 cookie found), from omni.cafe 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/thelextacoma-com

    Your web team · a few days

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

    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
  • Your server answers quicklyImportantPass

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

    Tested by Google LighthouseReduce server response times (TTFB), 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 16 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 thelextacoma.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/thelextacoma-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 thelextacoma.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/thelextacoma-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 thelextacoma.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 “downtown tacoma apartments”, like 590 people a month.

The same rules every run: four searches, up to three sites, six pages, made-up details, and it never sends anything.

  • FoundReached

    Your site was result 3 of the first search, and the agent opened it.

  • ReadNot reached

    The agent's answer cites no fact from your site's own pages.

  • ActedNot reached

    Reached when your site gives the agent a way to act.

  1. Finding the search your site already ranks for on Google.

  2. Reading your site to plan the first search.3s

  3. Reviewing the search results.8s

  6. Judging how far it got.

What it told the shopper1 of 10 sources is your site

Here are three downtown Tacoma apartment communities whose own websites I opened.

1. The Lex (415 St Helens Ave, 98402) Source: https://www.thelextacoma.com/

  • What the site says: It describes studio, one- and two-bedroom apartments in Downtown Tacoma, with sweeping views of Commencement Bay from almost every home and a rooftop deck.
  • Why I picked it: It is the best fit if you want a view and a walkable location. The site says the building sits close to the Sounder Transit Station and that it has a Walk Score of 96.
  • Next step: You can use the site's "Schedule a Tour" or "Apply Now" links, or call (844) 243-5680.
  • Not on the site: The page I opened did not list rents or floor-plan details. Its floor-plan section showed only a placeholder message. A directory listing I saw separately gave a price range, but I did not confirm it on the community's site.

2. Moraine (1402 Tacoma Ave S, 98402) Source: https://www.moraine-tac.com/

  • What the site says: It offers brand-new micro, studio, one-, two- and three-bedroom apartments, ranging from 292 to 900 square feet. It advertises views of Mt. Rainier and Puget Sound from its roof decks and some homes. It lists a garage, fitness center, clubhouse and pet-friendly policy.
  • Why I picked it: It is the best choice if you want a newer building with the widest range of layouts, including three-bedroom units.
  • Next step: Use the site's "Schedule a Tour" page or call +1 253-322-5682. The site lists office hours of 9 AM to 6 PM on weekdays and Saturday, and says it is closed on Sundays.
  • Not on the site: The site advertises "Get Up to 12 Weeks Free" but says restrictions apply and tells you to call for details. I did not find the exact rent amounts on the page I opened.

3. Analog Tacoma (411 S 15th Street, 98402) Source: https://www.analog-tacoma.com/

  • What the site says: It lists micro, studio, one-, two- and three-bedroom apartments. It has a rooftop terrace, a community lounge, a gym, a co-working space and a laundry facility. It is pet-friendly and says it is near the University of Washington Tacoma campus and the convention center.
  • Why I picked it: It is the best fit if you work from home, have a pet or want shared amenities.
  • Next step: Use the "Apply Now" or "Schedule a Tour" links, or call +1 253-243-3179. Its office is open weekdays from 9 AM to 5:30 PM and closed on weekends.
  • Not on the site: The site did not show prices or specific availability. Its contact form returned error messages when I reviewed it, so calling is the more reliable option.

All three communities are in or near Downtown Tacoma, so the choice depends on what matters most to you: views and transit (The Lex), the widest range of layouts (Moraine), or pet-friendly and shared amenities (Analog Tacoma). Before you decide, confirm current rents and move-in specials directly with each property, since I could not verify them on their sites.

These sites are competing with you

SiteLetterFindReadActPerformance
thelextacoma.comBuilt in ClutchAFindPassesReadPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
thelextacoma.comCFind9582Act71Performance66
moraine-tac.comOpened by the AI agent
analog-tacoma.comOpened by the AI agent

See thelextacoma.com rebuilt, without these issues

41st of 162 residence sites graded so far. See the board.

How we grade