F

Not ready for AI agents

Capped at F: your site turns AI agents away before they can read it. Your checks earned 68.

See the goal behind it

Start here.

These hold your letter down the most
  1. Unknown·Read

    AI agents can read your text without running scripts

    Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    What to do Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Your web team · a few daysSee the check

  2. Unknown·Read

    Your site tells AI agents what your business is (structured data)

    Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    What to do Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Your web team · about a daySee the check

  3. Unknown·Find

    Your site says when a page does not exist (404)

    Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    What to do Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Your web team · about an hourSee the check

73

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

  • Your site's security doesn't turn AI agents away (firewall)CriticalFail

    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.

    What we found: Your site answered Cloudflare's scan with 403 Forbidden instead of the page.

    • Answered 403 Forbidden

    How to fix it

    Let automated visits to your public pages through the firewall.

    Fix with AI

    My website https://livebeacon85.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's security doesn't turn AI agents away (firewall) What the grader found: Your site answered Cloudflare's scan with 403 Forbidden instead of the page. Details: - Answered 403 Forbidden The fix, for a developer: Find the firewall or bot-protection rule that answers automated requests with a challenge or a 403, and exempt requests for public pages. Run Cloudflare's agent readiness scan again to confirm it gets the page. Source: Web fetch tool, Anthropic: https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-fetch-tool; Is Your Site Agent-Ready?, Cloudflare: https://isitagentready.com/ 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/livebeacon85-com/2026-11-11

    Your web team · about an hour

    Tested by CloudflareWeb fetch tool, Anthropic

    Report an issue with this check
  • Your site says when a page does not exist (404)ImportantUnknown

    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: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    • our reader was turned away

    How to fix it

    Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Fix with AI

    My website https://livebeacon85.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: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does. Details: - our reader was turned away The fix, for a developer: Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader. 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/livebeacon85-com/2026-11-11

    Your web team · about an hour

    Tested by ClutchHow Google Search handles HTTP status codes, Google

    Report an issue with this check
  • Your site lets AI agents in (robots.txt)CriticalNot measured

    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.

    What we found: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareOverview of OpenAI crawlers, OpenAI

    Report an issue with this check
  • Your site lists its pages for search engines (XML sitemap)ImportantNot measured

    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.

    What we found: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareBuild and submit a sitemap, Google

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

  • AI agents can read your text without running scriptsCriticalUnknown

    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.

    What we found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    • our reader was turned away

    How to fix it

    Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Fix with AI

    My website https://livebeacon85.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 read your text without running scripts What the grader found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does. Details: - our reader was turned away The fix, for a developer: Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader. Source: Understand JavaScript SEO basics, Google Search Central: https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics; HTML Standard, Parsing HTML documents, WHATWG: https://html.spec.whatwg.org/multipage/parsing.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/livebeacon85-com/2026-11-11

    Your web team · a few days

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

    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.

    What we found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    • our reader was turned away

    How to fix it

    Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Fix with AI

    My website https://livebeacon85.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 what your business is (structured data) What the grader found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does. Details: - our reader was turned away The fix, for a developer: Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader. Source: Intro to structured data, Google: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data; JSON-LD 1.1, W3C: https://www.w3.org/TR/json-ld11/ 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/livebeacon85-com/2026-11-11

    Your web team · about a day

    Tested by ClutchIntro to structured data, 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: llms.txt does not follow recommendations

    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://livebeacon85.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: llms.txt does not follow recommendations 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/livebeacon85-com/2026-11-11

    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://livebeacon85.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/livebeacon85-com/2026-11-11

    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)ImportantNot measured

    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: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareMarkdown for Agents, Cloudflare

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

    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: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareContent Signals, Content Signals

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

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.

