clutch

D

Poor for AI agents

Speed: Fail (Google's lab run of this page)

See if AI chooses you.

An AI agent searched “apartments for rent in opelika al”, like 590 people a month. Google shows

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.

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

    Your business is described in structured data

    The page has no structured data with a type.

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

  • See your site rebuilt

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

73

Understand

Can they tell who you are and what you offer?

25% of your grade · 4 of 6 goals pass

  • Your business is described in structured dataImportantFail

    The page has no structured data with a type. 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.

    • The page has no structured data with a type: https://www.thetayloratopelika.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

  • Every page has its own summary for search resultsImportantFail

    Document does not have 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.

    • Document does not have a meta description: https://thetayloratopelika.com/

    What to do Write a one or two sentence summary of every page, different on each.

    For your web team: Add <meta name="description" content="..."> to the head of every page. Write a sentence or two that are unique to that page.

    Your web team · about an hour · Important

    How to Write Meta Descriptions, 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 18 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

  • Headings give each page an outlineImportantPass

    Heading elements appear in a sequentially-descending order Headings give a page a clear structure.

    Optimizing your website for generative AI features on Google Search, 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

  • 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

39

Act

Can they take the next step for a customer?

25% of your grade · 2 of 7 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 _ngcontent-lna-c35="" apptheme="" themetype="icon" class="nbw-fab nbw-fab-open" style="background-color: rgb(225, 188, 120); color: rgb(255, 255, 255);">: https://thetayloratopelika.com/
    • Links must have discernible text: <a data-review-prev="true" href="#" class="review-prev-btn w-inline-block is-disabled">: https://thetayloratopelika.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://thetayloratopelika.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

  • 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 data-wf-domain="www.thetayloratopelika.com" data-wf-page="6932f3cddaaf35941980522b" data-wf-site="6932f3cddaaf359419805235" lang="en" class="w-mod-js w-mod-touch wf-ptsans-n4-active wf-montserrat-i9-active wf-montse…">: https://thetayloratopelika.com/

    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 4.47 (foreground color: #777777, background color: #ffffff, font size: 9.0pt (12px), font weight: normal). Expected contrast ratio of 4.5:1: <span _ngcontent-lna-c33="" class="nbw-nav-item-subtitle">: https://thetayloratopelika.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

  • 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

  • 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

55

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 (73.2 s), First Contentful Paint (3.2 s), and Speed Index (9.7 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 (73.2 s): https://thetayloratopelika.com/
    • First Contentful Paint (3.2 s): https://thetayloratopelika.com/
    • Speed Index (9.7 s): https://thetayloratopelika.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 responds as soon as it appearsImportantFail

    Total Blocking Time (1,850 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 (1,850 ms): https://thetayloratopelika.com/
    • Reduce JavaScript execution time (3.1 s): Unattributable
    • Minimize main-thread work (5.1 s): https://thetayloratopelika.com/

    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

  • Repeat visitors get a faster pageImportantFail

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

    • Use efficient cache lifetimes (Est savings of 552 KiB), from nurtureboss.io: https://widget.nurtureboss.io/widget.js
    • Use efficient cache lifetimes (Est savings of 552 KiB), from Adobe TypeKit: https://use.typekit.net/vwn0elu.js
    • Use efficient cache lifetimes (Est savings of 552 KiB), from Adobe TypeKit: https://p.typekit.net/p.gif?s=1&k=vwn0elu&ht=tk&h=www.thetayloratopelika.com&f=139.140.175.176.2005.2006.2009.2010.6958.6959.6960.6961.6962.6963.8482.8483.8484.8485.10954.13453.13454.13455.12102.12103.15665.15666.17398.17399.17400.17401.18058.18059.18060.18065.14584.14585.14586.14587.9869.9870.9871.9872.18099.18100.18101.18106.18182.18183.18184.18189.18138.18139.18140.18145.18168.18169.18170.18175.18209.18210.18211.18212.18338.18339.18340.18345.18350.18351.18352.18357.18288.18289.18290.18295.18021.18022.18023.18028.18046.18047.18048.18053.18126.18127.18128.18133.22618.22619.23548.23562.23565.23566.24539.24540.24547.24548.24735.24741.24736.24737.24742.24743.24744.24745.24746.24747.24748.24738.14032.14033.14034.14035.11315.29382.29383.29431.29432.29434.29435.39347.39348.39349.60034.60035.39488.39489.39490.39491.39492.39493.39494.39495.39496.39497.39498.39499.39500.39501.39502.39503.39504.39505.39508.39509.44426.44427.44428.44429.45065.45066.45069.45070.45079.45080.45083.45084.45402.45403.45404.45405.45406.45407.45408.45409.45410.45411.53629.59888.59889.59950.59951.59952.59953.59954.59955.59956.59957.59958.59959.59960.59961.59962.59963.59964.59965.59966.59967.59968.59969.59970.59971.59972.59973.59974.59975.59976.59977.59978.59979.59984.59986.59988.59993.59998.59999.60000.60001.60002.60003.60004.60005.60006.60007.60008.60009.60010.60011.60012.60013.60018.60019.60022.60023.60795.60798.60802.60803.60808&a=84237844&js=1.21.0&app=typekit&e=js&_=1793381997286

    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

  • Served fastImportantPartial

    Document request latency (Est savings of 180 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 180 ms): https://thetayloratopelika.com/
    • Network Round Trip Times (10 ms): https://thetayloratopelika.com/
    • Server Backend Latencies (50 ms): https://thetayloratopelika.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 384 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 384 KiB): <section class="mobile-plan-image-section">, from website-files.com: https://cdn.prod.website-files.com/6932f3cddaaf359419805235/6932f3cddaaf3594198052cd_img-home-neighborhood(1).png
    • Displays images with incorrect aspect ratio: <img src="https://cdn.prod.website-files.com/6932f3cddaaf359419805235/69373bccd6addd…" loading="lazy" width="Auto" sizes="100vw" alt="" srcset="https://cdn.prod.website-files.com/6932f3cddaaf359419805235/69373bccd6addd…" class="design-image-mobile">, from website-files.com: https://cdn.prod.website-files.com/6932f3cddaaf359419805235/69373bccd6adddc1ffa9ecea_newest-19-550x0-c-default.webp
    • Image elements do not have explicit width and height: <img src="https://cdn.prod.website-files.com/6932f3cddaaf359419805235/69373b1ba6591c…" loading="lazy" sizes="100vw" srcset="https://cdn.prod.website-files.com/6932f3cddaaf359419805235/69373b1ba6591c…" alt="" class="image-19">, from website-files.com: https://cdn.prod.website-files.com/6932f3cddaaf359419805235/69373b1ba6591c75fbf083af_23-146-The-Taylor-A3-Living-room-FINAL-24.0729-1024x0-c-default-p-800.webp

    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,465 KiB), Reduce unused JavaScript (Est savings of 544 KiB), Reduce unused CSS (Est savings of 78 KiB), and Minify CSS (Est savings of 8 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,465 KiB), from nurtureboss.io: https://widget.nurtureboss.io/widget.js
    • Reduce unused JavaScript (Est savings of 544 KiB), from Google CDN: https://www.gstatic.com/recaptcha/releases/NhfdZHzre166o-vFZrWsq3yu/recaptcha__en.js
    • Reduce unused CSS (Est savings of 78 KiB), from website-files.com: https://cdn.prod.website-files.com/6932f3cddaaf359419805235/css/thetayloratopelika.webflow.shared.7dda4f88d.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 does not jump around while it loadsImportantPass

    Cumulative Layout Shift (0.001) 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

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

Run more than one site? Grade every site in your portfolio. Talk to us

31st of 31 residence sites graded so far. See the board.

How we grade