C

Hard for AI agents to use

Speed: Fail (real visitors, last 28 days)

100

Find

Does your site let search engines and assistants read and list your pages?

25% of your grade · 11 of 11 goals pass

  • Search engines and AI assistants are allowed to read your sitePass

    Every AI search crawler and agent we grade is allowed. Training crawlers are allowed. A crawler is a robot that reads sites for a search engine or assistant, and one that is blocked cannot recommend you. Bing lists blocking Bingbot among the things to avoid, because content it cannot crawl may not be indexed or used in Copilot's answers.

    Overview of OpenAI crawlers, OpenAI
  • Search engines may list each pagePass

    The page answers, no tag or header keeps it out of search results, and robots.txt lets search crawlers read it. Google leaves out a page marked noindex, and a page its crawler cannot read cannot be listed or used as a supporting link in its AI features.

    AI features and your website, Google
  • Search results can show your pages' wordsPass

    All 2 audits in this goal pass. A page whose text is kept out of results leaves a search engine or assistant nothing to quote. Google's AI features follow nosnippet and max-snippet, and Bing keeps content marked noarchive out of Copilot and limits nocache pages to their address, title and snippet.

    Robots.txt Introduction and Guide, Google
  • Your pages are listed in a sitemapPass

    https://www.olympuspinegrove.com/sitemap.xml is a sitemap. Google and Bing use an XML sitemap named in robots.txt to find your pages, and neither promises to index every page in it. A page must be indexed to appear in Google's AI answers.

    Build and submit a sitemap, Google
  • Pages that do not exist say soPass

    A page that does not exist answers 404. Google treats content behind a 404 or 410 as gone, and flags empty pages that answer 200 (success) as soft 404s.

    How Google Search handles HTTP status codes, Google
  • Every page has its own titlePass

    The title is the page's own and describes it. Google builds the title link in search results from the page's title, and may change one that is missing, vague, boilerplate or repeated. A title of its own keeps your wording in front of searchers.

    Influencing Title Links in Google Search, Google
  • Titles and descriptions fit in a search resultPass

    All 2 audits in this goal pass. Google sets no length limit and cuts a title or description to the device's width. SEO tools measure a title in pixels, since 60 characters run from 267 to 1,133 pixels, and count a description in characters. A cut loses the last words.

    Influencing Title Links in Google Search, Google
  • Key pages say what they offer in the titlePass

    The title says what the page offers and where. Google asks for descriptive titles. SearchPilot's test of putting the location at the start of a healthcare provider's titles predicted 8.5% more organic sessions.

    Adding Location to the Start of Title Tags, SearchPilot
  • Each page has a clear address and place in your sitePass

    All 2 audits in this goal pass. Google uses one canonical address per page, recommends readable words rather than long ID numbers, and can show a breadcrumb trail in desktop results when the page marks one up.

    How to Specify a Canonical with rel="canonical" and Other Methods, Google
  • Pages open without detoursPass

    Avoid multiple page redirects: the page only switches to https or adds or drops www. Chrome says each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

    Avoid multiple page redirects, Chrome
  • A shared link shows a previewPass

    The page names a title, description and image for shared links, and an icon. Open Graph tags decide the title, description and image a link shows when shared; Google shows your icon in results.

    The Open Graph protocol, ogp.me
70

Understand

Do they understand who you are and what you offer?

