clutch

C

Hard for AI agents to use

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. Partial·Understand

    Your business is described in structured data

    The structured data lacks apartment complex and apartment on /corporate-apartments/, and gives the business no address.

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

    Your web team · about a daySee the check

Fix it,

or see it rebuilt

These 13 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/maac-com. Tell me how to fix each issue and the level of effort each fix takes.

  • See your site rebuilt

    Clutch rebuilds maac.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 · 4 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: <h4 id="heading-Modern Living">: https://www.maac.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

  • Your business is described in structured dataImportantPartial

    The structured data lacks apartment complex and apartment on /corporate-apartments/, and gives the business no address. 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.

    • Not in the page's structured data: https://www.maac.com/
    • Not in the page's structured data: https://www.maac.com/corporate-apartments/
    • No value on the business: https://www.maac.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.

    Your web team · about a day · Important

    Intro to structured data, GoogleReport an issue with this check

  • Images describe themselvesImportantPartial

    1 of the 7 images on the page has a numbered file name. 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.

    • 79327221: https://www.maac.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

    Scripts add 35 pieces of text your server does not send, and none of it is what visitors come to the page for. 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

  • 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

    The description is the page's own and reads as a summary. 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

64

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="flyout__close-btn">: https://www.maac.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://www.maac.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 (6px by 6px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 0px instead of at least 24px.: <button aria-label="Go to slide 1" aria-current="true" style="width: 6px; height: 6px; border-radius: 50%; background: rgb(0, 0, 0);">: https://www.maac.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

  • Extra labels on controls are used correctlyImportantPass

    All 11 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

  • Videos and embedded frames have textImportantPass

    <frame> or <iframe> elements have a title WCAG, the web accessibility standard most laws point to, requires captions for the audio in prerecorded video.

    Accessibility for agents, ChromeReport an issue with this check

79

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

  • Repeat visitors get a faster pageImportantFail

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

    • Use efficient cache lifetimes (Est savings of 15,944 KiB), from sitecorecloud.io: https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media/project/maac/maac_com/alabama/birmingham/properties/maa-eagle-ridge/property-gallery/10328---maa-eagle-ridge---dog-park.jpg?h=2772&iar=0&w=3840&mw=750&q=75
    • Use efficient cache lifetimes (Est savings of 15,944 KiB), from sitecorecloud.io: https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media/project/maac/maac_com/alabama/birmingham/properties/maa-eagle-ridge/property-gallery/10328---maa-eagle-ridge---pool.jpg?h=2358&iar=0&w=3840&mw=750&q=75
    • Use efficient cache lifetimes (Est savings of 15,944 KiB), from sitecorecloud.io: https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media/project/maac/maac_com/alabama/birmingham/properties/maa-eagle-ridge/property-gallery/10328---maa-eagle-ridge---tennis.jpg?h=2887&iar=0&w=3840&mw=750&q=75

    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.1 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.

    • Speed Index (10.1 s): https://www.maac.com/
    • LCP request discovery: https://www.maac.com/
    • LCP breakdown: https://www.maac.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

  • Images are the right sizeImportantPartial

    Improve image delivery (Est savings of 8,480 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 8,480 KiB): <img alt="Pool at MAA Eagle Ridge luxury apartment homes in Birmingham, AL" loading="lazy" width="350" height="236" decoding="async" data-nimg="1" srcset="https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media…" src="https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media…" style="color: transparent;">, from sitecorecloud.io: https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media/project/maac/maac_com/alabama/birmingham/properties/maa-eagle-ridge/property-gallery/10328---maa-eagle-ridge---pool.jpg?h=2358&iar=0&w=3840&mw=750&q=75
    • Displays images with incorrect aspect ratio: <img alt="pool deck" loading="lazy" width="550" height="348" decoding="async" data-nimg="1" style="color:transparent" srcset="https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media…" src="https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media…">, from sitecorecloud.io: https://edge.sitecorecloud.io/midamericaa7861-test603e-prod9e24-2f78/media/project/maac/maac_com/home-page/search_hero/79327221.jpg?h=744&iar=0&w=851&mw=1200&q=75

    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 34,252 KiB), Reduce unused JavaScript (Est savings of 1,460 KiB), Reduce unused CSS (Est savings of 157 KiB), and Legacy JavaScript (Est savings of 91 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 34,252 KiB), from Cloudinary: https://res.cloudinary.com/maa/video/upload/q_auto/v1/maac/-/media/redesign/videos/adobestock_70653253.mov
    • Reduce unused JavaScript (Est savings of 1,460 KiB): https://www.maac.com/_next/static/chunks/0015wgli2f3hc.js?dpl=dpl_7CAxutuBQ4FvuoFnC6guLntNz3CM
    • Reduce unused CSS (Est savings of 157 KiB): https://www.maac.com/_next/static/chunks/2yghyz3m3k-gg.css?dpl=dpl_7CAxutuBQ4FvuoFnC6guLntNz3CM

    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 Missing source maps for large first-party JavaScript. An error in the console means a problem on your page that you need to resolve.

    • requestStorageAccess: Permission denied.: https://www.maac.com/
    • Missing source maps for large first-party JavaScript: https://www.maac.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

  • Visitors are not interrupted on arrivalImportantPartial

    Requests the geolocation permission on page load. 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: https://www.maac.com/

    What to do Ask for permissions only after a visitor does something that needs them.

    For your web team: Request geolocation and notification permission from a click handler, and remove paste handlers that block input.

    Your web team · about an hour · Important

    Requests the geolocation permission on page load, ChromeReport an issue with this check

  • The page responds as soon as it appearsImportantPass

    Interaction to Next Paint is 179 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

  • Served fastImportantPass

    All 5 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

See if AI chooses you

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 maac.com rebuilt, without these issues