B

Usable by AI agents, with gaps

Speed: Fail (Google's lab run of this page)

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://spectraapts.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

    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
  • Each page has one clear addressPass

    All 2 audits in this goal pass. 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. 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
100

Understand

Do they understand who you are and what you offer?

25% of your grade · 7 of 7 goals pass

  • Your key facts are in the page itselfPass

    The page as your server sends it holds its text; scripts add 23 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
  • Your business is described in structured dataPass

    The home page's structured data names ApartmentComplex, LocalBusiness, PostalAddress, GeoCoordinates, Place, FloorPlan, QuantitativeValue, PriceSpecification, LocationFeatureSpecification, OpeningHoursSpecification, ReserveAction, EntryPoint, CommunicateAction, FindAction, PropertyValue, WebPage, ImageObject, and Action. 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, Google
  • 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
  • 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.

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

Act

Can they use your site for a shopper?

25% of your grade · 4 of 7 goals pass

  • 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://spectraapts.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
  • Text is readablePartial

    1 of the 2 audits in this goal falls short: Background and foreground colors do not have a sufficient contrast ratio. 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 3.59 (foreground color: #ffffff, background color: #2894a1, font size: 11.3pt (15px), font weight: normal). Expected contrast ratio of 4.5:1: <span class="vertaligner-primary secondary-font">: https://spectraapts.com/

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

    Rule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe
  • Buttons and links are big enough to tapPartial

    1 of the 2 audits in this goal falls short: Touch targets do not have sufficient size or spacing. web.dev recommends tap targets of around 48 pixels, and WCAG sets a minimum of 24 by 24 pixels.

    • 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">: https://spectraapts.com/

    What to do Ask the people who run your site to make small buttons and tightly packed links bigger on phones.

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

    Accessible tap targets, Google
  • Extra labels on controls are used correctlyPass

    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 axe
  • 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
  • Assistants can read your page's controlsPass

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

    Accessibility for agents, Chrome
71

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

  • The page does not jump around while it loadsFail

    Cumulative Layout Shift is 0.37 for real visitors of this page, last 28 days, which Google rates poor. 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.37 for real visitors of this page, last 28 days, which Google rates poor.: https://spectraapts.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
  • Repeat visitors get a faster pageFail

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

    • Use efficient cache lifetimes (Est savings of 76 KiB): https://spectraapts.com/assets/images/cache/2PwVv9dk7rfNGn9fwfxIG8brXF418bbUffqPKyf6-9e7f1ebcf2e8f70e7a22d03873d4a86b.jpg
    • Use efficient cache lifetimes (Est savings of 76 KiB): https://spectraapts.com/assets/images/page_pattern.jpg
    • Use efficient cache lifetimes (Est savings of 76 KiB): https://spectraapts.com/themer/assets/logo/logo_main_1755205607.png

    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

    3 of the 3 audits in this goal fall short: Largest Contentful Paint is 3.8 s for real visitors of this page, last 28 days, which Google rates needs improvement, First Contentful Paint is 2.3 s for real visitors of this page, last 28 days, which Google rates needs improvement, and Speed Index (5.2 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 3.8 s for real visitors of this page, last 28 days, which Google rates needs improvement.: https://spectraapts.com/
    • First Contentful Paint is 2.3 s for real visitors of this page, last 28 days, which Google rates needs improvement.: https://spectraapts.com/
    • Speed Index (5.2 s): https://spectraapts.com/

    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
  • Images are the right sizePartial

    2 of the 4 audits in this goal fall short: Improve image delivery (Est savings of 320 KiB) and Image elements do not have explicit width and height. 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 320 KiB): <img data-jdl-action="home-hero-impression" data-jdl-data="{&quot;index&quot;:0,&quot;count&quot;:4,&quot;media_type&quot;:&quot;image&quot;,&quot;title&quot;:&quot;Sophistication in Every…" data-jdl-view="" data-el="image[]" class="homepage__rotator-image" fetchpriority="high" src="https://spectraapts.com/assets/images/cache/2PwVv9dk7rfNGn9fwfxIG8brXF418b…" alt="a blue statue in front of a building" draggable="false" style="opacity: 1;">: https://spectraapts.com/assets/images/cache/2PwVv9dk7rfNGn9fwfxIG8brXF418bbUffqPKyf6-9e7f1ebcf2e8f70e7a22d03873d4a86b.jpg
    • 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_1755205607.png" alt="Spectra">: https://spectraapts.com/themer/assets/logo/logo_main_1755205607.png

    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 responds as soon as it appearsPass

    Total Blocking Time (0 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 (TBT), Google
  • The page does not weigh muchPass

    All 8 audits in this goal pass. Chrome says large network payloads are highly correlated with long load times and cost visitors money on mobile data.

    Avoid enormous network payloads, Chrome
  • 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
  • The page loads without errorsPass

    All 7 audits in this goal pass. Chrome says an error in the console means a problem on your page that you need to resolve.

    Browser errors were logged to the console, Chrome
  • 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
  • Served fastPass

    All 3 audits in this goal pass. Chrome says 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), Chrome

See how the sites the assistant picked grade

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

  • skylineredmond.com
  • elanredmond.com
  • theknollredmond.com

2nd of 10 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