25% of your grade · 4 of 7 goals pass

  • Your key facts are in the page itselfFail

    Your server sends 1433 words of the 889 the page shows once scripts run, and what it leaves out is content visitors come to the page for. An assistant that runs no script reads only what your server sends. 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.

    • Only there once scripts run: https://www.olympuspinegrove.com/
    • Only there once scripts run: https://www.olympuspinegrove.com/
    • Only there once scripts run: https://www.olympuspinegrove.com/

    What to do Ask whoever runs your site to make the home page send its text from the server, so it shows up with scripts turned off.

    For your web team: Render the page's content on the server or at build time, and use scripts to add to it. Fetch the page without a browser to check the text is in it.

    Understand JavaScript SEO basics, Google Search Central
  • Your business is described in structured dataPartial

    The structured data lacks apartment on /floor-plans, and gives the business no number of bedrooms and pets allowed. The page does not state the business's keywords. 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.

    • Not in the page's structured data: https://www.olympuspinegrove.com/floor-plans
    • No value on the business: https://www.olympuspinegrove.com/
    • No value on the business: https://www.olympuspinegrove.com/

    What to do Ask whoever runs your site to mark the business up with the most specific schema.org type that fits it, to add the facts this goal lists to the structured data of the pages that show them, and to state on the page any detail this goal says the page does not state.

    For your web team: Add a JSON-LD script whose "@type" is the most specific schema.org type that fits the business, with each missing property set to the value the page shows, a node for each missing type on the page that shows it, and the value of each detail the page does not state in the text of the page. schema.org lists every type, its subtypes and the properties of each.

    About Usage Statistics, schema.org
  • Lists and tables are built as lists and tablesPartial

    1 of the 4 audits in this goal falls short: List items (<li>) are not contained within <ul>, <ol> or <menu> parent elements. 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.

    • Fix any of the following: List item does not have a <ul>, <ol> parent element: <li index="0" class="photoGalleryThumbs asymetric-big-image" data-index="0">: https://olympuspinegrove.com/

    What to do Ask the people who run your site to build price lists and schedules as real lists and tables.

    For your web team: Use ul, ol and dl with li, dt and dd children, and table markup with th header cells for tabular data, rather than line breaks and styled divs.

    Rule list: <ul> and <ol> must only directly contain <li>, <script> or <template> elements, Deque axe
  • A short guide to your site for AI assistantsPass

    llms.txt follows recommendations llmstxt.org proposes the file so assistants find what they need and follow its links. Lighthouse calls it an emerging convention and Google Search does not use it, so it is a bonus.

    Optimizing your website for generative AI features on Google Search, Google
  • Every page has its own summary for search resultsPass

    The description is the page's own and reads as a summary. 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, Google
  • Headings give each page an outlinePass

    Heading elements appear in a sequentially-descending order Google's guide to AI features says headings give a page a clear structure.

    Optimizing your website for generative AI features on Google Search, Google
  • Images describe themselvesPass

    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. It asks for descriptive file names.

    Image SEO Best Practices, Google
  • Pages say which language they are inPass

    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 axe
67

Act

Can they use your site for a shopper?

25% of your grade · 6 of 9 goals pass

  • Assistants can read your page's controlsMust haveFail

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

    A must have. While it fails, your letter stays at C or lower.

    • ARIA commands must have an accessible name: <a data-dm-multisize-attr="href" data-image-url="https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa99-d2f2-715b-9ace…" style="" role="button" tabindex="0">: https://olympuspinegrove.com/

    What to do Ask whoever runs your site to 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.

    Accessibility for agents, Chrome
  • Your site offers tools to AI assistantsMust haveFail

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

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

    • PageSpeed's "WebMCP tools registered" audit lists no tool: https://olympuspinegrove.com/

    What to do Ask whoever runs your site to 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 .

    WebMCP for developers, Chrome
  • Forms are labelledPass

    Form elements have associated labels WCAG requires every form field to have a label or instructions, and the axe rule label checks for it.

    Rule label: Form elements must have labels, Deque axe
  • Extra labels on controls are used correctlyPass

    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 axe
  • Text is readablePass

    All 3 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 axe
  • Buttons and links are big enough to tapPass

    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, Google
  • Visitors can move around the pagePass

    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, Chrome
  • Videos and embedded frames have textPass

    <frame> or <iframe> elements have a title WCAG, the web accessibility standard most laws point to, requires captions for the audio in prerecorded video.

    Accessibility for agents, Chrome
68

Performance

