D

Poor for AI agents

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 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·Performance

    Your site responds quickly to taps and clicks

    Total Blocking Time (840 ms)

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

    Your web team · a week or moreSee 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

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 · 6 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: <h6 class="el-CardBgImage__content__heading" style="opacity: 1; transform: translate(0px, 0px);">
    • Fix any of the following: Heading order invalid: <h4 class="el-CardIconInfo__heading">
    • Fix any of the following: Heading order invalid: <h4 class="el-CardInfo__heading">

    How to fix it

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

    Fix with AI

    My website https://charmeoneagle.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: <h6 class="el-CardBgImage__content__heading" style="opacity: 1; transform: translate(0px, 0px);"> - Fix any of the following: Heading order invalid: <h4 class="el-CardIconInfo__heading"> - Fix any of the following: Heading order invalid: <h4 class="el-CardInfo__heading"> 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/charmeoneagle-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 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://charmeoneagle.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/charmeoneagle-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://charmeoneagle.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/charmeoneagle-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://charmeoneagle.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/charmeoneagle-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://charmeoneagle.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/charmeoneagle-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
  • 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
  • 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
41

Act

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

25% of your grade · 3 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: <div class="mol-Hotspots__hotspot mol-Hotspots__hotspot--information" style="left: 55.647457627119%; top: 75.332284646357%;" data-hotspot-id="1" data-hotspot-type="information" aria-expanded="false">
    • Buttons must have discernible text: <button class="atom-Hamburger atom-Hamburger--dark">
    • Links must have discernible text: <a class="atom-ButtonIcon atom-ButtonIcon--large atom-ButtonIcon--dark atom-ButtonIc…" href="https://www.tiktok.com/@charme.on.eagle" target="_blank">

    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://charmeoneagle.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: <div class="mol-Hotspots__hotspot mol-Hotspots__hotspot--information" style="left: 55.647457627119%; top: 75.332284646357%;" data-hotspot-id="1" data-hotspot-type="information" aria-expanded="false"> - Buttons must have discernible text: <button class="atom-Hamburger atom-Hamburger--dark"> - Links must have discernible text: <a class="atom-ButtonIcon atom-ButtonIcon--large atom-ButtonIcon--dark atom-ButtonIc…" href="https://www.tiktok.com/@charme.on.eagle" target="_blank"> 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/charmeoneagle-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://charmeoneagle.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/charmeoneagle-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 404

    How to fix it

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

    Fix with AI

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

    Your web team · a few days

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

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

    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. [user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

    • Fix any of the following: Element has insufficient color contrast of 3.63 (foreground color: #ece0d0, background color: #cb4627, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1: <span class="atom-ButtonPrimary__text">
    • Fix any of the following: user-scalable on <meta> tag disables zooming on mobile devices: <meta name="viewport" content="width=device-width, height=device-height, initial-scale=1.0, user-scalable…">

    How to fix it

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

    Fix with AI

    My website https://charmeoneagle.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. [user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5. Details: - Fix any of the following: Element has insufficient color contrast of 3.63 (foreground color: #ece0d0, background color: #cb4627, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1: <span class="atom-ButtonPrimary__text"> 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/charmeoneagle-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
  • 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": <div class="mol-Hotspots__hotspot mol-Hotspots__hotspot--information" style="left: 55.647457627119%; top: 75.332284646357%;" data-hotspot-id="1" data-hotspot-type="information" 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://charmeoneagle.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": <div class="mol-Hotspots__hotspot mol-Hotspots__hotspot--information" style="left: 55.647457627119%; top: 75.332284646357%;" data-hotspot-id="1" data-hotspot-type="information" 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/charmeoneagle-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
  • 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.

    Tested by Google LighthouseRule label: Form elements must have labels, 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 measured

    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: Could not check Link headers: The operation was aborted, Could not fetch API Catalog: The operation was aborted, Could not fetch Agent Skills index: The operation was aborted, and Could not fetch A2A Agent Card: The operation was aborted.

    Tested by CloudflareRFC 8288, Web Linking, IETF

    Report an issue with this check
55

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 site responds quickly to taps and clicksImportantFail

    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 (840 ms)

    • Reduce JavaScript execution time (3.0 s), from Google CDN
    • Minimize main-thread work (4.6 s)
    • Forced reflow

    How to fix it

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

    Fix with AI

    My website https://charmeoneagle.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 (840 ms) Details: - Reduce JavaScript execution time (3.0 s), from Google CDN - Minimize main-thread work (4.6 s) - Forced reflow 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/charmeoneagle-com

    Your web team · a week or more

    Tested by Google LighthouseTotal Blocking Time (TBT), Google

    Report an issue with this check
  • Return visits load fasterImportantFail

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

    What we found: Use efficient cache lifetimes (Est savings of 2,501 KiB)

    • Use efficient cache lifetimes (Est savings of 2,501 KiB), from aframe.io
    • Use efficient cache lifetimes (Est savings of 2,501 KiB), from Facebook
    • Use efficient cache lifetimes (Est savings of 2,501 KiB), from Facebook

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://charmeoneagle.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 2,501 KiB) Details: - Use efficient cache lifetimes (Est savings of 2,501 KiB), from aframe.io - Use efficient cache lifetimes (Est savings of 2,501 KiB), from Facebook - Use efficient cache lifetimes (Est savings of 2,501 KiB), from Facebook The fix, for a developer: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag. Source: Prevent unnecessary network requests with the HTTP Cache, Google: https://web.dev/articles/http-cache Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/charmeoneagle-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 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 (8.3 s). First Contentful Paint (2.4 s). Speed Index (18.6 s). Lab test on a phone: too few real visitors to measure it.

    • LCP request discovery
    • LCP breakdown
    • Render-blocking requests (Est savings of 1,460 ms), from Adobe TypeKit

    How to fix it

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

    Fix with AI

    My website https://charmeoneagle.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 (8.3 s). First Contentful Paint (2.4 s). Speed Index (18.6 s). Lab test on a phone: too few real visitors to measure it. Details: - LCP request discovery - LCP breakdown - Render-blocking requests (Est savings of 1,460 ms), from Adobe TypeKit 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/charmeoneagle-com

    Your web team · a week or more

    Tested by Google LighthouseWeb Vitals, 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.158)

    • Layout shift culprits
    • Avoid large layout shifts (1 layout shift found): <div class="mol-ListingBgImageCardsSlider mol-ListingBgImageCardsSlider--disableBottom…" data-center-slides="false" data-number-of-slides="18">

    How to fix it

    Stop content from moving as images and fonts load.

    Fix with AI

    My website https://charmeoneagle.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.158) Details: - Layout shift culprits - Avoid large layout shifts (1 layout shift found): <div class="mol-ListingBgImageCardsSlider mol-ListingBgImageCardsSlider--disableBottom…" data-center-slides="false" data-number-of-slides="18"> 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/charmeoneagle-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 1,547 KiB). Image elements do not have explicit width and height.

    • Improve image delivery (Est savings of 1,547 KiB): <img class="atom-ResponsiveImage atom-ResponsiveImage--bgImage" alt="Facelab 2025 11 05 08 38 12" src="https://amplify-charme-on-eagle.imgix.net/Media/Brand-Ambassador/Facelab-2…" srcset="https://amplify-charme-on-eagle.imgix.net/Media/Brand-Ambassador/Facelab-2…" sizes="100vw">, from imgix
    • Image elements do not have explicit width and height: <img class="atom-ResponsiveImage" alt="Charme On Eagle" src="https://s3-us-west-2.amazonaws.com/amplify-charme-on-eagle/images/Graphics…">, from Amazon Web Services

    How to fix it

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

    Fix with AI

    My website https://charmeoneagle.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 1,547 KiB). Image elements do not have explicit width and height. Details: - Improve image delivery (Est savings of 1,547 KiB): <img class="atom-ResponsiveImage atom-ResponsiveImage--bgImage" alt="Facelab 2025 11 05 08 38 12" src="https://amplify-charme-on-eagle.imgix.net/Media/Brand-Ambassador/Facelab-2…" srcset="https://amplify-charme-on-eagle.imgix.net/Media/Brand-Ambassador/Facelab-2…" sizes="100vw">, from imgix - Image elements do not have explicit width and height: <img class="atom-ResponsiveImage" alt="Charme On Eagle" src="https://s3-us-west-2.amazonaws.com/amplify-charme-on-eagle/images/Graphics…">, from Amazon Web Services 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/charmeoneagle-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 8,120 KiB). Reduce unused JavaScript (Est savings of 1,311 KiB). Reduce unused CSS (Est savings of 70 KiB). Minify CSS (Est savings of 18 KiB). Legacy JavaScript (Est savings of 133 KiB).

    • Reduce unused JavaScript (Est savings of 1,311 KiB), from aframe.io

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://charmeoneagle.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 8,120 KiB). Reduce unused JavaScript (Est savings of 1,311 KiB). Reduce unused CSS (Est savings of 70 KiB). Minify CSS (Est savings of 18 KiB). Legacy JavaScript (Est savings of 133 KiB). Details: - Reduce unused JavaScript (Est savings of 1,311 KiB), from aframe.io 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/charmeoneagle-com

    Your web team · a few days

    Tested by Google LighthouseAvoid enormous network payloads, Chrome

    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. Missing source maps for large first-party JavaScript.

    • Refused to execute script from 'https://cdnjs.cloudflare.com/polyfill?features=fetch,Promise' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.

    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://charmeoneagle.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. Missing source maps for large first-party JavaScript. Details: - Refused to execute script from 'https://cdnjs.cloudflare.com/polyfill?features=fetch,Promise' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. 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/charmeoneagle-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 18 fixes add up to about seven weeks of your web team's time.

  • Send to your agency

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

    Send to your agency

  • Explore with your AI

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

    Read the Agent Grader report for charmeoneagle.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/charmeoneagle-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 charmeoneagle.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/charmeoneagle-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 charmeoneagle.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 “student apartments denton tx”, like 1,300 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 charmeoneagle.com rebuilt, without these issues

147th of 164 residence sites graded so far. See the board.

How we grade