clutch

D

Poor for AI agents

Capped at D: assistants have trouble acting on your site (Act 45). 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·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·Act

    Custom controls announce what they are

    Elements with role="dialog" or role="alertdialog" do not have accessible names.

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

    Your web team · a few daysSee the check

Fix it,

or see it rebuilt

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

  • See your site rebuilt

    Clutch rebuilds mark-taylor.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
89

Find

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

25% of your grade · 7 of 9 goals pass

  • Your pages are listed in a sitemapImportantPartial

    https://www.mark-taylor.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://www.mark-taylor.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

  • Pages that do not exist say soImportantPass

    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, 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

85

Understand

Can they tell who you are and what you offer?

25% of your grade · 6 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 class="card-title fv-numeric">: https://www.mark-taylor.com/apartments/az/phoenix/niro/
    • Fix any of the following: Heading order invalid: <h4 class="ff-serif fw-semibold fv-numeric fs-24 fs-lg-32 mb-16 w-75">: https://www.mark-taylor.com/apartments/az/phoenix/niro/

    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 key facts are in the page itselfCriticalPass

    The page as your server sends it holds its text; scripts add 138 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 GeoCoordinates, ApartmentComplex, PostalAddress, LocationFeatureSpecification, FloorPlan, QuantitativeValue, and OpeningHoursSpecification. 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

  • Images describe themselvesImportantPass

    Image elements 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.

    Image SEO Best Practices, 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

45

Act

