D

Poor for AI agents

Capped at D: your pages load slowly on phones (Performance 54). Your checks earned 77.

See the goal behind it

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

Start here.

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

    The page responds as soon as it appears

    Total Blocking Time (1,290 ms)

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

    Your web team · a week or moreSee the check

  2. Partial·Performance

    The main content shows up quickly

    Largest Contentful Paint (4.2 s), First Contentful Paint (2.4 s), and Speed Index (8.9 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

  3. Partial·Performance

    The page does not jump around while it loads

    Cumulative Layout Shift (0.188)

    What to do Stop content from moving as images and fonts load.

    Your web team · about a daySee the check

Fix it,

or see it rebuilt

These 15 fixes add up to about five 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 this report on our website: clutch.io/grade/liveatfoxridge-com. Tell me how to fix each issue and the level of effort each fix takes.

  • See your site rebuilt

    Clutch rebuilds liveatfoxridge.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
95

Find

Can AI agents and search engines reach and list your pages?

25% of your grade · 9 of 10 goals pass

Read

25% of your grade · 8 of 11 goals pass

  • Your AI tools are listed in an AI catalogImportantTested by Google LighthouseFail

    ARD manifest is invalid The Agentic Resource Discovery (ARD) draft is a format that helps assistants discover what a site offers, such as tools and agents. Lighthouse audits the catalog, and the grade counts a standard that is likely to be adopted.

    • ARD manifest is invalid: https://liveatfoxridge.com/

    What to do Publish an ARD catalog once your site has an MCP server or agent to list.

    For your web team: Serve a JSON file at /.well-known/ard.json with an entries list that follows the ARD schema: each entry carries 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. Name the catalog from every page with <link rel="ard" href="/.well-known/ard.json">. Lighthouse reads that path and warns about a catalog it finds only at the older /.well-known/ai-catalog.json.

    Your web team · about a day · Important

    Lighthouse agentic browsing scoring, ChromeReport an issue with this check

  • Your pages answer in Markdown when an agent asksImportantTested by CloudflareFail

    Site does not support Markdown for Agents. Cloudflare calls Markdown the common language of agents: its explicit structure gives better results and wastes fewer tokens, and an agent asks for it with an Accept header.

    • Site does not support Markdown for Agents: https://liveatfoxridge.com/

    What to do Serve each page as Markdown to agents that ask for it.

    For your web team: 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.

    Your web team · about a day · Important

    Markdown for Agents, CloudflareReport an issue with this check

  • Your site says how AI may use its contentImportantTested by CloudflareFail

    No Content Signals found in robots.txt. Content Signals follow AI Preferences, a proposal at the IETF for a way for a publisher to say how automated systems may use its content.

    • No Content Signals found in robots.txt: https://liveatfoxridge.com/

    What to do 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.

    For your web team: 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.

    Your web team · about an hour · Important

    Content Signals, Content SignalsReport an issue with this check

  • Your key facts are in the page itselfCriticalTested by ClutchPass

    Your home page holds 387 words before any script runs. Claude's web fetch tool does not support pages that fill in their text with JavaScript, and Google reads such a page only after its first HTML, once it reaches the rendering queue. A page whose first response is empty waits or looks empty.

    Understand JavaScript SEO basics, Google Search CentralReport an issue with this check

  • Your business is described in structured dataImportantTested by ClutchPass

    The home page's structured data names ApartmentComplex, LocalBusiness, QuantitativeValue, PostalAddress, GeoCoordinates, OpeningHoursSpecification, AggregateRating, Review, Person, Rating, LocationFeatureSpecification, and ImageObject. Structured data spares an assistant from guessing what a page means. Google says it gives explicit clues about a page; Bing says it may support clearer grounding and promises nothing.

    Intro to structured data, GoogleReport an issue with this check

  • Headings give each page an outlineImportantTested by Google LighthousePass

    Heading elements appear in a sequentially-descending order Headings give a page a clear structure.

    Optimizing your website for generative AI features on Google Search, GoogleReport an issue with this check

  • Images describe themselvesImportantTested by Google LighthousePass

    All 2 audits in this goal pass. Alt text is a short written description of an image. Google calls it the most important attribute for adding metadata about an image, and it also uses computer vision on the picture.

    Image SEO Best Practices, GoogleReport an issue with this check

  • Lists and tables are built as lists and tablesImportantTested by Google LighthousePass

    All 4 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires the structure a page shows on screen to be in its markup as well, and the axe rules check lists and tables for it.

    Rule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axeReport an issue with this check

  • A short guide to your site for AI assistantsImportantTested by Google LighthousePass

    llms.txt follows recommendations llmstxt.org proposes the file so assistants find what they need and follow its links. Lighthouse audits it as an emerging convention, and the grade counts a standard that is likely to be adopted.

    llms.txt audit, ChromeReport an issue with this check

  • Every page has its own summary for search resultsImportantTested by Google LighthousePass

    Document has a meta description Google can show a page's meta description as its snippet and asks for a different one on every page. It is less likely to show a list of keywords, so a specific summary has the best chance of being used.

    How to Write Meta Descriptions, GoogleReport an issue with this check

  • Pages say which language they are inImportantTested by Google LighthousePass

    All 3 audits in this goal pass. WCAG requires the language of each page to be set in its code, so software reads it with the right rules and voice.

    Rule html-has-lang: <html> element must have a lang attribute, Deque axeReport an issue with this check

75

Act

Can they take the next step for a customer?

25% of your grade · 6 of 8 goals pass

  • Your site offers tools to AI assistantsMust haveImportantTested by Google LighthouseTested by CloudflareFail

    Your home page offers no tools to AI assistants and No WebMCP tools detected on page load. WebMCP lets an assistant book or reserve through a site's own code instead of guessing its way around the screen.

    While it fails, your letter stays at B or lower.

    • PageSpeed's "WebMCP tools registered" audit lists no tool: https://liveatfoxridge.com/
    • No WebMCP tools detected on page load: https://liveatfoxridge.com/

    What to do Expose the main action on your site, such as booking or contacting you, as a WebMCP tool.

    For your web team: Call document.modelContext.registerTool({ name, description, inputSchema, execute }) as the home page loads, or add toolname and tooldescription attributes to the form. A name is 1 to 128 letters, digits, _, - or .

    Your web team · about a day · Important

    WebMCP for developers, ChromeReport an issue with this check

  • Agents can discover your MCP serverMust haveImportantTested by ClutchFail

    Lighthouse finds your ARD catalog invalid, so an agent cannot rely on it to discover an MCP server. ARD is how an agent finds what a site offers from its domain alone, and the MCP project accepted server cards so that a client can discover a server before it connects.

    While it fails, your letter stays at B or lower.

    • Lighthouse's ard-schema audit fails: https://www.liveatfoxridge.com/.well-known/ard.json

    What to do Run an MCP server for your main actions and list it in the site's ARD catalog.

    For your web team: 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.

    Your web team · a few days · Important

    SEP-2127: MCP Server Cards, Model Context ProtocolReport an issue with this check

  • Assistants can read your page's controlsCriticalTested by Google LighthousePass

    Accessibility tree is well-formed (All audits passed) Agents review the accessibility tree to find what they can click or fill in, and missing labels can block them.

    Accessibility for agents, ChromeReport an issue with this check

  • Extra labels on controls are used correctlyImportantTested by Google LighthousePass

    All 10 audits in this goal pass. Wrong ARIA tells an assistant a control is something it is not. WAI-ARIA defines the roles and attributes that are valid, and the axe rules check them.

    Rule aria-roles: ARIA roles used must conform to valid values, Deque axeReport an issue with this check

  • Visitors can move around the pageImportantTested by Google LighthousePass

    All 3 audits in this goal pass. WCAG, the web accessibility standard most laws point to, requires every function of a page to work from a keyboard.

    Accessibility for agents, ChromeReport an issue with this check

  • Text is readableImportantTested by Google LighthousePass

    All 2 audits in this goal pass. WCAG requires text to contrast with its background by at least 4.5 to 1, and the axe rule color-contrast checks for it.

    Rule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axeReport an issue with this check

  • Buttons and links are big enough to tapImportantTested by Google LighthousePass

    All 2 audits in this goal pass. web.dev recommends tap targets of around 48 pixels, and WCAG sets a minimum of 24 by 24 pixels.

    Accessible tap targets, GoogleReport an issue with this check

  • Your site tells agents what else it offersImportantTested by CloudflareNot yet

    No Link headers found on target page, API Catalog returned HTML instead of JSON, Agent Skills index returned HTML instead of JSON, and A2A Agent Card returned HTML instead of JSON. Each is a published way for a site to tell an agent what it can call or learn there. Few sites that sell to the public need them yet, so they earn points and cost none.

    • No Link headers found on target page: https://liveatfoxridge.com/
    • API Catalog returned HTML instead of JSON: https://liveatfoxridge.com/
    • Agent Skills index returned HTML instead of JSON: https://liveatfoxridge.com/

    What to do Ask whoever runs your site which of these your business has a use for, such as an API catalog if you publish an API.

    For your web team: 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.

    Your web team · about a day · Important

    RFC 8288, Web Linking, IETFReport an issue with this check

54

Performance

Is it fast for the person who clicks through?

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

  • The page responds as soon as it appearsImportantTested by Google LighthouseFail

    Total Blocking Time (1,290 ms) INP is the wait between a tap and the page responding, and under 200 milliseconds is good. Total Blocking Time, the lab test's stand-in, has the same bar.

    • Total Blocking Time (1,290 ms): https://liveatfoxridge.com/
    • Reduce JavaScript execution time (4.7 s), from audioeye-services.com: https://wsv3cdn.audioeye-services.com/static-scripts/m/audioeye-scanner-esm/v11.2.50/audioeye-scanner-esm.js
    • Minimize main-thread work (6.8 s): https://liveatfoxridge.com/

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

    For your web team: Split long tasks and defer scripts that are not needed to start. PageSpeed lists the costliest scripts.

    Your web team · a week or more · Important

    Total Blocking Time (TBT), GoogleReport an issue with this check

  • The main content shows up quicklyImportantTested by Google LighthousePartial

    Largest Contentful Paint (4.2 s), First Contentful Paint (2.4 s), and Speed Index (8.9 s). Lab test on a phone: too few real visitors to measure it. LCP is how long the main picture or text takes to appear, and visitors leave slow pages. web.dev says 2.5 seconds or less is good, one of Google's three Core Web Vitals.

    • Largest Contentful Paint (4.2 s): https://liveatfoxridge.com/
    • First Contentful Paint (2.4 s): https://liveatfoxridge.com/
    • Speed Index (8.9 s): https://liveatfoxridge.com/

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

    For your web team: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. PageSpeed lists what holds it back.

    Your web team · a week or more · Important

    Web Vitals, GoogleReport an issue with this check

  • The page does not jump around while it loadsImportantTested by Google LighthousePartial

    Cumulative Layout Shift (0.188) CLS measures how much the page jumps while it loads, which makes people tap the wrong thing. web.dev names it one of three Core Web Vitals, and 0.1 or less is good.

    • Cumulative Layout Shift (0.188): https://liveatfoxridge.com/
    • Layout shift culprits: https://liveatfoxridge.com/
    • Avoid large layout shifts (4 layout shifts found): <section id="overview">: https://liveatfoxridge.com/

    What to do Stop content from moving as images and fonts load.

    For your web team: Set width and height on images and embeds, reserve space for late content, and use font-display with a matching fallback font.

    Your web team · about a day · Important

    Web Vitals, GoogleReport an issue with this check

  • Served fastImportantTested by Google LighthousePartial

    Document request latency (Est savings of 450 ms). A CDN (a network of servers near your visitors) reduces the network latency that slows a server's first response.

    • Document request latency (Est savings of 450 ms): https://liveatfoxridge.com/
    • Network Round Trip Times (10 ms): https://liveatfoxridge.com/
    • Server Backend Latencies (50 ms): https://liveatfoxridge.com/

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

    For your web team: Serve the page through a CDN or edge network over HTTP/2 or HTTP/3, compress text with gzip or Brotli, cache the document at the edge, and avoid redirects.

    Your web team · about a day · Important

    Reduce server response times (TTFB), ChromeReport an issue with this check

  • Images are the right sizeImportantTested by Google LighthousePartial

    Improve image delivery (Est savings of 213 KiB) and Image elements do not have explicit width and height. Serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 213 KiB): <img src="https://media.multihub.io/cdn-cgi/image/format=auto,w=640/property/6767906…" srcset="https://media.multihub.io/cdn-cgi/image/format=auto,w=160/property/6767906…" sizes="(min-width: 768px) 25vw, 50vw" alt="Blue playground slide and climbing structure in a gravel play area with tr…" loading="lazy" fetchpriority="auto" class="absolute inset-0 w-full h-full object-cover object-center">, from multihub.io: https://media.multihub.io/cdn-cgi/image/format=auto,w=640/property/6767906449166316/019fcdf5-eec6-73de-9356-f92957ad28eb.webp
    • Image elements do not have explicit width and height: <img src="/assets/repli_white-BirIi_dg.svg" alt="Repli Logo" height="36" loading="eager" fetchpriority="high" class="h-9 w-auto">: https://www.liveatfoxridge.com/assets/repli_white-BirIi_dg.svg

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

    For your web team: 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.

    Your web team · about a day · Important

    Properly size images, ChromeReport an issue with this check

  • The page does not weigh muchImportantTested by Google LighthousePartial

    Avoid enormous network payloads (Total size was 3,573 KiB), Reduce unused JavaScript (Est savings of 1,098 KiB), Reduce unused CSS (Est savings of 55 KiB), Minify JavaScript (Est savings of 43 KiB), Minify CSS (Est savings of 3 KiB), Duplicated JavaScript (Est savings of 6 KiB), and Legacy JavaScript (Est savings of 24 KiB). Large network payloads are highly correlated with long load times and cost visitors money on mobile data.

    • Avoid enormous network payloads (Total size was 3,573 KiB): https://www.liveatfoxridge.com/assets/index-BrZBWLY8.js
    • Reduce unused JavaScript (Est savings of 1,098 KiB): https://www.liveatfoxridge.com/assets/index-BrZBWLY8.js
    • Reduce unused CSS (Est savings of 55 KiB): @keyframes v-shake{59%{margin-left:0} …

    What to do Remove code and files the page does not use.

    For your web team: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. PageSpeed lists the files by size.

    Your web team · a few days · Important

    Avoid enormous network payloads, ChromeReport an issue with this check

  • Repeat visitors get a faster pageImportantTested by Google LighthousePartial

    Use efficient cache lifetimes (Est savings of 162 KiB) Fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 162 KiB), from hy.ly: https://my.hy.ly/js/attribution-manager.js?v=1.2
    • Use efficient cache lifetimes (Est savings of 162 KiB), from repli360.com: https://app.repli360.com/admin/rrac-website-script/eyJpdiI6IlJGQ1M3azJlWHI5MUtrOE40WDJ4QlE9PSIsInZhbHVlIjoib2k4NEkwRmNMQmNyY3VXUHVJb2JXUT09IiwibWFjIjoiYTE3MzRiMTkzNDhjMzc4NTExODMxYjAwMTQ0MTMyNzc3MGNlZTE1NmRiNDJhMzcxYzhhYmQzNmIyYWM1ZWEyOCJ9
    • Use efficient cache lifetimes (Est savings of 162 KiB), from eliseai.com: https://cdn.eliseai.com/@meetelise/chat

    What to do Let browsers keep images, scripts and styles between visits.

    For your web team: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag.

    Your web team · about an hour · Important

    Prevent unnecessary network requests with the HTTP Cache, GoogleReport an issue with this check

  • The page loads without errorsImportantTested by Google LighthousePartial

    Browser errors were logged to the console and Uses deprecated APIs (1 warning found). An error in the console means a problem on your page that you need to resolve.

    • %cHUB%c2253ms%c Image Type: 99 Not Found background:#861E5A;color:#fff;padding:4px 8px;border-radius:2px 0 0 2px; background:#636163;color:#bbb;padding:4px;border-radius:0 2px 2px 0;: https://liveatfoxridge.com/
    • Uses deprecated APIs (1 warning found): https://liveatfoxridge.com/

    What to do Open the page in a browser's developer tools and clear the errors it lists.

    For your web team: 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.

    Your web team · a few days · Important

    Browser errors were logged to the console, ChromeReport an issue with this check

  • Visitors are on a secure connectionImportantTested by Google LighthousePass

    Uses HTTPS A secure connection helps prevent intruders tampering with traffic between your site and its visitors.

    Why HTTPS matters, GoogleReport an issue with this check

  • Visitors are not interrupted on arrivalImportantTested by Google LighthousePass

    All 3 audits in this goal pass. Users are mistrustful of or confused by pages that ask for their location as soon as they load.

    Requests the geolocation permission on page load, ChromeReport an issue with this check

See if AI chooses you

An AI agent searched “apartments for rent royersford pa”, like 390 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 liveatfoxridge.com rebuilt, without these issues

55th of 89 residence sites graded so far. See the board.

How we grade