clutch

D

Poor for AI agents

Speed: Pass (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·Understand

    Headings give each page an outline

    Heading elements are not in a sequentially-descending order

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

    Your web team · about an hourSee the check

  3. Fail·Understand

    Images describe themselves

    Image elements do not have [alt] attributes

    What to do Describe every meaningful image.

    Your web team · a few daysSee the check

Fix it,

or see it rebuilt

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

  • See your site rebuilt

    Clutch rebuilds equityapartments.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
78

Find

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

25% of your grade · 6 of 9 goals pass

  • Pages that do not exist say soImportantFail

    A page that does not exist answers 200 with a normal page at https://equityapartments.com/, so every guessed address looks real. Google treats content behind a 404 or 410 as gone, and flags empty pages that answer 200 (success) as soft 404s.

    • Status 200: https://equityapartments.com/

    What to do Make a mistyped address show a page that says it was not found, with a 404 status behind it.

    For your web team: Return 404 (or 410 for a page that is gone) for unknown routes. A single-page app needs its server to answer unknown paths with the not-found page and a 404 status; a redirect to the home page makes every address look real.

    Your web team · about an hour · Important

    How Google Search handles HTTP status codes, GoogleReport an issue with this check

  • Your pages are listed in a sitemapImportantPartial

    https://equityapartments.com/sitemap.xml is a sitemap, and robots.txt does not name it. 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.

    • No Sitemap line naming the sitemap: https://equityapartments.com/robots.txt

    What to do Publish a sitemap and name it in robots.txt.

    For your web team: Serve a sitemap.xml (a urlset, or a sitemapindex for several files) and add a Sitemap line with the sitemap's full address to robots.txt.

    Your web team · about an hour · Important

    Build and submit a sitemap, GoogleReport an issue with this check

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

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

  • Search engines may list each pageCriticalPass

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

  • Search results can show your pages' wordsCriticalPass

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

  • Every page has its own titleImportantPass

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

  • Each page has one clear addressImportantPass

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

  • Pages open without detoursImportantPass

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

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 style="font-size:1.4em; padding-top:.3em; font-weight:100; color:white">: https://equityapartments.com/dallas/addison/lyle-apartments
    • Fix any of the following: Heading order invalid: <h4 class="panel-title">: https://equityapartments.com/dallas/addison/lyle-apartments
    • Fix any of the following: Heading order invalid: <h5>: https://equityapartments.com/dallas/addison/lyle-apartments

    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 src="https://media.equityapartments.com/image/upload/v1717685645/Marketing/Engr…" style="width: 100%; height: auto;">: https://equityapartments.com/dallas/addison/lyle-apartments
    • 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="https://media.equityapartments.com/image/upload/v1780602903/Marketing/Furn…" style="width: 100%; height: auto;">: https://equityapartments.com/dallas/addison/lyle-apartments
    • 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="https://media.equityapartments.com/image/upload/v1722630373/Marketing/Tech…" style="width: 100%; height: auto;">: https://equityapartments.com/dallas/addison/lyle-apartments

    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 75 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 Product and AggregateRating. 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

  • A short guide to your site for AI assistantsImportantNot yet

    llms.txt does not follow 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.

    • llms.txt does not follow recommendations: https://equityapartments.com/dallas/addison/lyle-apartments
    • llms.txt does not follow recommendations: https://equityapartments.com/dallas/addison/lyle-apartments

    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

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

  • Your AI tools are listed in an AI catalogImportantNot yet

    ARD manifest is invalid The Agentic Resource Discovery (ARD) draft is a format that helps assistants discover what a site offers, such as tools and agents; the standards are still emerging.

    • ARD manifest is invalid: https://equityapartments.com/dallas/addison/lyle-apartments

    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/ai-catalog.json with a specVersion and an entries list that follow the ARD schema. That is the path Lighthouse reads today; the ARD spec is moving to /.well-known/ard.json.

    Your web team · about a day · Important

    Agentic Resource Discovery specification, agenticresourcediscovery.orgReport an issue with this check

41

Act

Can they take the next step for a customer?

25% of your grade · 1 of 8 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.

    • ARIA input fields must have an accessible name: <div class="carousel-inner" role="listbox">: https://equityapartments.com/dallas/addison/lyle-apartments
    • Elements must only use permitted ARIA attributes: <i class="fa fa-leaf" style="color: #fff; margin-left: 0.125em;" aria-label="sustainable amenity">: https://equityapartments.com/dallas/addison/lyle-apartments
    • Certain ARIA roles must contain particular children: <div class="carousel-inner" role="listbox">: https://equityapartments.com/dallas/addison/lyle-apartments

    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://equityapartments.com/dallas/addison/lyle-apartments

    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

  • Custom controls announce what they areImportantPartial

    ARIA input fields do not have accessible names and ARIA progressbar elements do not 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.

    • Fix any of the following: 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: <div class="carousel-inner" role="listbox">: https://equityapartments.com/dallas/addison/lyle-apartments
    • Fix any of the following: 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: <div class="progress-bar progress-bar-success" role="progressbar" aria-valuenow="60" aria-valuemin="0" aria-valuemax="100" style="width: 63%;">: https://equityapartments.com/dallas/addison/lyle-apartments

    What to do Name every custom control, such as a date picker or a slider.

    For your web team: Give each element with an ARIA control role an accessible name through aria-label or aria-labelledby.

    Your web team · a few days · Important

    Accessibility for agents, ChromeReport an issue with this check

  • Extra labels on controls are used correctlyImportantPartial

    Elements use prohibited ARIA attributes and Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. 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.

    • Fix all of the following: aria-label attribute cannot be used on "i" elements with no valid role attribute.: <i class="fa fa-leaf" style="color: #fff; margin-left: 0.125em;" aria-label="sustainable amenity">: https://equityapartments.com/dallas/addison/lyle-apartments
    • Fix any of the following: Element has children which are not allowed: a[aria-label]: <div class="carousel-inner" role="listbox">: https://equityapartments.com/dallas/addison/lyle-apartments

    What to do Remove ARIA markup that is invalid and use plain HTML controls where they exist.

    For your web team: Use native elements first, give each ARIA role its required attributes and children, remove attributes the role does not allow, and keep ids unique.

    Your web team · a few days · Important

    Rule aria-roles: ARIA roles used must conform to valid values, Deque axeReport an issue with this check

  • Visitors can move around the pageImportantPartial

    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 lang="en">: https://equityapartments.com/dallas/addison/lyle-apartments

    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.

    Your web team · about a day · Important

    Accessibility for agents, ChromeReport an issue with this check

  • Text is readableImportantPartial

    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 2.26 (foreground color: #6cc04a, background color: #ffffff, font size: 9.8pt (13.008px), font weight: normal). Expected contrast ratio of 4.5:1: <button id="onetrust-pc-btn-handler" class="cookie-setting-link">: https://equityapartments.com/dallas/addison/lyle-apartments

    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

  • Buttons and links are big enough to tapImportantPass

    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

78

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

  • Repeat visitors get a faster pageImportantFail

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

    • Use efficient cache lifetimes (Est savings of 10,003 KiB), from sightmap.com: https://cdn.sightmap.com/assets/yz/vg/yzvgdn96vln/32/91/32914c86e6bae3e1ecda3958435bf90e.jpg
    • Use efficient cache lifetimes (Est savings of 10,003 KiB): https://images.equityapartments.com//media/tx_lyle/floorplans/Lyle_A24_1b1b_1272sqft.png
    • Use efficient cache lifetimes (Est savings of 10,003 KiB): https://images.equityapartments.com//media/tx_lyle/floorplans/Lyle_B19_2b2b_1533sqft.png

    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 main content shows up quicklyImportantPartial

    Speed Index (10.8 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 (10.8 s): https://equityapartments.com/dallas/addison/lyle-apartments
    • LCP request discovery: https://equityapartments.com/dallas/addison/lyle-apartments
    • Render-blocking requests (Est savings of 1,840 ms): https://equityapartments.com/Content/Styles/custom-bootstrap-c7e61cb155.css

    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

  • Images are the right sizeImportantPartial

    Improve image delivery (Est savings of 2,882 KiB), Displays images with incorrect aspect ratio, 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 2,882 KiB): <img src="https://media.equityapartments.com/image/upload/v1780602903/Marketing/Furn…" style="width: 100%; height: auto;">: https://media.equityapartments.com/image/upload/v1780602903/Marketing/Furnished_-_Marketing_box_-_Vertical.jpg
    • Displays images with incorrect aspect ratio: <img alt="" align="middle" width="100%" src="https://media.equityapartments.com/image/upload/v1780602903/Marketing/Furn…">: https://media.equityapartments.com/image/upload/v1780602903/Marketing/Furnished_-_Marketing_box_2.jpg
    • Image elements do not have explicit width and height: <img src="https://media.equityapartments.com/image/upload/v1780602903/Marketing/Furn…" style="width: 100%; height: auto;">: https://media.equityapartments.com/image/upload/v1780602903/Marketing/Furnished_-_Marketing_box_-_Vertical.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 muchImportantPartial

    Avoid enormous network payloads (Total size was 18,853 KiB), Reduce unused JavaScript (Est savings of 852 KiB), Reduce unused CSS (Est savings of 436 KiB), Minify JavaScript (Est savings of 194 KiB), Minify CSS (Est savings of 323 KiB), and Legacy JavaScript (Est savings of 29 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 18,853 KiB), from sightmap.com: https://cdn.sightmap.com/assets/yz/vg/yzvgdn96vln/32/91/32914c86e6bae3e1ecda3958435bf90e.jpg
    • Reduce unused JavaScript (Est savings of 852 KiB), from sightmap.com: https://sightmap.com/app/vendor.199cb81509aeb5c1.js
    • Reduce unused CSS (Est savings of 436 KiB): https://equityapartments.com/Content/Styles/ea5-77a92ca20a.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

  • The page loads without errorsImportantPartial

    Browser errors were logged to the console and Issues were logged in the Issues panel in Chrome Devtools. 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://equityapartments.com/dallas/addison/lyle-apartments
    • Issues were logged in the Issues panel in Chrome Devtools: https://equityapartments.com/dallas/addison/lyle-apartments

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

  • The page does not jump around while it loadsImportantPass

    Cumulative Layout Shift is 0.01 for real visitors of your whole site, 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

  • Served fastImportantPass

    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 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 “luxury apartments in addison tx”, 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 equityapartments.com rebuilt, without these issues

124th of 126 residence sites graded so far. See the board.

How we grade