clutch

B

Usable by AI agents, with gaps

Capped at B: your site offers assistants no tools to act with, and an A needs them. Your checks earned 90.

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

See if AI chooses you.

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

    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

  2. Partial·Performance

    The main content shows up quickly

    Largest Contentful Paint (4.5 s), First Contentful Paint (3.5 s), and Speed Index (5.6 s). Lab test on a phone: too few real visitors to measure it.

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

    Repeat visitors get a faster page

    Use efficient cache lifetimes (Est savings of 100 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 7 fixes add up to about three 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/thegrassdale-com. Tell me how to fix each issue and the level of effort each fix takes.

  • See your site rebuilt

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

100

Understand

Can they tell who you are and what you offer?

25% of your grade · 7 of 7 goals pass

86

Act

Can they take the next step for a customer?

25% of your grade · 6 of 7 goals pass

75

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

    • Use efficient cache lifetimes (Est savings of 100 KiB), from Other Google APIs/SDKs: https://lh3.googleusercontent.com/MHFynikj4N3tDq-Co-NfjRcg-NDUP-SSBDnBL9O6cWR2oivXjtIjTOb1nGrV7pYbqB4lN3VB55ifsKUcixy5aipQ9WZxUkPpaZ5gKSk=s512-rw
    • Use efficient cache lifetimes (Est savings of 100 KiB), from Other Google APIs/SDKs: https://lh3.googleusercontent.com/NbCMKk3ehfpG5-iwp2PhQgX-RTKO4DVN_1xDnv7WaUjUxLvGnuzd96qKgq9FMJyEFo8oLxTu9YZ4MtiIINuua0gL0Q68pyTfoqpKy1DQ=s512-rw
    • Use efficient cache lifetimes (Est savings of 100 KiB), from Other Google APIs/SDKs: https://lh3.googleusercontent.com/O1fkBTFPOLl4mY4rKLIsexDu4XUuef-Tgw2gpUPnhE0MqXpdr8c0r2A6XSbZHL2DjJf0ba6bKk-5O4cu2VmkugdwSBG3CN5MkSM_i7E=s512-rw

    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 (4.5 s), First Contentful Paint (3.5 s), and Speed Index (5.6 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 (4.5 s): https://thegrassdale.com/
    • First Contentful Paint (3.5 s): https://thegrassdale.com/
    • Speed Index (5.6 s): https://thegrassdale.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 90 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 90 ms): https://thegrassdale.com/
    • Network Round Trip Times (0 ms): https://thegrassdale.com/
    • Server Backend Latencies (100 ms): https://thegrassdale.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 44 KiB). Serving images larger than the version rendered on screen results in wasted bytes and slows page load.

    • Improve image delivery (Est savings of 44 KiB): <img style="background-image: url(&quot;https://lh3.googleusercontent.com/MHFynikj4N3tDq-Co…&quot;);" src="https://lh3.googleusercontent.com/MHFynikj4N3tDq-Co-NfjRcg-NDUP-SSBDnBL9O6…" alt="" loading="lazy">, from Other Google APIs/SDKs: https://lh3.googleusercontent.com/MHFynikj4N3tDq-Co-NfjRcg-NDUP-SSBDnBL9O6cWR2oivXjtIjTOb1nGrV7pYbqB4lN3VB55ifsKUcixy5aipQ9WZxUkPpaZ5gKSk=s512-rw

    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

    Reduce unused JavaScript (Est savings of 66 KiB) and Reduce unused CSS (Est savings of 50 KiB). Large network payloads are highly correlated with long load times and cost visitors money on mobile data.

    • Reduce unused JavaScript (Est savings of 66 KiB), from Google Tag Manager: https://www.googletagmanager.com/gtag/js?id=G-L42FX6307Q
    • Reduce unused CSS (Est savings of 50 KiB): https://www.thegrassdale.com/assets/css/community/version2/mobile/main.min.css?v=9-27-hot-fix-1_202610221735

    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

    Uses deprecated APIs (1 warning found). An error in the console means a problem on your page that you need to resolve.

    • Uses deprecated APIs (1 warning found): https://thegrassdale.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 (130 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.013) 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 thegrassdale.com rebuilt, without these issues.

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

4th of 31 residence sites graded so far. See the board.

How we grade