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

    Assistants can read your page's controls

    Accessibility tree is not well-formed

    What to do Run Google's PageSpeed Insights on the home page and fix the accessibility problems it lists, which are mostly buttons and fields with no label.

    Your web team · about a daySee the check

  2. Fail·Act

    Your site offers tools to AI assistants

    Your home page offers no tools to AI assistants and No WebMCP tools detected on page load.

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

    Your web team · about a daySee the check

  3. Fail·Act

    Agents can discover your MCP server

    Your site has no ARD catalog at /.well-known/ard.json, so an agent cannot discover an MCP server from it.

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

    Your web team · a few daysSee the check

Fix it,

or see it rebuilt

These 19 fixes add up to about six weeks of your web team's time.

  • Send to your agency

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

    Send to your agency

  • Explore with your AI

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

    Read this report on our website: clutch.io/grade/keysatwildwood-com. Tell me how to fix each issue and the level of effort each fix takes.

  • See your site rebuilt

    Clutch rebuilds keysatwildwood.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
90

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

  • Headings give each page an outlineImportantTested by Google LighthouseFail

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

    • Fix any of the following: Heading order invalid: <h3 class="uagb-heading-text">: https://keysatwildwood.com/

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

    For your web team: Use h1 once, then h2 to h6 without skipping a level, and remove or fill any heading element that has no text.

    Your web team · about an hour · Important

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

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

    Your site does not publish /llms.txt. 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.

    • Lighthouse found no /llms.txt: https://keysatwildwood.com/

    What to do Publish /llms.txt with your business name as its title and links to your most important pages.

    For your web team: Serve a Markdown file at /llms.txt with a 200, and keep it out of the way of any rule that routes unknown paths to the home page or answers them with a firewall page. Start it with an H1 naming the site, then sections of Markdown links to key pages, as llmstxt.org describes.

    Your web team · about an hour · Important

    llms.txt audit, ChromeReport an issue with this check

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

    Your site does not publish an ARD catalog at /.well-known/ard.json. 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.

    • Lighthouse found no ARD catalog at /.well-known/ard.json: https://keysatwildwood.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://keysatwildwood.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://keysatwildwood.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

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

    Document does not have 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.

    • Document does not have a meta description: https://keysatwildwood.com/

    What to do Write a one or two sentence summary of every page, different on each.

    For your web team: Add <meta name="description" content="..."> to the head of every page. Write a sentence or two that are unique to that page.

    Your web team · about an hour · Important

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

  • Your key facts are in the page itselfCriticalTested by ClutchPass

    Your home page holds 366 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 WebSite, SearchAction, WebPage, ReadAction, Organization, 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

  • Images describe themselvesImportantTested by Google LighthousePass

    Image elements have [alt] attributes 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 2 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

  • Pages say which language they are inImportantTested by Google LighthousePass

    All 2 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

46

Act

Can they take the next step for a customer?

