clutch

D

Poor for AI agents

Capped at D: your pages load slowly on phones (Performance 51). Your checks earned 82.

See the goal behind it

Speed: Fail (Google's lab run of this page)Core Web Vitals, Google

Start here.

These hold your letter down the most
  1. Fail·Performance

    The main content shows up quickly

    Largest Contentful Paint (4.8 s), First Contentful Paint (3.1 s), and Speed Index (6.5 s). Lab test on a phone: too few real visitors to measure it.

    What to do Make the first screen load faster on phones, starting with its biggest image.

    Your web team · a week or moreSee the check

  2. Fail·Performance

    The page does not jump around while it loads

    Cumulative Layout Shift (0.435)

    What to do Stop content from moving as images and fonts load.

    Your web team · about a daySee the check

  3. Fail·Performance

    Visitors are on a secure connection

    Does not use HTTPS (1 insecure request found)

    What to do Serve every page over a secure connection and send the plain address to it.

    Your web team · about an hourSee the check

Fix it,

or see it rebuilt

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

  • See your site rebuilt

    Clutch rebuilds liveatthriveexchange.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

100

Understand

Can they tell who you are and what you offer?

25% of your grade · 7 of 7 goals pass

78

Act

Can they take the next step for a customer?

25% of your grade · 5 of 8 goals pass

  • 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://liveatthriveexchange.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

  • 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 4.43 (foreground color: #6c757f, background color: #f9f9f6, font size: 14.0pt (18.6778px), font weight: normal). Expected contrast ratio of 4.5:1: <div class="px-3 pt-4 h2 text-md icon-text font-weight-medium" customlabelreplaced="">: https://liveatthriveexchange.com/

    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

  • Assistants can read your page's controlsCriticalPass

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

    Accessibility for agents, ChromeReport 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 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, ChromeReport 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

51

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 quicklyImportantFail

    Largest Contentful Paint (4.8 s), First Contentful Paint (3.1 s), and Speed Index (6.5 s). Lab test on a phone: too few real visitors to measure it. 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 (4.8 s): https://liveatthriveexchange.com/
    • First Contentful Paint (3.1 s): https://liveatthriveexchange.com/
    • Speed Index (6.5 s): https://liveatthriveexchange.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

  • The page does not jump around while it loadsImportantFail

    Cumulative Layout Shift (0.435) 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 (0.435): https://liveatthriveexchange.com/
    • Layout shift culprits: https://liveatthriveexchange.com/
    • Avoid large layout shifts (15 layout shifts found): <div id="onetrust-banner-sdk" class="otFlat bottom ot-wo-title vertical-align-content ot-buttons-fw" tabindex="0" aria-label="Privacy" aria-describedby="onetrust-policy-text" style="bottom: 0px;">: https://liveatthriveexchange.com/

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

    Your web team · about a day · Important

    Web Vitals, GoogleReport an issue with this check

  • Visitors are on a secure connectionImportantFail

    Does not use HTTPS (1 insecure request found) A secure connection helps prevent intruders tampering with traffic between your site and its visitors.

    • Does not use HTTPS (1 insecure request found): http://www.liveatthriveexchange.com/

    What to do Serve every page over a secure connection and send the plain address to it.

    For your web team: Serve every page and file over a valid certificate, redirect http to https in one hop, and load no resource over plain http.

    Your web team · about an hour · Important

    Why HTTPS matters, GoogleReport an issue with this check

  • Served fastImportantPartial

    Document request latency (Est savings of 230 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 230 ms): https://liveatthriveexchange.com/
    • Network Round Trip Times (30 ms): https://liveatthriveexchange.com/
    • Server Backend Latencies (10 ms): https://liveatthriveexchange.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

  • The page does not weigh muchImportantPartial

    Reduce unused JavaScript (Est savings of 229 KiB), Reduce unused CSS (Est savings of 73 KiB), and Legacy JavaScript (Est savings of 9 KiB). Large network payloads are highly correlated with long load times and cost visitors money on mobile data.

    • Reduce unused JavaScript (Est savings of 229 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtag/js?id=G-FLK5J6Y89X&cx=c&gtm=4e6b41
    • Reduce unused CSS (Est savings of 73 KiB), from rentcafe.com: https://cdngeneralmvc.rentcafe.com/css/scss/426995/relic/relic.554345.134383511810000000.css
    • Legacy JavaScript (Est savings of 9 KiB), from Optanon: https://cdn.cookielaw.org/scripttemplates/202609.1.0/otBannerSdk.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.

    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 82 KiB) Fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 82 KiB), from Optanon: https://cdn.cookielaw.org/scripttemplates/202609.1.0/otBannerSdk.js
    • Use efficient cache lifetimes (Est savings of 82 KiB), from Clarity: https://scripts.clarity.ms/0.8.73-beta/clarity.js
    • Use efficient cache lifetimes (Est savings of 82 KiB), from Optanon: https://cdn.cookielaw.org/logos/4e85079a-4e3a-4ba5-a0ac-b85ac51e9d47/221d7757-1dc9-428d-971d-642d2cbb865a/d0529638-efff-446e-aa23-ea449b9acaa8/blank.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 page responds as soon as it appearsImportantPass

    Total Blocking Time (90 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), GoogleReport an issue with this check

  • Images are the right sizeImportantPass

    All 4 audits in this goal pass. Serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    Properly size images, ChromeReport an issue with this check

  • The page loads without errorsImportantPass

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

    Browser errors were logged to the console, 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 “affordable apartments chicago”, like 4,400 people a month.

The same rules every run: four searches, up to three sites, six pages, made-up details, and it never sends anything.

  • FoundOpened directly

    Search didn't list your site: it was not among the results of the agent's 3 searches. The agent then opened your site directly, so the gates after this one are still judged.

  • UnderstoodReached

    The agent's answer cites a fact from your site's own pages.

  • ActedNot reached

    Your site registers no tool for AI assistants, so an assistant can only send the shopper to a form, a phone number or a contact page.

    Behind it:Buttons and links say what they doYour site offers tools to AI assistants

  1. Finding the search your site already ranks for on Google.

  2. Reading your site to plan the first search.3s

  3. Reviewing the search results.2s

  4. Reviewing the search results.3s

  6. Deciding the next step.3s

  7. Reviewing the search results.17s

  8. Deciding what to do after a page that did not load.19s

  9. Judging how far it got.

What it told the shopper4 of 31 sources are your site

I found one option for affordable apartments in Chicago: Thrive Exchange, at 7905 S. Exchange Ave., Chicago, IL 60617. The searches didn't turn up other businesses' own websites, so this is the only shortlist entry.

What its website says (https://www.liveatthriveexchange.com/)

  • It describes itself as a rental community offers new affordable South Chicago apartments uniquely designed to suit your needs.
  • It is a six-story mixed-use building at the corner of 79th Street and Exchange Avenue, part of the $100 million Invest South/West initiative.
  • Apartments have vinyl plank flooring and stainless-steel appliances, including a dishwasher, microwave, and refrigerator.
  • Layouts run from practical studios to comfortable two-bedroom homes.
  • Shared amenities include a well-equipped fitness center, a comfortable resident lounge, an outdoor deck, and laundry facilities on every residential floor. The site also mentions indoor bicycle storage and on-site parking.
  • Transit: it is situated one block from the Cheltenham/79th Metra station.

Why it fits: It presents itself as an affordable South Shore rental with studio and two-bedroom options, which matches your search.

Next steps: Call +1 872-228-0060, or use the contact page at https://www.liveatthriveexchange.com/contactus. The floor plans page at https://www.liveatthriveexchange.com/floorplans is linked from the home page as the place to check availability. I did not open the floor plans page, so I can't say what those listings cost.

What the site did not say: The home page gives no rent prices, deposits, fees, or current availability. It says it offers "affordable" housing but doesn't define that, and it doesn't say whether income requirements apply. A 2026 tax credit eligibility FAQ is linked from the contact menu, which suggests some units may be income-restricted, but I haven't read it, so I can't confirm that. Ask the leasing office for current rents and income limits before you plan around this building.

These sites are competing with you

SiteLetterFindUnderstandActPerformance
liveatthriveexchange.comBuilt in ClutchAFindPassesUnderstandPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
liveatthriveexchange.comDFind100Understand100Act78Performance51
claretianassociates.orgOpened by the AI agent
habitat.comOpened by the AI agent
lincolncommonapartments.comOpened by the AI agent

See liveatthriveexchange.com rebuilt, without these issues

106th of 132 residence sites graded so far. See the board.

How we grade