Not measured.

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

    What we found: Not measured: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    • PageSpeed's "WebMCP tools registered" audit lists no tool

    How to fix it

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

    Fix with AI

    My website https://livebeacon85.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: Not measured: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this. Details: - PageSpeed's "WebMCP tools registered" audit lists no tool 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/livebeacon85-com/2026-11-11

    Your web team · about a day

    Tested by Google LighthouseCloudflareWebMCP for developers, Chrome

    Report an issue with this check
  • Buttons and links are big enough for an agent to clickImportantPartial

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

    What we found: Touch targets do not have sufficient size or spacing.

    • Fix any of the following: Target has insufficient size (7px by 7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 10px instead of at least 24px.: <a href="#" class="homepage__gallery-active">

    How to fix it

    Make small buttons and tightly packed links bigger on phones.

    Fix with AI

    My website https://livebeacon85.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Buttons and links are big enough for an agent to click What the grader found: Touch targets do not have sufficient size or spacing. Details: - Fix any of the following: Target has insufficient size (7px by 7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 10px instead of at least 24px.: <a href="#" class="homepage__gallery-active"> The fix, for a developer: Make each target at least 24 by 24 CSS pixels, or leave enough space around smaller ones, and aim for around 48 pixels. Set width=device-width in the viewport tag so taps answer at once. Source: Accessible tap targets, Google: https://web.dev/articles/accessible-tap-targets; Understanding Success Criterion 2.5.8: Target Size (Minimum), W3C: https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/livebeacon85-com/2026-11-11

    Your web team · about an hour

    Tested by Google LighthouseAccessible tap targets, Google

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

    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: We could not read /.well-known/ard.json. The letter waits until we can measure this.

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

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

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

    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: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this, Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this, Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this, and Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareRFC 8288, Web Linking, IETF

    Report an issue with this check
77

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

  • 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 30 KiB)

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://livebeacon85.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 30 KiB) 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/livebeacon85-com/2026-11-11

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

    • Render-blocking requests (Est savings of 710 ms), from Google Fonts
    • 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://livebeacon85.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 is 3.3 s for real visitors of this page, last 28 days, which Google rates needs improvement. First Contentful Paint is 1.9 s for real visitors of this page, last 28 days, which Google rates needs improvement. Speed Index (3.7 s). Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone. Details: - Render-blocking requests (Est savings of 710 ms), from Google Fonts - 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/livebeacon85-com/2026-11-11

    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 is 0.25 for real visitors of this page, last 28 days, which Google rates needs improvement.

    How to fix it

    Stop content from moving as images and fonts load.

    Fix with AI

    My website https://livebeacon85.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 is 0.25 for real visitors of this page, last 28 days, which Google rates needs improvement. 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/livebeacon85-com/2026-11-11

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

    • Improve image delivery (Est savings of 99 KiB): <img data-jdl-action="home-hero-impression" data-jdl-data="{&quot;index&quot;:0,&quot;count&quot;:3,&quot;media_type&quot;:&quot;image&quot;,&quot;title&quot;:&quot;Welcome Home&quot;,&quot;src&quot;:&quot;ht…" data-jdl-view="" data-el="image[]" class="homepage__rotator-image" fetchpriority="high" src="/assets/images/cache/0GFC2y0Cfgqt3mwjEHcWONGOvETWb…" alt="A kitchen with a bar and stools at Beacon 85 Apartments, one of the apartm…" draggable="false" style="opacity: 1;">
    • Image elements do not have explicit width and height: <img class="themer-logo themer-logo--main themer-logo--full" fetchpriority="high" src="/themer/assets/logo/logo_main_1722528199.svg" alt="Beacon 85 Apartments">

    How to fix it

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

    Fix with AI

    My website https://livebeacon85.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 99 KiB). Image elements do not have explicit width and height. Details: - Improve image delivery (Est savings of 99 KiB): <img data-jdl-action="home-hero-impression" data-jdl-data="{&quot;index&quot;:0,&quot;count&quot;:3,&quot;media_type&quot;:&quot;image&quot;,&quot;title&quot;:&quot;Welcome Home&quot;,&quot;src&quot;:&quot;ht…" data-jdl-view="" data-el="image[]" class="homepage__rotator-image" fetchpriority="high" src="/assets/images/cache/0GFC2y0Cfgqt3mwjEHcWONGOvETWb…" alt="A kitchen with a bar and stools at Beacon 85 Apartments, one of the apartm…" draggable="false" style="opacity: 1;"> 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/livebeacon85-com/2026-11-11

    Your web team · about a day

    Tested by Google LighthouseProperly size images, Chrome

    Report an issue with this check
  • Your pages are light to downloadImportantPartial

    Heavy pages take longer to load and cost visitors on mobile data real money. Chrome says large downloads are closely tied to long load times.

    What we found: Reduce unused CSS (Est savings of 46 KiB).

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://livebeacon85.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages are light to download What the grader found: Reduce unused CSS (Est savings of 46 KiB). 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/livebeacon85-com/2026-11-11

    Your web team · a few days

    Tested by Google LighthouseAvoid enormous network payloads, Chrome

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

    A page that freezes after a tap feels broken, so visitors tap again or leave. Google rates a reaction under 200 milliseconds as good and counts it among its Core Web Vitals.

    Tested by Google LighthouseTotal Blocking Time (TBT), Google

    Report an issue with this check
  • Your 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 pages load without errorsImportantPass

    An error in the browser often means part of your page is broken, such as a form that will not send. Chrome says each one is a problem to resolve.

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

    Report an issue with this check
  • Your site does not ask visitors for permissions as they arriveImportantPass

    People distrust or are confused by a page that asks for their location the moment it opens. A field that blocks pasting makes a form harder to fill in.

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

    Report an issue with this check

Fix it,

or see it rebuilt

These 14 fixes add up to about four 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 livebeacon85.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/livebeacon85-com/2026-11-11 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 livebeacon85.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/livebeacon85-com/2026-11-11 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 livebeacon85.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 “apartments lakewood co”, like 2,400 people a month.

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

  • FoundNot reached

    Reached when the agent opens your site.

  • ReadNot reached

    Reached when the agent answers the shopper from your site's own facts.

  • ActedNot reached

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

See livebeacon85.com rebuilt, without these issues

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

Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

How we grade