Is it fast and sound 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 · 3 of 10 goals pass

  • Repeat visitors get a faster pageFail

    Use efficient cache lifetimes (Est savings of 288 KiB) web.dev says fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 288 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js
    • Use efficient cache lifetimes (Est savings of 288 KiB), from Facebook: https://connect.facebook.net/en_US/bundle/sdk.js/
    • Use efficient cache lifetimes (Est savings of 288 KiB), from repli360.com: https://app.repli360.com/admin/rrac-website-script/eyJpdiI6IkxsTDlrVDBnQUU0dlpuN0VEcGp6ZGc9PSIsInZhbHVlIjoiN2NxS2ZBU2JYTW5LSUxiSkc2MEtjdz09IiwibWFjIjoiM2YwNTE4MDg1YTJiOTQ1OGUxOGI0N2RkODNlY2U1MWE0NTE4ZWJlMTk3YzEwOTE4OGJmODBiNmViYTlhM2Y5ZSJ9

    What to do Ask the people who run your site to 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.

    Prevent unnecessary network requests with the HTTP Cache, Google
  • The main content shows up quicklyPartial

    1 of the 3 audits in this goal falls short: Speed Index (16.3 s). Measured from real visitors of your whole site, 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.

    • Speed Index (16.3 s): https://olympuspinegrove.com/
    • LCP breakdown: https://olympuspinegrove.com/
    • Render-blocking requests (Est savings of 750 ms), from cdn-website.com: https://static.cdn-website.com/mnlt/production/6862/_dm/s/rt/dist/scripts/d-js-one-runtime-unified-mobile.min.js

    What to do Ask the people who run your site to 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.

    Web Vitals, Google
  • The page does not jump around while it loadsPartial

    Cumulative Layout Shift is 0.21 for real visitors of your whole site, last 28 days, which Google rates needs improvement. 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 is 0.21 for real visitors of your whole site, last 28 days, which Google rates needs improvement.: https://olympuspinegrove.com/
    • Layout shift culprits: https://olympuspinegrove.com/
    • Avoid large layout shifts (15 layout shifts found): <div class="u_1498584710 dmRespCol small-12 large-7 medium-7" id="1498584710">: https://olympuspinegrove.com/

    What to do Ask the people who run your site to 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.

    Web Vitals, Google
  • Images are the right sizePartial

    1 of the 4 audits in this goal falls short: Improve image delivery (Est savings of 48,778 KiB). Chrome says serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 48,778 KiB): <img src="https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa9b-91ab-72ca-96d9…" alt="Fenced-in dog park with agility equipment and a playground in the backgrou…">, from cdn-website.com: https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa9b-91ab-72ca-96d9-a9dc58417465.webp

    What to do Ask the people who run your site to 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.

    Properly size images, Chrome
  • The page does not weigh muchPartial

    7 of the 7 audits in this goal fall short: Avoid enormous network payloads (Total size was 54,868 KiB), Reduce unused JavaScript (Est savings of 1,243 KiB), Reduce unused CSS (Est savings of 91 KiB), Minify JavaScript (Est savings of 54 KiB), Minify CSS (Est savings of 3 KiB), Duplicated JavaScript (Est savings of 6 KiB), and Legacy JavaScript (Est savings of 29 KiB). Chrome says large network payloads are highly correlated with long load times and cost visitors money on mobile data.

    • Avoid enormous network payloads (Total size was 54,868 KiB), from cdn-website.com: https://irp.cdn-website.com/d4191897/dms3rep/multi/01a0aa9b-91ab-72ca-96d9-a9dc58417465.webp
    • Reduce unused JavaScript (Est savings of 1,243 KiB), from eliseai.com: https://cdn.eliseai.com/@meetelise/chat
    • Reduce unused CSS (Est savings of 91 KiB), from cdn-website.com: https://irp.cdn-website.com/d4191897/files/d4191897_withFlex_0.min.css?v=118

    What to do Ask the people who run your site to 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.

    Avoid enormous network payloads, Chrome
  • The page loads without errorsPartial

    2 of the 7 audits in this goal fall short: Browser errors were logged to the console and Uses deprecated APIs (1 warning found). Chrome says an error in the console means a problem on your page that you need to resolve.

    • SyntaxError: Unexpected token '-': https://olympuspinegrove.com/
    • Uses deprecated APIs (1 warning found): https://olympuspinegrove.com/

    What to do Ask the people who run your site to 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.

    Browser errors were logged to the console, Chrome
  • Served fast from servers near your visitorsPartial

    2 of the 5 audits in this goal fall short: Document request latency (Est savings of 130 ms) and We found no CDN or edge network in front of your home page. A CDN keeps copies of your site on servers close to each visitor, so pages arrive sooner. Chrome says a CDN reduces the network latency that slows a server's first response.

    • Document request latency (Est savings of 130 ms): https://olympuspinegrove.com/
    • No CDN in the page's response headers: https://www.olympuspinegrove.com/
    • Network Round Trip Times (30 ms): https://olympuspinegrove.com/

    What to do Ask the people who run your site to put a CDN in front of it and to turn on compression and caching.

    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, avoid redirects, and send Strict-Transport-Security with a max-age above zero.

    Reduce server response times (TTFB), Chrome
  • The page responds as soon as it appearsPass

    Interaction to Next Paint is 89 ms for real visitors of your whole site, last 28 days, which Google rates good. 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 (TBT), Google
  • Visitors are on a secure connectionPass

    Uses HTTPS web.dev says a secure connection helps prevent intruders tampering with traffic between your site and its visitors.

    Why HTTPS matters, Google
  • Visitors are not interrupted on arrivalPass

    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, Chrome

See how the sites the assistant picked grade

The assistant opened 3 other sites for this shopper. Grade them with the same checks.

  • rosewickapartments.com
  • qpmgmt.com
  • ascendpinegrove.com

5th of 9 residence sites graded so far. See the board.

Get a site that keeps itself ready

Get this site rebuilt in Clutch. It grades itself as assistants change and fixes what slips, so it stays ready on its own. You approve the new site before it goes live.

How we grade