clutch

C

Hard for AI agents to use

Capped at C: assistants can't read your page's controls. Your checks earned 82.

Speed: Fail (real visitors, last 28 days)

See if AI chooses you.

An AI agent searched “apartments for rent west los angeles”, 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·Performance

    The main content shows up quickly

    Largest Contentful Paint is 5.5 s for real visitors of this page, last 28 days, which Google rates poor, First Contentful Paint is 3.0 s for real visitors of this page, last 28 days, which Google rates poor, and Speed Index (8.8 s). Measured from real visitors of this page, last 28 days; the rest is a lab test on a phone.

    What to do Make the first screen load faster on phones, starting with its biggest image.

    Your web team · a week or moreSee the check

  3. Fail·Act

    Your site offers tools to AI assistants

    Your home page offers no tools to AI assistants.

    What to do Expose the main action on your site, such as booking or contacting you, as a WebMCP tool.

    Your web team · about a daySee the check

Fix it,

or see it rebuilt.

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

  • See your site rebuilt

    Clutch rebuilds liveatwestedge.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
94

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.liveatwestedge.com/sitemaps-1-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

61

Act

Can they take the next step for a customer?

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

    • Links must have discernible text: <a href="/">: https://www.liveatwestedge.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.liveatwestedge.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 readableImportantPartial

    [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: user-scalable on <meta> tag disables zooming on mobile devices: <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=0', …">: https://www.liveatwestedge.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

  • Custom controls announce what they areImportantPass

    Elements with role="dialog" or role="alertdialog" 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.

    Accessibility for agents, ChromeReport 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

    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

72

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

  • The main content shows up quicklyImportantFail

    Largest Contentful Paint is 5.5 s for real visitors of this page, last 28 days, which Google rates poor, First Contentful Paint is 3.0 s for real visitors of this page, last 28 days, which Google rates poor, and Speed Index (8.8 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.

    • Largest Contentful Paint is 5.5 s for real visitors of this page, last 28 days, which Google rates poor.: https://www.liveatwestedge.com/
    • First Contentful Paint is 3.0 s for real visitors of this page, last 28 days, which Google rates poor.: https://www.liveatwestedge.com/
    • Speed Index (8.8 s): https://www.liveatwestedge.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

  • Repeat visitors get a faster pageImportantFail

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

    • Use efficient cache lifetimes (Est savings of 3,010 KiB): https://www.liveatwestedge.com/uploads/home_banner_2023-12-19-131758_mgxj.jpg
    • Use efficient cache lifetimes (Est savings of 3,010 KiB): https://www.liveatwestedge.com/uploads/home_banner.jpg
    • Use efficient cache lifetimes (Est savings of 3,010 KiB): https://www.liveatwestedge.com/uploads/TheResidences_WestEdge_PHKitchen.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

  • Images are the right sizeImportantPartial

    Improve image delivery (Est savings of 1,766 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 1,766 KiB): <img class="lg:hidden object-cover w-full h-full" srcset="https://www.liveatwestedge.com/uploads/TheResidences_WestEdge_PHKitchen.jpg" src="https://www.liveatwestedge.com/uploads/TheResidences_WestEdge_PHKitchen.jpg" alt="The Residences West Edge PH Kitchen">: https://www.liveatwestedge.com/uploads/TheResidences_WestEdge_PHKitchen.jpg
    • Image elements do not have explicit width and height: <img src="https://www.liveatwestedge.com/uploads/AM_23-WebBadge-2.png" alt="AM 23 Web Badge 2" class="awards_logo block ml-3 lg:ml-8 max-h-[34px] lg:max-h-[40px]">: https://www.liveatwestedge.com/uploads/AM_23-WebBadge-2.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 4,032 KiB), Reduce unused JavaScript (Est savings of 566 KiB), Reduce unused CSS (Est savings of 29 KiB), Minify JavaScript (Est savings of 24 KiB), and Legacy JavaScript (Est savings of 28 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 4,032 KiB): https://www.liveatwestedge.com/uploads/home_banner_2023-12-19-131758_mgxj.jpg
    • Reduce unused JavaScript (Est savings of 566 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtm.js?id=GTM-N79T5JW
    • Reduce unused CSS (Est savings of 29 KiB): https://www.liveatwestedge.com/build/css/app.css?id=85d01c1cfeecd5eb31880d3a90b9788d

    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.

    • Failed to load resource: the server responded with a status of 404 (Not Found): https://www.liveatwestedge.com/
    • Missing source maps for large first-party JavaScript: https://www.liveatwestedge.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

    Interaction to Next Paint is 114 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.02 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 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 liveatwestedge.com rebuilt, without these issues.

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

17th of 34 residence sites graded so far. See the board.

How we grade