Can they take the next step for a customer?

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

    • ARIA dialog and alertdialog nodes should have an accessible name: <div role="dialog" aria-live="polite" style="position: fixed; bottom: 16px; left: 16px; right: 16px; z-index: 1100;">: https://www.mark-taylor.com/apartments/az/phoenix/niro/
    • Links must have discernible text: <a id="headerLinkMenu" class="header-link-menu" href="/apartments/az/phoenix/niro/">: https://www.mark-taylor.com/apartments/az/phoenix/niro/
    • Select element must have an accessible name: <select class="floor-plan-filter-select">: https://www.mark-taylor.com/apartments/az/phoenix/niro/

    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

  • Custom controls announce what they areImportantFail

    Elements with role="dialog" or role="alertdialog" 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 role="dialog" aria-live="polite" style="position: fixed; bottom: 16px; left: 16px; right: 16px; z-index: 1100;">: https://www.mark-taylor.com/apartments/az/phoenix/niro/

    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

  • 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.mark-taylor.com/apartments/az/phoenix/niro/

    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

  • Forms are labelledCriticalPartial

    Select elements do not have associated label elements. WCAG requires every form field to have a label or instructions, and the axe rule label checks for it.

    • Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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": <select class="floor-plan-filter-select">: https://www.mark-taylor.com/apartments/az/phoenix/niro/

    What to do Put a visible label on every field in your booking, contact and order forms.

    For your web team: Associate each input and select with one label element through for and id, and use valid autocomplete values on fields for names, addresses and payment details.

    Your web team · about a day · Critical

    Rule label: Form elements must have labels, Deque axeReport 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.86 (foreground color: #96999d, background color: #ffffff, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1: <span class="mb-0 floor-plan-filter-clear">: https://www.mark-taylor.com/apartments/az/phoenix/niro/

    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

  • 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

    Document has a main landmark. 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

80

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

    Speed Index (6.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 (6.8 s): https://www.mark-taylor.com/apartments/az/phoenix/niro/
    • Render-blocking requests (Est savings of 590 ms): https://www.mark-taylor.com/static/css/all.bd2a707bf14a32a3e4c8.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

  • The page responds as soon as it appearsImportantPartial

    Interaction to Next Paint is 262 ms for real visitors of your whole site, last 28 days, which Google rates needs improvement. 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.

    • Interaction to Next Paint is 262 ms for real visitors of your whole site, last 28 days, which Google rates needs improvement.: https://www.mark-taylor.com/apartments/az/phoenix/niro/
    • Minimize main-thread work (2.7 s): https://www.mark-taylor.com/apartments/az/phoenix/niro/
    • Forced reflow: https://www.mark-taylor.com/apartments/az/phoenix/niro/

    What to do Remove scripts it does not need, which keep the page busy.

    For your web team: Split long tasks and defer scripts that are not needed to start. PageSpeed lists the costliest scripts.

    Your web team · a week or more · Important

    Total Blocking Time (TBT), GoogleReport an issue with this check

  • Images are the right sizeImportantPartial

    Improve image delivery (Est savings of 29,368 KiB). Serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 29,368 KiB): <img src="https://crm-production-1.s3.amazonaws.com/corporate/niro/image/2026-09-02/…" class="figure-img img-fluid" alt="Prime Location" loading="lazy" style="width:100%;height:100%;object-fit:cover">, from Amazon Web Services: https://crm-production-1.s3.amazonaws.com/corporate/niro/image/2026-09-02/1788369051_iStock-1009759582.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 85,931 KiB), Reduce unused JavaScript (Est savings of 916 KiB), Reduce unused CSS (Est savings of 165 KiB), Minify CSS (Est savings of 17 KiB), and Legacy JavaScript (Est savings of 24 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 85,931 KiB), from Amazon Web Services: https://crm-production-1.s3.amazonaws.com/corporate/niro/image/2026-09-02/1788369051_iStock-1009759582.jpg
    • Reduce unused JavaScript (Est savings of 916 KiB), from gounion.com: https://my.gounion.com/api/v1/load_dwelljs/dwell.js?client_id=29a92641fdb13eb24d231210ec7ed6cd&source=subsite
    • Reduce unused CSS (Est savings of 165 KiB): https://www.mark-taylor.com/static/css/all.bd2a707bf14a32a3e4c8.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 76,932 KiB) Fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 76,932 KiB), from Amazon Web Services: https://crm-production-1.s3.amazonaws.com/corporate/niro/image/2026-09-02/1788369051_iStock-1009759582.jpg
    • Use efficient cache lifetimes (Est savings of 76,932 KiB), from Amazon Web Services: https://crm-production-1.s3.amazonaws.com/corporate/niro/image/2026-09-02/1788369507_iStock-881521012.jpg
    • Use efficient cache lifetimes (Est savings of 76,932 KiB), from Azure Web Services: https://resman.blob.core.windows.net/mt0-public/7de39ecb-1ae2-43aa-8e02-4d2a98b6bc74.jpg

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

    • Failed to load resource: the server responded with a status of 404 (Not Found): https://www.mark-taylor.com/apartments/az/phoenix/niro/
    • Missing source maps for large first-party JavaScript: https://www.mark-taylor.com/apartments/az/phoenix/niro/

    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 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 “new apartments in phoenix az”, like 320 people a month.

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

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

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

  3. Reviewing the search results.4s

  6. Deciding the next step.10s

  7. Deciding the next step.5s

  8. Judging how far it got.

What it told the shopper2 of 12 sources are your site

I found one apartment company to check for new apartments in Phoenix: Mark-Taylor. I could not confirm that it has any new Phoenix apartments available right now.

Mark-Taylor (https://www.mark-taylor.com/)

  • What its site says: Established in 1985, Mark-Taylor Companies is the region's only privately held developer, owner, and investment manager of multifamily communities. The homepage lists Phoenix among the cities where it has communities, and it also lists Avondale, Chandler, Gilbert, Glendale, Mesa, Scottsdale, Tempe and others.
  • Why I picked it: It is a Phoenix-area rental company with a Phoenix listing. It is also a developer as well as an owner, so it may have newer properties. The site does not say which of its communities are new, so that part is unconfirmed.
  • Amenities on the homepage: The site highlights features such as a Resort-Style Pool, a Fitness Center, Washer & Dryer connections, and Private Balcony options. It also describes an app that gives easy access to rental payments, the community marketplace, service requests, fitness class reservations, social feeds and more.
  • How to take the next step: Go to the "Find Your Home" page at https://www.mark-taylor.com/find-your-home/, which has search, filter and map options for rent range and bedrooms. Or call (480) 991-9111, the number on the site. The listings did not load when I checked, so I could not see any Phoenix units, prices or move-in dates.
  • What the site did not say: It did not list specific new Phoenix buildings, current availability, rent prices, lease terms, or move-in dates. The map showed "0 Results" when I opened it, so I could not check what is open now.

Because I could only check this one company, I have no comparison with other Phoenix landlords. Calling the office or using the filters on the Find Your Home page will tell you what is available now.

  • Your sitemark-taylor.com/

    The assistant quoted your home page:

    Established in 1985, Mark-Taylor Companies is the region's only privately held developer, owner, and investment manager of multifamily communities.
    Resort-Style PoolResort-Style PoolClubhouse
  • Your sitemark-taylor.com/find-your-home

These sites are competing with you

SiteLetterFindUnderstandActPerformance
mark-taylor.comBuilt in ClutchAFindPassesUnderstandPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
mark-taylor.comDFind89Understand85Act45Performance80
lumaraphoenix.comOpened by the AI agent
rainbowroadphx.comOpened by the AI agent
gardencommunitiesca.comOpened by the AI agent

See mark-taylor.com rebuilt, without these issues

112th of 134 residence sites graded so far. See the board.

How we grade