clutch

D

Poor for AI agents

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

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 page responds as soon as it appears

    Total Blocking Time (870 ms)

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

    Your web team · a week or moreSee the check

  2. Partial·Performance

    The page does not jump around while it loads

    Cumulative Layout Shift is 0.22 for real visitors of your whole site, last 28 days, which Google rates needs improvement.

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

    Your web team · about a daySee the check

  3. Fail·Performance

    Repeat visitors get a faster page

    Use efficient cache lifetimes (Est savings of 417 KiB)

    What to do Let browsers keep images, scripts and styles between visits.

    Your web team · about an hourSee the check

Fix it,

or see it rebuilt

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

  • See your site rebuilt

    Clutch rebuilds vayaonaxia.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 · 8 of 9 goals pass

  • 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

  • Your pages are listed in a sitemapImportantPass

    https://www.vayaonaxia.com/sitemap.xml is a sitemap. 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.

    Build and submit a sitemap, 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

100

Understand

Can they tell who you are and what you offer?

25% of your grade · 7 of 7 goals pass

66

Act

Can they take the next step for a customer?

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

    • Elements must only use permitted ARIA attributes: <a data-dm-multisize-attr="temp" aria-label="Silhouette of person taking photo of sunset with orange and blue sky." data-dm-force-device="mobile" class="u_1430524013" data-image-url="https://irp.cdn-website.com/d4f4753c/dms3rep/multi/Hero+Image.png" style="background-image: url(&quot;https://irp.cdn-website.com/d4f4753c/dms3rep/multi/…&quot;);">: https://vayaonaxia.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://vayaonaxia.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

  • 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 "a" elements with no valid role attribute.: <a data-dm-multisize-attr="temp" aria-label="Silhouette of person taking photo of sunset with orange and blue sky." data-dm-force-device="mobile" class="u_1430524013" data-image-url="https://irp.cdn-website.com/d4f4753c/dms3rep/multi/Hero+Image.png" style="background-image: url(&quot;https://irp.cdn-website.com/d4f4753c/dms3rep/multi/…&quot;);">: https://vayaonaxia.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

  • 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 1.69 (foreground color: #fff9f9, background color: #c3c5a8, font size: 11.3pt (15px), font weight: normal). Expected contrast ratio of 4.5:1: <span class="text" id="1675411546">: https://vayaonaxia.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

  • 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 (121.5px by 19px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19px instead of at least 24px.: <a href="https://www.avenue5.com/privacy-policy" class="unifiednav__item unav-item unav-top-item" target="_blank" data-target-page-alias="https://www.avenue5.com/privacy-policy">: https://vayaonaxia.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

    All 3 audits in this goal pass. 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

  • 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

  • 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

56

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 · 2 of 10 goals pass

  • The page responds as soon as it appearsImportantFail

    Total Blocking Time (870 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 (870 ms): https://vayaonaxia.com/
    • Reduce JavaScript execution time (3.1 s), from Google CDN: https://www.gstatic.com/recaptcha/releases/bSuJ2xBC8cFy7pM4Z3Hu9boH/recaptcha__en.js
    • Minimize main-thread work (5.0 s): https://vayaonaxia.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 417 KiB) Fetching resources over the network is both slow and expensive.

    • Use efficient cache lifetimes (Est savings of 417 KiB), from Facebook: https://connect.facebook.net/signals/config/1330543551844169?v=2.9.438&r=stable&domain=www.vayaonaxia.com&im=1&hme=4453c87d489b6902031c012cadd2731893cd69feb64fe8a61b339727247a7703&ex_m=118%2C242%2C171%2C27%2C82%2C83%2C162%2C78%2C77%2C11%2C181%2C102%2C20%2C153%2C141%2C46%2C85%2C90%2C149%2C176%2C183%2C8%2C4%2C5%2C7%2C6%2C3%2C103%2C115%2C161%2C72%2C185%2C110%2C184%2C211%2C263%2C37%2C84%2C283%2C282%2C281%2C14%2C25%2C28%2C40%2C62%2C117%2C68%2C10%2C73%2C111%2C112%2C113%2C119%2C144%2C38%2C36%2C146%2C147%2C148%2C143%2C142%2C172%2C86%2C175%2C173%2C174%2C57%2C69%2C67%2C137%2C19%2C179%2C52%2C333%2C334%2C335%2C332%2C32%2C17%2C31%2C18%2C33%2C34%2C35%2C55%2C163%2C87%2C126%2C22%2C24%2C51%2C47%2C49%2C48%2C95%2C104%2C108%2C124%2C160%2C164%2C53%2C125%2C29%2C26%2C133%2C79%2C43%2C166%2C165%2C167%2C157%2C155%2C30%2C42%2C66%2C123%2C178%2C80%2C21%2C128%2C93%2C76%2C23%2C97%2C98%2C130%2C96%2C151%2C150%2C154%2C109%2C177%2C180%2C41%2C349%2C371%2C256%2C238%2C70%2C239%2C237%2C374%2C365%2C59%2C257%2C121%2C145%2C92%2C135%2C61%2C54%2C56%2C127%2C134%2C140%2C139%2C65%2C74%2C168%2C88%2C89%2C129%2C44%2C39%2C60%2C63%2C114%2C182%2C1%2C138%2C16%2C136%2C12%2C2%2C64%2C105%2C15%2C75%2C71%2C132%2C101%2C100%2C187%2C188%2C106%2C107%2C9%2C116%2C186%2C58%2C158%2C99%2C91%2C81%2C131%2C120%2C169%2C50%2C159%2C0%2C94%2C152%2C156%2C170%2C45%2C122%2C13%2C189
    • Use efficient cache lifetimes (Est savings of 417 KiB), from Facebook: https://connect.facebook.net/en_US/fbevents.js
    • Use efficient cache lifetimes (Est savings of 417 KiB), from termly.io: https://app.termly.io/resource-blocker/11473d1d-18a7-48ab-9c9e-fe276ea9c294?autoBlock=on

    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 (9.5 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 (9.5 s): https://vayaonaxia.com/
    • Render-blocking requests (Est savings of 1,710 ms), from termly.io: https://app.termly.io/resource-blocker/11473d1d-18a7-48ab-9c9e-fe276ea9c294?autoBlock=on
    • Network dependency tree: https://vayaonaxia.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 loadsImportantPartial

    Cumulative Layout Shift is 0.22 for real visitors of your whole site, last 28 days, which Google rates needs improvement. 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 is 0.22 for real visitors of your whole site, last 28 days, which Google rates needs improvement.: https://vayaonaxia.com/
    • Layout shift culprits: https://vayaonaxia.com/
    • Avoid large layout shifts (2 layout shifts found): <div class="u_1185398630 dmRespRow fullBleedChanged fullBleedMode" id="1185398630">: https://vayaonaxia.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

  • Served fastImportantPartial

    Document request latency (Est savings of 120 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 120 ms): https://vayaonaxia.com/
    • Network Round Trip Times (0 ms): https://vayaonaxia.com/
    • Server Backend Latencies (10 ms): https://vayaonaxia.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 13,458 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 13,458 KiB): <img src="https://irp.cdn-website.com/d4f4753c/dms3rep/multi/B1_transparent.png" alt="Floorplan image" data-uw-rm-alt="ALT">, from cdn-website.com: https://irp.cdn-website.com/d4f4753c/dms3rep/multi/B1_transparent.png
    • Image elements do not have explicit width and height: <img src="https://irp.cdn-website.com/d4f4753c/dms3rep/multi/B1_transparent.png" alt="Floorplan image" data-uw-rm-alt="ALT">, from cdn-website.com: https://irp.cdn-website.com/d4f4753c/dms3rep/multi/B1_transparent.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 17,721 KiB), Reduce unused JavaScript (Est savings of 1,300 KiB), Reduce unused CSS (Est savings of 89 KiB), Minify JavaScript (Est savings of 85 KiB), Minify CSS (Est savings of 7 KiB), and Legacy JavaScript (Est savings of 23 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 17,721 KiB), from cdn-website.com: https://irp.cdn-website.com/d4f4753c/dms3rep/multi/B1_transparent.png
    • Reduce unused JavaScript (Est savings of 1,300 KiB), from Google CDN: https://www.gstatic.com/recaptcha/releases/bSuJ2xBC8cFy7pM4Z3Hu9boH/recaptcha__en.js
    • Reduce unused CSS (Est savings of 89 KiB), from cdn-website.com: https://irp.cdn-website.com/d4f4753c/files/d4f4753c_withFlex_0.min.css?v=3c232006bdad40ebdac9eba9cae88b03

    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. 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://vayaonaxia.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 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 otay ranch”, like 720 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 vayaonaxia.com rebuilt, without these issues

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

How we grade