25% of your grade · 3 of 8 goals pass

  • Assistants can read your page's controlsMust haveCriticalTested by Google LighthouseFail

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

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

    • Links must have discernible text: <a class="spectra-container-link-overlay" rel="noopener" href="/contact">: https://keysatwildwood.com/

    What to do Run Google's PageSpeed Insights on the home page and fix the accessibility problems it lists, which are mostly buttons and fields with no label.

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

    Your web team · about a day · Critical

    Accessibility for agents, ChromeReport an issue with this check

  • 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://keysatwildwood.com/
    • No WebMCP tools detected on page load: https://keysatwildwood.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

    Your site has no ARD catalog at /.well-known/ard.json, so an agent cannot discover an MCP server from it. 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.

    • Status 404: https://keysatwildwood.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

  • Text is readableImportantTested by Google LighthousePartial

    Background and foreground colors do not have a sufficient contrast ratio and Links rely on color to be distinguishable. WCAG requires text to contrast with its background by at least 4.5 to 1, and the axe rule color-contrast checks for it.

    • Fix any of the following: Element has insufficient color contrast of 2.25 (foreground color: #ffffff, background color: #f78da7, font size: 10.5pt (14px), font weight: bold). Expected contrast ratio of 4.5:1: <strong>: https://keysatwildwood.com/
    • Fix any of the following: The link has insufficient color contrast of 2.25:1 with the surrounding text. (Minimum contrast is 3:1, link text: #f78da7, surrounding text: #ffffff) The link has no styling (such as underline) to distinguish it from the surrounding text: <a href="/contact">: https://keysatwildwood.com/

    What to do Darken pale text and underline the links inside paragraphs.

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

    Your web team · about a day · Important

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

  • Extra labels on controls are used correctlyImportantTested by Google LighthousePass

    All 11 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 2 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

  • 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

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

    • Agent Skills index not found: https://keysatwildwood.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

73

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

  • The main content shows up quicklyImportantTested by Google LighthousePartial

    Largest Contentful Paint is 4.1 s for real visitors of this page, last 28 days, which Google rates poor, First Contentful Paint is 3.6 s for real visitors of this page, last 28 days, which Google rates poor, and Speed Index (3.5 s). Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone. 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 is 4.1 s for real visitors of this page, last 28 days, which Google rates poor.: https://keysatwildwood.com/
    • First Contentful Paint is 3.6 s for real visitors of this page, last 28 days, which Google rates poor.: https://keysatwildwood.com/
    • Speed Index (3.5 s): https://keysatwildwood.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 responds as soon as it appearsImportantTested by Google LighthousePartial

    Total Blocking Time (380 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 (380 ms): https://keysatwildwood.com/
    • Avoid long main-thread tasks (4 long tasks found), from Facebook: https://connect.facebook.net/signals/config/1291657839818246?v=2.9.439&r=stable&domain=keysatwildwood.com&im=1&hme=1f127d11ce7bba675ee077e129c6ec7e07038113ad3e920301e60f2f865dc776&ex_m=119%2C243%2C172%2C27%2C82%2C83%2C163%2C78%2C77%2C11%2C182%2C102%2C20%2C154%2C142%2C46%2C85%2C90%2C184%2C111%2C150%2C177%2C8%2C4%2C5%2C7%2C6%2C3%2C103%2C116%2C162%2C72%2C186%2C110%2C185%2C212%2C264%2C37%2C84%2C284%2C283%2C282%2C14%2C25%2C28%2C40%2C62%2C118%2C68%2C10%2C73%2C112%2C113%2C114%2C120%2C145%2C38%2C36%2C147%2C148%2C149%2C144%2C143%2C173%2C86%2C176%2C174%2C175%2C57%2C69%2C67%2C138%2C19%2C180%2C52%2C334%2C335%2C336%2C333%2C32%2C17%2C31%2C18%2C33%2C34%2C35%2C55%2C164%2C87%2C127%2C22%2C24%2C51%2C47%2C49%2C48%2C95%2C104%2C108%2C125%2C161%2C165%2C53%2C126%2C29%2C26%2C134%2C79%2C43%2C167%2C166%2C168%2C158%2C156%2C30%2C42%2C66%2C124%2C179%2C80%2C21%2C129%2C93%2C76%2C23%2C97%2C98%2C131%2C96%2C152%2C151%2C155%2C109%2C178%2C181%2C41%2C350%2C372%2C257%2C239%2C70%2C240%2C238%2C375%2C366%2C59%2C258%2C122%2C146%2C92%2C136%2C61%2C54%2C56%2C128%2C135%2C141%2C140%2C65%2C74%2C169%2C88%2C89%2C130%2C44%2C39%2C60%2C63%2C115%2C183%2C1%2C139%2C16%2C137%2C12%2C2%2C64%2C105%2C15%2C75%2C71%2C133%2C101%2C100%2C188%2C189%2C106%2C107%2C9%2C117%2C187%2C58%2C159%2C99%2C91%2C81%2C132%2C121%2C170%2C50%2C160%2C0%2C94%2C153%2C157%2C171%2C45%2C123%2C13%2C190
    • Max Potential First Input Delay (240 ms): https://keysatwildwood.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

  • Images are the right sizeImportantTested by Google LighthousePartial

    Improve image delivery (Est savings of 580 KiB). Serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 580 KiB): <img decoding="async" width="1024" height="683" src="https://keysatwildwood.com/wp-content/uploads/2026/07/KeysatWildwood-69-76…" alt="KeysatWildwood" class="wp-image-216" srcset="https://keysatwildwood.com/wp-content/uploads/2026/07/KeysatWildwood-69-10…" sizes="(max-width: 1024px) 100vw, 1024px">: https://keysatwildwood.com/wp-content/uploads/2026/07/KeysatWildwood-69-768x512.jpg

    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,450 KiB), Reduce unused JavaScript (Est savings of 269 KiB), Reduce unused CSS (Est savings of 46 KiB), Minify CSS (Est savings of 4 KiB), and Legacy JavaScript (Est savings of 59 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,450 KiB): https://keysatwildwood.com/wp-content/uploads/2026/07/KeysatWildwood-1-scaled.jpg
    • Reduce unused JavaScript (Est savings of 269 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtag/js?id=G-T469FRH5ZT&cx=c&gtm=4e6b90
    • Reduce unused CSS (Est savings of 46 KiB): https://keysatwildwood.com/wp-content/themes/twentytwentyone/style.css?ver=2.6

    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 318 KiB) Fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 318 KiB), from Facebook: https://connect.facebook.net/signals/config/1291657839818246?v=2.9.439&r=stable&domain=keysatwildwood.com&im=1&hme=1f127d11ce7bba675ee077e129c6ec7e07038113ad3e920301e60f2f865dc776&ex_m=119%2C243%2C172%2C27%2C82%2C83%2C163%2C78%2C77%2C11%2C182%2C102%2C20%2C154%2C142%2C46%2C85%2C90%2C184%2C111%2C150%2C177%2C8%2C4%2C5%2C7%2C6%2C3%2C103%2C116%2C162%2C72%2C186%2C110%2C185%2C212%2C264%2C37%2C84%2C284%2C283%2C282%2C14%2C25%2C28%2C40%2C62%2C118%2C68%2C10%2C73%2C112%2C113%2C114%2C120%2C145%2C38%2C36%2C147%2C148%2C149%2C144%2C143%2C173%2C86%2C176%2C174%2C175%2C57%2C69%2C67%2C138%2C19%2C180%2C52%2C334%2C335%2C336%2C333%2C32%2C17%2C31%2C18%2C33%2C34%2C35%2C55%2C164%2C87%2C127%2C22%2C24%2C51%2C47%2C49%2C48%2C95%2C104%2C108%2C125%2C161%2C165%2C53%2C126%2C29%2C26%2C134%2C79%2C43%2C167%2C166%2C168%2C158%2C156%2C30%2C42%2C66%2C124%2C179%2C80%2C21%2C129%2C93%2C76%2C23%2C97%2C98%2C131%2C96%2C152%2C151%2C155%2C109%2C178%2C181%2C41%2C350%2C372%2C257%2C239%2C70%2C240%2C238%2C375%2C366%2C59%2C258%2C122%2C146%2C92%2C136%2C61%2C54%2C56%2C128%2C135%2C141%2C140%2C65%2C74%2C169%2C88%2C89%2C130%2C44%2C39%2C60%2C63%2C115%2C183%2C1%2C139%2C16%2C137%2C12%2C2%2C64%2C105%2C15%2C75%2C71%2C133%2C101%2C100%2C188%2C189%2C106%2C107%2C9%2C117%2C187%2C58%2C159%2C99%2C91%2C81%2C132%2C121%2C170%2C50%2C160%2C0%2C94%2C153%2C157%2C171%2C45%2C123%2C13%2C190
    • Use efficient cache lifetimes (Est savings of 318 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js
    • Use efficient cache lifetimes (Est savings of 318 KiB), from Amazon Web Services: https://capi-automation.s3.us-east-2.amazonaws.com/public/client_js/capiParamBuilder/clientParamBuilder.bundle.js

    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. An error in the console means a problem on your page that you need to resolve.

    • Failed to load resource: net::ERR_CONNECTION_FAILED: https://keysatwildwood.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

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

    Cumulative Layout Shift is 0.10 for real visitors of this page, last 28 days, which Google rates good. 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.

    Web Vitals, GoogleReport 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

  • Served fastImportantTested by Google LighthousePass

    All 3 audits in this goal pass. A CDN (a network of servers near your visitors) reduces the network latency that slows a server's first response.

    Reduce server response times (TTFB), ChromeReport 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 in wildwood fl”, like 590 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 keysatwildwood.com rebuilt, without these issues

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

How we grade