clutch

D

Poor for AI agents

Capped at D: assistants have trouble acting on your site (Act 45). Your checks earned 71.

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

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

Fix it,

or see it rebuilt

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

  • See your site rebuilt

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

64

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

  • 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>: https://parkonnapoli.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 key facts are in the page itselfCriticalPass

    The page as your server sends it holds its text; scripts add 10 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

  • 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

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

    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

45

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.

    • ARIA commands must have an accessible name: <div class="acsb-trigger acsb-widget" tabindex="0" role="button">: https://parkonnapoli.com/
    • Elements must only use permitted ARIA attributes: <div style="background-position: center bottom; background-size: cover;" class="uc-image s-module__image-background fixed" data-v-5638d9ee="" aria-label="Park on Napoli - Neighborhood, City, Condo">: https://parkonnapoli.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://parkonnapoli.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 readableImportantFail

    Background and foreground colors do not have a sufficient contrast ratio and [user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5. 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 1.94 (foreground color: #ffffff, background color: #c0b9af, font size: 13.5pt (18px), font weight: normal). Expected contrast ratio of 4.5:1: <button id="schedule-tour-popup-button" style="bottom: 0px; left: 0px; position: fixed; margin-bottom: 15px;">: https://parkonnapoli.com/
    • Fix any of the following: user-scalable=no on <meta> tag disables zooming on mobile devices: <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=2, user-scalable=no">: https://parkonnapoli.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 correctlyImportantPartial

    Elements use prohibited ARIA attributes. 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 "div" elements with no valid role attribute.: <div style="background-position: center bottom; background-size: cover;" class="uc-image s-module__image-background fixed" data-v-5638d9ee="" aria-label="Park on Napoli - Neighborhood, City, Condo">: https://parkonnapoli.com/

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

  • 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

74

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

    • Use efficient cache lifetimes (Est savings of 929 KiB), from Stripe: https://js.stripe.com/v3/
    • Use efficient cache lifetimes (Est savings of 929 KiB), from myrazz.com: https://chunks.myrazz.com/assets/static/style.BHUSrbgJ.css
    • Use efficient cache lifetimes (Est savings of 929 KiB), from myrazz.com: https://chunks.myrazz.com/assets/chunks/chunk-7WwAAsOB5T7F-_onpa.js

    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

    Largest Contentful Paint (3.5 s), First Contentful Paint (3.5 s), and Speed Index (5.3 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 (3.5 s): https://parkonnapoli.com/
    • First Contentful Paint (3.5 s): https://parkonnapoli.com/
    • Speed Index (5.3 s): https://parkonnapoli.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

  • Served fastImportantPartial

    Document request latency (Est savings of 150 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 150 ms): https://parkonnapoli.com/
    • Network Round Trip Times (10 ms): https://parkonnapoli.com/
    • Server Backend Latencies (100 ms): https://parkonnapoli.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 8 KiB) 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 8 KiB): <img id="ConciegeImage" src="https://concierge-images.s3.amazonaws.com/Allied-Orion-ParkonNapoli-Chat-B…" alt="Concierge Chatbot">, from Amazon Web Services: https://concierge-images.s3.amazonaws.com/Allied-Orion-ParkonNapoli-Chat-Box_1731690979_151124.png
    • Image elements do not have explicit width and height: <img id="ConciegeImage" src="https://concierge-images.s3.amazonaws.com/Allied-Orion-ParkonNapoli-Chat-B…" alt="Concierge Chatbot">, from Amazon Web Services: https://concierge-images.s3.amazonaws.com/Allied-Orion-ParkonNapoli-Chat-Box_1731690979_151124.png

    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 8,737 KiB), Reduce unused JavaScript (Est savings of 434 KiB), Reduce unused CSS (Est savings of 224 KiB), and Minify JavaScript (Est savings of 45 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 8,737 KiB), from myrazz.com: https://images.myrazz.com/uc-image/2a71b701-f405-42e7-b95e-44f14ea4448a/-/format/webp/-/quality/smart/dscf7068_69_70_71_72_copy.jpeg.webp
    • Reduce unused JavaScript (Est savings of 434 KiB), from Stripe: https://js.stripe.com/v3/
    • Reduce unused CSS (Est savings of 224 KiB), from myrazz.com: https://chunks.myrazz.com/assets/static/style.BHUSrbgJ.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 Uses deprecated APIs (1 warning found). 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://parkonnapoli.com/
    • Uses deprecated APIs (1 warning found): https://parkonnapoli.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

  • The page responds as soon as it appearsImportantPass

    Total Blocking Time (60 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

  • The page does not jump around while it loadsImportantPass

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

  • 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 “apartments in northwest houston”, like 480 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 parkonnapoli.com rebuilt, without these issues

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

How we grade