D

Poor for AI agents

Speed: Pass (real visitors, last 28 days)

Capped at D: assistants have trouble acting on your site (Act 50). Your checks earned 74.

100

Find

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

25% of your grade · 9 of 9 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

    Page isn’t blocked from indexing 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.thegibsongp.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
  • Every page has its own titlePass

    Document has a <title> element 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 keeps your wording in front of searchers.

    Influencing Title Links in Google Search, 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
  • Each page has one clear addressPass

    Document has a valid hreflang Google uses one canonical address per page, and uses hreflang to send searchers to the version of the page in their language.

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

    All 2 audits in this goal pass. Each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds.

    Avoid multiple page redirects, Chrome
69

Understand

Do they understand who you are and what you offer?

25% of your grade · 5 of 7 goals pass

  • Your business is described in structured dataFail

    The page has no structured data with a type. 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.

    • The page has no structured data with a type: https://www.thegibsongp.com/

    What to do Mark the business up with the most specific schema.org type that fits it.

    For your web team: Add a JSON-LD script to the home page whose "@type" is the most specific schema.org type that fits the business. schema.org lists every type and its subtypes.

    Intro to structured data, Google
  • Images describe themselvesFail

    Image elements do not 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.

    • Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation": <img src="data:image/svg+xml,%3csvg%20width='54'%20height='24'%20viewBox='0%200%2054…">: https://thegibsongp.com/
    • Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation": <img src="data:image/svg+xml,%3csvg%20xmlns='http://www.w3.org/2000/svg'%20width='15…" class="chakra-image getflex-widget-0">: https://thegibsongp.com/
    • Fix any of the following: Element does not have an alt attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element's default semantics were not overridden with role="none" or role="presentation": <img src="data:image/svg+xml,%3csvg%20xmlns='http://www.w3.org/2000/svg'%20width='12…" class="chakra-image getflex-widget-0">: https://thegibsongp.com/

    What to do Describe every meaningful image.

    For your web team: Give each meaningful img an alt attribute that says what it shows, an empty alt="" to decorative images, and a text name to image buttons, svg graphics and objects.

    Image SEO Best Practices, Google
  • Your key facts are in the page itselfPass

    The page as your server sends it holds its text; scripts add 5 pieces of text. 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 Central
  • Headings give each page an outlinePass

    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, Google
  • Lists and tables are built as lists and tablesPass

    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 axe
  • Every page has its own summary for search resultsPass

    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, Google
  • Pages say which language they are inPass

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

Act

Can they use your site for a shopper?

25% of your grade · 3 of 7 goals pass

  • Assistants can read your page's controlsMust haveFail

    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 C or lower.

    • Links must have discernible text: <a href="https://www.tiktok.com/@thegibsonapts" target="_blank" class="menu-socials_link hidden w-inline-block">: https://thegibsongp.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.

    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.

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

    • PageSpeed's "WebMCP tools registered" audit lists no tool: https://thegibsongp.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 .

    WebMCP for developers, Chrome
  • Visitors can move around the pagePartial

    Document does not have a main landmark. WCAG, the web accessibility standard most laws point to, requires every function of a page to work from a keyboard.

    • Fix all of the following: Document does not have a main landmark: <html data-wf-domain="www.thegibsongp.com" data-wf-page="69ef5c60736e162073d4739e" data-wf-site="69ef5c5a736e162073d4728b" lang="en" class="w-mod-js w-mod-touch wf-montserrat-n6-active wf-montserrat-n1-active wf-mo…" data-theme="light" style="color-scheme: light;">: https://thegibsongp.com/

    What to do Make the page work from the keyboard alone.

    For your web team: Wrap the page's content in one main element, add a skip link to it, keep tabindex at 0 or less, and remove meta refresh redirects.

    Accessibility for agents, Chrome
  • Extra labels on controls are used correctlyPass

    All 13 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 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 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
77

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

  • Repeat visitors get a faster pageFail

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

    • Use efficient cache lifetimes (Est savings of 1,182 KiB), from getflex.com: https://sdk.getflex.com/widgets/v1/widgets.js?clientId=recA0Z0jQ1tKwjCsf
    • Use efficient cache lifetimes (Est savings of 1,182 KiB), from getflex.com: https://sdk.getflex.com/widgets/v1/CooperMdBT-Italic.ttf
    • Use efficient cache lifetimes (Est savings of 1,182 KiB), from getflex.com: https://sdk.getflex.com/widgets/v1/CooperMdBT-Regular.ttf

    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.

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

    First Contentful Paint is 1.8 s for real visitors of this page, last 28 days, which Google rates needs improvement and Speed Index (9.4 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.

    • First Contentful Paint is 1.8 s for real visitors of this page, last 28 days, which Google rates needs improvement.: https://thegibsongp.com/
    • Speed Index (9.4 s): https://thegibsongp.com/
    • LCP request discovery: https://thegibsongp.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.

    Web Vitals, Google
  • Served fastPartial

    Document request latency (Est savings of 190 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 190 ms): https://thegibsongp.com/
    • Network Round Trip Times (20 ms): https://thegibsongp.com/
    • Server Backend Latencies (160 ms): https://thegibsongp.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.

    Reduce server response times (TTFB), Chrome
  • Images are the right sizePartial

    Improve image delivery (Est savings of 694 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 694 KiB): <img src="https://cdn.prod.website-files.com/69ef5c60736e162073d473cf/6adf694b01a58b…" loading="lazy" alt="A3" class="floor-plan-image">, from website-files.com: https://cdn.prod.website-files.com/69ef5c60736e162073d473cf/6adf694b01a58b56702b9728_6a3bf74647d5a1.94049995429.jpeg
    • Image elements do not have explicit width and height: <img src="https://cdn.prod.website-files.com/69ef5c60736e162073d473cf/69ef5cc90acc03…" loading="lazy" alt="" class="nav-logo">, from website-files.com: https://cdn.prod.website-files.com/69ef5c60736e162073d473cf/69ef5cc90acc03e590b2a4bc_header-logo.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.

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

    Avoid enormous network payloads (Total size was 3,931 KiB), Reduce unused JavaScript (Est savings of 550 KiB), and Legacy JavaScript (Est savings of 22 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,931 KiB), from website-files.com: https://cdn.prod.website-files.com/69ef5c5a736e162073d4728b/69ef66d3d46db9a0ceb57f23_Abstract_Pattern8_Repeat.png
    • Reduce unused JavaScript (Est savings of 550 KiB), from eliseai.com: https://cdn.eliseai.com/@meetelise/chat
    • Legacy JavaScript (Est savings of 22 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js

    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.

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

    Browser errors were logged to the console. An error in the console means a problem on your page that you need to resolve.

    • Error: <svg> attribute height: Expected length, "auto".: https://thegibsongp.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.

    Browser errors were logged to the console, Chrome
  • The page responds as soon as it appearsPass

    Interaction to Next Paint is 95 ms for real visitors of this page, 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
  • The page does not jump around while it loadsPass

    Cumulative Layout Shift is 0.00 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, Google
  • Visitors are on a secure connectionPass

    Uses HTTPS 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.

  • bradburyliving.com
  • ardenatmidtowngp.com
  • prairiemodernapartments.com

22nd of 22 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