clutch

D

Poor for AI agents

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

See the goal behind it

Speed: Fail (real visitors, last 28 days)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.

    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

Fix it,

or see it rebuilt

These 12 fixes add up to about four 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/live12north-com. Tell me how to fix each issue and the level of effort each fix takes.

  • See your site rebuilt

    Clutch rebuilds live12north.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
100

Find

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

25% of your grade · 9 of 9 goals pass

69

Understand

Can they tell who you are and what you offer?

25% of your grade · 5 of 7 goals pass

  • Headings give each page an outlineImportantFail

    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="content-image__subtitle">: https://live12north.com/
    • Fix any of the following: Heading order invalid: <h4 class="widget__title">: https://live12north.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

  • Images describe themselvesImportantFail

    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 width="512" height="512" src="https://live12north.com/wp-content/uploads/2025/01/chevron-up-solid.svg">: https://live12north.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 width="900" height="600" src="https://live12north.com/wp-content/uploads/2026/10/12-North-Promo-Drawer-G…" data-lazy-src="https://live12north.com/wp-content/uploads/2026/10/12-North-Promo-Drawer-G…" data-ll-status="loaded" class="entered lazyloaded">: https://live12north.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 width="900" height="600" src="https://live12north.com/wp-content/uploads/2026/10/12-North-Promo-Drawer-G…">: https://live12north.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.

    Your web team · a few days · Important

    Image SEO Best Practices, GoogleReport an issue with this check

  • Your key facts are in the page itselfCriticalPass

    The page as your server sends it holds its text; scripts add 11 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 CentralReport an issue with this check

  • Your business is described in structured dataImportantPass

    The home page's structured data names WebPage, ReadAction, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization, ImageObject, ApartmentComplex, and PostalAddress. 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

  • Lists and tables are built as lists and tablesImportantPass

    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

  • Every page has its own summary for search resultsImportantPass

    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 inImportantPass

    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

55

Act

Can they take the next step for a customer?

25% of your grade · 5 of 9 goals pass

  • Assistants can read your page's controlsMust haveCriticalFail

    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.

    • Buttons must have discernible text: <button class="menu-icon" type="button">: https://live12north.com/
    • Links must have discernible text: <a target="_blank" href="https://live12northapts.prospectportal.com/Apartments/module/application_a…" class="hover-container">: https://live12north.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 haveImportantFail

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

  • Buttons and links are big enough to tapImportantPartial

    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 (405.6px by 10.6px, 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 target="_blank" href="https://cardinalgroup.com" rel="noopener noreferrer nofollow">: https://live12north.com/

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

    Your web team · about an hour · Important

    Accessible tap targets, GoogleReport an issue with this check

  • Forms are labelledCriticalPass

    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 axeReport an issue with this check

  • Custom controls announce what they areImportantPass

    Elements with role="dialog" or role="alertdialog" have accessible names. WCAG, the web accessibility standard most laws point to, requires every control to expose its name and role to assistive technology and software.

    Accessibility for agents, ChromeReport an issue with this check

  • Extra labels on controls are used correctlyImportantPass

    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 pageImportantPass

    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

  • Text is readableImportantPass

    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

75

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 quicklyImportantPartial

    Largest Contentful Paint is 4.0 s for real visitors of this page, last 28 days, which Google rates needs improvement, First Contentful Paint is 3.5 s for real visitors of this page, last 28 days, which Google rates poor, and Speed Index (11.6 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.0 s for real visitors of this page, last 28 days, which Google rates needs improvement.: https://live12north.com/
    • First Contentful Paint is 3.5 s for real visitors of this page, last 28 days, which Google rates poor.: https://live12north.com/
    • Speed Index (11.6 s): https://live12north.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

  • Served fastImportantPartial

    Your home page is served over HTTP/1.1. A CDN (a network of servers near your visitors) reduces the network latency that slows a server's first response.

    • Served over HTTP/1.1: https://live12north.com/
    • Network Round Trip Times (20 ms): https://live12north.com/
    • Server Backend Latencies (120 ms): https://live12north.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 sizeImportantPartial

    Improve image delivery (Est savings of 1,104 KiB) and Displays images with incorrect aspect ratio. Serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 1,104 KiB): <img alt="Easytour Launch" src="https://easytourstorageprod.blob.core.windows.net/easytour-assets/easytour…" style="float: left;">, from Azure Web Services: https://easytourstorageprod.blob.core.windows.net/easytour-assets/easytour-wave.gif
    • Displays images with incorrect aspect ratio: <img width="900" height="600" src="https://live12north.com/wp-content/uploads/2026/10/12-North-Promo-Drawer-G…" data-lazy-src="https://live12north.com/wp-content/uploads/2026/10/12-North-Promo-Drawer-G…" data-ll-status="loaded" class="entered lazyloaded">: https://live12north.com/wp-content/uploads/2026/10/12-North-Promo-Drawer-Graphics-5.png

    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 muchImportantPartial

    Avoid enormous network payloads (Total size was 14,969 KiB), Reduce unused JavaScript (Est savings of 2,019 KiB), Reduce unused CSS (Est savings of 88 KiB), and Legacy JavaScript (Est savings of 44 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 14,969 KiB), from Azure Web Services: https://easytourstorageprod.blob.core.windows.net/easytour-assets/RazzleDazzleIntroVideo/63556795-c381-42a6-b1ac-f820a13046b30.ts
    • Reduce unused JavaScript (Est savings of 2,019 KiB), from Azure Web Services: https://easytourstorageprod.z19.web.core.windows.net/
    • Reduce unused CSS (Est savings of 88 KiB), from Google CDN: https://www.gstatic.com/recaptcha/releases/0lEGiwO4Qwx5R9ArxUy0mBpf/styles__ltr.css

    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 pageImportantPartial

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

    • Use efficient cache lifetimes (Est savings of 2,941 KiB), from Azure Web Services: https://easytourstorageprod.z19.web.core.windows.net/
    • Use efficient cache lifetimes (Est savings of 2,941 KiB), from Azure Web Services: https://easytourstorageprod.blob.core.windows.net/easytour-assets/easytour-wave.gif
    • Use efficient cache lifetimes (Est savings of 2,941 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.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 errorsImportantPartial

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

    • Access to XMLHttpRequest at 'https://consent.api.osano.com/record' from origin 'https://live12north.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.: https://live12north.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 responds as soon as it appearsImportantPass

    Interaction to Next Paint is 155 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), GoogleReport an issue with this check

  • The page does not jump around while it loadsImportantPass

    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, GoogleReport an issue with this check

  • Visitors are on a secure connectionImportantPass

    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 arrivalImportantPass

    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 near texas a&m”, like 720 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 live12north.com rebuilt, without these issues

109th of 138 residence sites graded so far. See the board.

How we grade