D

Poor for AI agents

AI agents can't see your site's buttons and fields.

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

    AI agents can see your site's buttons and fields (accessibility tree)

    Accessibility tree is not well-formed

    What to do Fix the accessibility problems Google's PageSpeed Insights lists for your home page, which are mostly buttons and fields with no label.

    Your web team · about a daySee the check

  2. Fail·Read

    Headings give each page a clear 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

  3. Partial·Performance

    Your main content shows up quickly on phones

    Largest Contentful Paint (7.1 s). First Contentful Paint (2.1 s). Speed Index (5.9 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

100

Find

Can AI agents and search engines get to your site and list its pages? If they can't find you, you're not in the conversation, and someone else gets recommended.

25% of your grade · 10 of 10 goals pass

71

Read

Can agents quickly work out who you are and what you offer? An agent only spends so much effort on one site. If yours is hard to read, it moves on and recommends one that's easier.

25% of your grade · 7 of 11 goals pass

  • Headings give each page a clear outlineImportantFail

    Clear headings show search engines and agents how a page is laid out, so they find the part that answers a question, such as your opening hours. Google's guide to its AI features recommends them.

    What we found: Heading elements are not in a sequentially-descending order

    • Fix any of the following: Heading order invalid: <h4 data-upcart-chunk="header-title-content">

    How to fix it

    Give each page one main heading and put the headings under it in order.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Headings give each page a clear outline What the grader found: Heading elements are not in a sequentially-descending order Details: - Fix any of the following: Heading order invalid: <h4 data-upcart-chunk="header-title-content"> The fix, for a developer: Use h1 once, then h2 to h6 without skipping a level, and remove or fill any heading element that has no text. Source: Optimizing your website for generative AI features on Google Search, Google: https://developers.google.com/search/docs/fundamentals/ai-optimization-guide; Understanding Success Criterion 1.3.1: Info and Relationships, W3C: https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about an hour
  • Your site tells AI agents everything they can do with it, in one place (ARD catalog)ImportantFail

    Agents read the catalog before they open a page, so they know straight away which of your services they can use, such as your MCP server. Lighthouse checks it, and the grade counts standards likely to be adopted, such as this draft.

    What we found: Google's Lighthouse found no ARD catalog at /.well-known/ard.json.

    How to fix it

    Publish an ARD catalog that lists every tool and service agents can use, such as your MCP server.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site tells AI agents everything they can do with it, in one place (ARD catalog) What the grader found: Google's Lighthouse found no ARD catalog at /.well-known/ard.json. The fix, for a developer: Serve JSON at /.well-known/ard.json with an entries list that follows the ARD schema: each entry has a urn:air: identifier, a displayName, a type and a url. An MCP server's entry has the type application/mcp-server-card+json and points at its server card, at /mcp/server-card. Link it from every page with <link rel="ard" href="/.well-known/ard.json">. Lighthouse warns about a catalog found only at the older /.well-known/ai-catalog.json. Source: Lighthouse agentic browsing scoring, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/scoring; Agentic Resource Discovery specification, agenticresourcediscovery.org: https://agenticresourcediscovery.org/spec/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about a day
  • Your site sends AI agents a plain-text version of each page (Markdown)ImportantFail

    Agents read Markdown faster and more accurately than a full web page, and it costs them fewer tokens, the units AI services count text in. Cloudflare calls Markdown the common language of agents.

    What we found: Cloudflare's scan asked your home page for Markdown and got none back.

    • Site does not support Markdown for Agents

    How to fix it

    Send each page as Markdown to agents that ask for it.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site sends AI agents a plain-text version of each page (Markdown) What the grader found: Cloudflare's scan asked your home page for Markdown and got none back. Details: - Site does not support Markdown for Agents The fix, for a developer: Answer a request whose Accept header names text/markdown with the page's content as Markdown and Content-Type: text/markdown. Cloudflare can convert pages at its edge, or the server can render the Markdown itself. Source: Markdown for Agents, Cloudflare: https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about a day
  • Your site says how AI may use its content (Content Signals)ImportantFail

    Content Signals let you say, in one line, whether AI may use your content for answers, for training, or both. They follow AI Preferences, a proposal at the IETF, the body that sets internet standards.

    What we found: Cloudflare found no Content-Signal line in your robots.txt.

    • No Content Signals found in robots.txt

    How to fix it

    Decide whether your content may be used for search, AI answers and AI training, and ask the people who run your site to say so in robots.txt.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site says how AI may use its content (Content Signals) What the grader found: Cloudflare found no Content-Signal line in your robots.txt. Details: - No Content Signals found in robots.txt The fix, for a developer: Add a Content-Signal line to robots.txt under the user agents it covers, such as Content-Signal: search=yes, ai-input=yes, ai-train=no. Source: Content Signals, Content Signals: https://contentsignals.org/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about an hour
  • AI agents can read your text without running scriptsCriticalPass

    Many agents read only the page your server sends and run none of its scripts. If your text appears only after scripts run, those agents see an empty page and answer from other sites. Claude's web fetch is one of them.

  • Your site tells AI agents what your business is (structured data)ImportantPass

    Structured data saves agents and search engines from guessing your type of business and contact details from the page. Google says it gives explicit clues about what a page means. Bing says it may help and promises nothing.

  • AI agents can tell what your images show (alt text)ImportantPass

    Agents rely on an image's text description, called alt text, to know what it shows, the same description that lets people who cannot see the image use the page. Google calls alt text the most important attribute for describing an image.

  • Your lists and tables are built so agents can read themImportantPass

    Agents read a list or a table as one only when the page's code marks it as one. Otherwise your prices or opening hours reach them as loose lines. The same code lets people who use screen readers follow them, and WCAG requires it.

  • Your site has a short guide for AI agents (llms.txt)ImportantPass

    llms.txt gives agents a short map of your site, so they reach your key pages without reading every one. Lighthouse checks it as an emerging convention, and the grade counts standards likely to be adopted.

  • Every page has a summary for search resultsImportantPass

    Google may show your summary under the page's title in its results, and asks for a different one on every page. Without one, it picks a snippet from the page, which may be a line you would never choose.

  • Your pages say which language they are inImportantPass

    A declared language tells software how to read your page, from the voice a screen reader uses to the language a translation starts from. WCAG, the accessibility standard most laws point to, requires it.

63

Act

Can agents do what a customer asks, such as book, reserve, enquire or search? When someone asks an agent to act for them and your site doesn't let it, the agent acts on a site that does.

25% of your grade · 5 of 12 goals pass

  • AI agents can see your site's buttons and fields (accessibility tree)CriticalFail

    Agents find what they can click or fill in through the accessibility tree, the browser's list of a page's controls. A control missing from it does not exist for an agent, so it cannot book, buy or send an enquiry. Screen readers use the same tree.

    What we found: Accessibility tree is not well-formed

    • Links must have discernible text: <a href="/collections/trades-construction-first-aid-kits">

    How to fix it

    Fix the accessibility problems Google's PageSpeed Insights lists for your home page, which are mostly buttons and fields with no label.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can see your site's buttons and fields (accessibility tree) What the grader found: Accessibility tree is not well-formed Details: - Links must have discernible text: <a href="/collections/trades-construction-first-aid-kits"> The fix, for a developer: 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. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about a day
  • AI agents can complete tasks without visiting your site (MCP server)ImportantFail

    Some agents never open a web page. They connect to a business directly and work from there. Giving them a way in means your site can be searched and booked by those agents too.

    What we found: Your site has no ARD catalog at /.well-known/ard.json, where agents look for an MCP server.

    • /.well-known/ard.json answers 404

    How to fix it

    Give agents a way to do every task a customer can do on your site without visiting it: an MCP server, listed in the site's ARD catalog.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can complete tasks without visiting your site (MCP server) What the grader found: Your site has no ARD catalog at /.well-known/ard.json, where agents look for an MCP server. Details: - /.well-known/ard.json answers 404 The fix, for a developer: Serve the MCP server card at /mcp/server-card, as the server card extension places it, and list it in /.well-known/ard.json as an entry with a urn:air: identifier, a displayName, the type application/mcp-server-card+json and the card's URL. Source: SEP-2127: MCP Server Cards, Model Context Protocol: https://modelcontextprotocol.io/seps/2127-mcp-server-cards; Agentic Resource Discovery specification, agenticresourcediscovery.org: https://agenticresourcediscovery.org/spec/ Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · a few days
  • Videos and embedded content have text AI agents can readImportantFail

    An agent cannot watch a video or see inside embedded content. Captions and titles tell it what is there, such as directions in a map or a booking form from another service, as they do for people who are deaf or blind.

    What we found: <frame> or <iframe> elements do not have a title

    • Fix any of the following: Element has no title attribute aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element's default semantics were not overridden with role="none" or role="presentation": <iframe id="merchantwidgetiframe" allowtransparency="true" frameborder="0" scrolling="no" sandbox="allow-same-origin allow-scripts allow-forms allow-popups allow-popups-to-e…" src="https://www.google.com/shopping/merchantverse/?screenWidth=412&amp;screenHeigh…" style="position: absolute; height: 733px; width: 416px; z-index: 2147483647;">

    How to fix it

    Add captions to your videos and a title to every embedded map, form and player.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Videos and embedded content have text AI agents can read What the grader found: <frame> or <iframe> elements do not have a title The fix, for a developer: Add a captions track to each video and a title attribute to each iframe and frame. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents; Understanding Success Criterion 1.2.2: Captions (Prerecorded), W3C: https://www.w3.org/WAI/WCAG22/Understanding/captions-prerecorded.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · a few days
  • Your site tells AI agents about its other servicesImportantFail

    Each one tells agents about a service they can use, such as an API for checking stock. An agent that finds them can do more for your customers without a visit to your site.

    What we found: Your home page sends no Link headers that point agents to these files. Your site has no API catalog. Your site has no Agent Skills index. Your site has no A2A agent card.

    • Link headers present but no agent-useful relation types found
    • API Catalog not found
    • Agent Skills index not found

    How to fix it

    Ask the people who run your site which of these fit your business, such as an API catalog if you offer an API.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site tells AI agents about its other services What the grader found: Your home page sends no Link headers that point agents to these files. Your site has no API catalog. Your site has no Agent Skills index. Your site has no A2A agent card. Details: - Link headers present but no agent-useful relation types found - API Catalog not found - Agent Skills index not found The fix, for a developer: Publish the files that fit: an API catalog at /.well-known/api-catalog, an Agent Skills index, an A2A agent card at /.well-known/agent-card.json, and Link headers on the home page that point to them. Source: RFC 8288, Web Linking, IETF: https://www.rfc-editor.org/rfc/rfc8288; RFC 9727, api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs, IETF: https://www.rfc-editor.org/rfc/rfc9727 Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about a day
  • Your text stands out clearly from its backgroundImportantPartial

    Some agents look at a page as a picture, as people do, and pale text is easy for both to miss. The same contrast lets people with low vision read it. WCAG, the accessibility standard most laws point to, sets how much contrast text needs.

    What we found: Background and foreground colors do not have a sufficient contrast ratio.

    • Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #269267, background color: #faf8f6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1: <a href="/collections" id="ViewAll-template--22280255242275__collection_list_jYeRjK" class="link underlined-link large-up-hide scroll-trigger animate--slide-in" aria-labelledby="ViewAll-template--22280255242275__collection_list_jYeRjK SectionHeading-te…">

    How to fix it

    Darken pale text, underline links inside paragraphs and let visitors zoom.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your text stands out clearly from its background What the grader found: Background and foreground colors do not have a sufficient contrast ratio. Details: - Fix any of the following: Element has insufficient color contrast of 3.67 (foreground color: #269267, background color: #faf8f6, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1: <a href="/collections" id="ViewAll-template--22280255242275__collection_list_jYeRjK" class="link underlined-link large-up-hide scroll-trigger animate--slide-in" aria-labelledby="ViewAll-template--22280255242275__collection_list_jYeRjK SectionHeading-te…"> The fix, for a developer: 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. Source: Rule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe: https://dequeuniversity.com/rules/axe/4.13/color-contrast; Understanding Success Criterion 1.4.3: Contrast (Minimum), W3C: https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about a day
  • Buttons and links are big enough for an agent to clickImportantPartial

    Agents that click where a button sits, as a person does, miss small or crowded targets, and so do people on phones and people with limited movement. Google's web.dev recommends targets of about 48 pixels, and WCAG sets a minimum of 24.

    What we found: Touch targets do not have sufficient size or spacing.

    • Fix any of the following: Target has insufficient size because it is partially obscured (smallest space is 14px by 81.8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.: <div tabindex="0" role="button" aria-label="Review image" class="go4139199820 reputon-small-images-container">

    How to fix it

    Make small buttons and tightly packed links bigger on phones.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Buttons and links are big enough for an agent to click What the grader found: Touch targets do not have sufficient size or spacing. Details: - Fix any of the following: Target has insufficient size because it is partially obscured (smallest space is 14px by 81.8px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 4px instead of at least 24px.: <div tabindex="0" role="button" aria-label="Review image" class="go4139199820 reputon-small-images-container"> The fix, for a developer: 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. Source: Accessible tap targets, Google: https://web.dev/articles/accessible-tap-targets; Understanding Success Criterion 2.5.8: Target Size (Minimum), W3C: https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about an hour
  • AI agents can tell what every form field asks forCriticalPass

    An agent fills in a form by reading each field's label. Without one it is left guessing, so the enquiry or booking is never sent. Labels serve people who use screen readers the same way, and Chrome says missing ones can block agents.

  • AI agents can tell what custom controls are, such as date pickersImportantPass

    A custom date picker or slider is invisible to an agent unless its code gives it a name, so the agent cannot choose a date or set a price range. The same name tells people who use screen readers what the control is.

  • Hidden labels on your buttons and fields are accurate (ARIA)ImportantPass

    Agents trust these labels. A wrong one tells an agent a control is something it is not, such as a button marked as a heading, so it clicks the wrong thing or nothing. Screen readers trust them too, so people with disabilities are misled the same way.

  • AI agents can move around your pages without a mouseImportantPass

    Agents move through a page from control to control, as keyboard users do. A page that skips controls or refreshes on its own keeps them from the button they need. WCAG requires every function to work from a keyboard, which people with disabilities rely on.

  • AI agents can complete tasks when they visit your site (WebMCP)ImportantPass

    Your site can tell agents what it lets a customer do, for example book a tour, reserve a table, ask a question, or search what's available. An agent can then do it for them, start to finish. Without that, the agent can only read your pages and send the customer to do it themselves, or do it on another site that lets it.

71

Performance

Does your site answer fast? Agents work against the clock, and so do people. A slow site costs them time, and they give that time to a faster one.

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

  • Return visits load fasterImportantFail

    Downloading every file again on each visit is slow and costly. When browsers keep the files, returning visitors see your page sooner.

    What we found: Use efficient cache lifetimes (Est savings of 255 KiB)

    • Use efficient cache lifetimes (Est savings of 255 KiB), from squarecdn.com
    • Use efficient cache lifetimes (Est savings of 255 KiB), from Google CDN
    • Use efficient cache lifetimes (Est savings of 255 KiB), from gotolstoy.com

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Return visits load faster What the grader found: Use efficient cache lifetimes (Est savings of 255 KiB) Details: - Use efficient cache lifetimes (Est savings of 255 KiB), from squarecdn.com - Use efficient cache lifetimes (Est savings of 255 KiB), from Google CDN - Use efficient cache lifetimes (Est savings of 255 KiB), from gotolstoy.com The fix, for a developer: Send Cache-Control with a long max-age for fingerprinted static files, and revalidate the rest with ETag. Source: Prevent unnecessary network requests with the HTTP Cache, Google: https://web.dev/articles/http-cache Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about an hour
  • Your main content shows up quickly on phonesImportantPartial

    Visitors leave pages that are slow to show anything, and Google uses this speed in ranking. It is called Largest Contentful Paint, one of Google's three Core Web Vitals.

    What we found: Largest Contentful Paint (7.1 s). First Contentful Paint (2.1 s). Speed Index (5.9 s). Lab test on a phone: too few real visitors to measure it.

    • Render-blocking requests
    • Network dependency tree

    How to fix it

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

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your main content shows up quickly on phones What the grader found: Largest Contentful Paint (7.1 s). First Contentful Paint (2.1 s). Speed Index (5.9 s). Lab test on a phone: too few real visitors to measure it. Details: - Render-blocking requests - Network dependency tree The fix, for a developer: Serve the largest element early: preload it, avoid render-blocking scripts and styles, and cut server response time. PageSpeed lists what holds it back. Source: Web Vitals, Google: https://web.dev/articles/vitals; Largest Contentful Paint (LCP), Google: https://web.dev/articles/lcp Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · a week or more
  • Your site responds quickly to taps and clicksImportantPartial

    A page that freezes after a tap feels broken, so visitors tap again or leave. Google rates a reaction under 200 milliseconds as good and counts it among its Core Web Vitals.

    What we found: Total Blocking Time (590 ms)

    • Reduce JavaScript execution time (2.0 s)
    • Minimize main-thread work (5.8 s)
    • Forced reflow

    How to fix it

    Remove scripts the page does not need, since they keep it busy.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your site responds quickly to taps and clicks What the grader found: Total Blocking Time (590 ms) Details: - Reduce JavaScript execution time (2.0 s) - Minimize main-thread work (5.8 s) - Forced reflow The fix, for a developer: Split long tasks and defer scripts that are not needed to start. PageSpeed lists the costliest scripts. Source: Total Blocking Time (TBT), Google: https://web.dev/articles/tbt; Lighthouse performance scoring, Chrome: https://developer.chrome.com/docs/lighthouse/performance/performance-scoring Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · a week or more
  • Images are sent at the size they are shownImportantPartial

    An image bigger than the space it fills wastes data and slows the page, most of all on a phone connection. Smaller images mean a faster page for every visitor.

    What we found: Improve image delivery (Est savings of 720 KiB).

    • Improve image delivery (Est savings of 720 KiB): <img srcset="//assurancefirstaidkits.com.au/cdn/shop/collections/car-first-aid-kits-aus…" src="/cdn/shop/collections/car-first-aid-ki…" sizes=" (min-width: 1200px) 366px, (min-width: 75…" alt="" height="1080" width="1080" loading="lazy" class="motion-reduce">

    How to fix it

    Resize and compress your images before they go on the page.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Images are sent at the size they are shown What the grader found: Improve image delivery (Est savings of 720 KiB). Details: - Improve image delivery (Est savings of 720 KiB): <img srcset="//assurancefirstaidkits.com.au/cdn/shop/collections/car-first-aid-kits-aus…" src="/cdn/shop/collections/car-first-aid-ki…" sizes=" (min-width: 1200px) 366px, (min-width: 75…" alt="" height="1080" width="1080" loading="lazy" class="motion-reduce"> The fix, for a developer: 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. Source: Properly size images, Chrome: https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · about a day
  • Your pages are light to downloadImportantPartial

    Heavy pages take longer to load and cost visitors on mobile data real money. Chrome says large downloads are closely tied to long load times.

    What we found: Avoid enormous network payloads (Total size was 5,827 KiB). Reduce unused JavaScript (Est savings of 847 KiB). Reduce unused CSS (Est savings of 45 KiB). Legacy JavaScript (Est savings of 39 KiB).

    • Avoid enormous network payloads (Total size was 5,827 KiB), from Shopify
    • Reduce unused JavaScript (Est savings of 847 KiB), from Shopify
    • Reduce unused CSS (Est savings of 45 KiB), from Shopify

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages are light to download What the grader found: Avoid enormous network payloads (Total size was 5,827 KiB). Reduce unused JavaScript (Est savings of 847 KiB). Reduce unused CSS (Est savings of 45 KiB). Legacy JavaScript (Est savings of 39 KiB). Details: - Avoid enormous network payloads (Total size was 5,827 KiB), from Shopify - Reduce unused JavaScript (Est savings of 847 KiB), from Shopify - Reduce unused CSS (Est savings of 45 KiB), from Shopify The fix, for a developer: Minify scripts and styles, remove unused and duplicate code, and stop shipping legacy polyfills. PageSpeed lists the files by size. Source: Avoid enormous network payloads, Chrome: https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · a few days
  • Your pages load without errorsImportantPartial

    An error in the browser often means part of your page is broken, such as a form that will not send. Chrome says each one is a problem to resolve.

    What we found: Browser errors were logged to the console.

    • Error producing monorail event MonorailUnableToProduceError: Error producing to the Monorail Edge. Response received: {"status":400,"message":"Invalid agent: Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36 Chrome-Lighthouse"} at T.produce (https://shopify-assets.shopifycdn.com/shopifycloud/arrive-server/pay/vite-pay/assets/AnalyticsProvider-BlmIIKHi.js:2:7049)

    How to fix it

    Open the page in a browser's developer tools and clear the errors it lists.

    Fix with AI

    My website https://assurancefirstaidkits.com.au/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your pages load without errors What the grader found: Browser errors were logged to the console. Details: - Error producing monorail event MonorailUnableToProduceError: Error producing to the Monorail Edge. Response received: {"status":400,"message":"Invalid agent: Mozilla/5.0 (Linux; Android 11; moto g power (2022)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Mobile Safari/537.36 Chrome-Lighthouse"} at T.produce (https://shopify-assets.shopifycdn.com/shopifycloud/arrive-server/pay/vite-pay/assets/AnalyticsProvider-BlmIIKHi.js:2:7049) The fix, for a developer: 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. Source: Browser errors were logged to the console, Chrome: https://developer.chrome.com/docs/lighthouse/best-practices/errors-in-console Explain the fix in plain words, then write what my web team should change and how we can check it worked. Full report, if you want more context: https://clutch.io/grade/assurancefirstaidkits-com-au

    Your web team · a few days
  • Your pages stay still while they loadImportantPass

    When content jumps as a page loads, visitors tap the wrong thing, such as a link that moved under their finger. Google counts layout shift among its three Core Web Vitals.

  • Your site loads over a secure connectionImportantPass

    A secure connection stops others reading or changing what passes between your site and its visitors. Browsers mark pages without one as not secure, and Google counts it in page experience.

  • Your server answers quicklyImportantPass

    Every visitor and agent waits for your server's first response before anything else can load. Chrome says a CDN, a network of servers close to your visitors, cuts that wait.

  • Your site does not ask visitors for permissions as they arriveImportantPass

    People distrust or are confused by a page that asks for their location the moment it opens. A field that blocks pasting makes a form harder to fill in.

Fix it,

or see it rebuilt

These 17 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 the Agent Grader report for assurancefirstaidkits.com.au, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/assurancefirstaidkits-com-au Then tell me how to fix each issue it lists, in order, and the effort each one takes, in plain words I can pass to my web team.

    Fix with AI

    Read the Agent Grader report for assurancefirstaidkits.com.au, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/assurancefirstaidkits-com-au Then tell me how to fix each issue it lists, in order, and the effort each one takes, in plain words I can pass to my web team.

  • See your site rebuilt

    Clutch rebuilds assurancefirstaidkits.com.au 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

See if AI chooses you

A shopper's AI agent

Find me a first aid kit for snake bites and a workplace that's WHS compliant, shipped to Australia. Which one should I buy?

Find

Did a search lead the agent to you?

  1. Searched“snake bite first aid kit Australia shipping”

    • stjohn.org.au
    • firstaidae.com.au
    • mediband.com
  2. Searched“WHS compliant first aid kit Australia supplier”

    • lfafirstresponse.com.au
    • assuresafetycompliance.com.au
    • stjohnwa.com.au
    • assurancefirstaidkits.com.au
Find partly passed

The agent found your site, but not from its first search.

Read

Did your site answer the shopper's question?

  1. Openedassurancefirstaidkits.com.au/products/workplace-first-aid-kit-10

    It could read the page right away: 1,030 words

  2. Openedtacmedaustralia.com.au/products/tacmed-snake-bite-kit

Read partly passed

The agent read your site, but what it found there didn't answer what the shopper asked.

The agent's answer

Short answer: For a snake bite kit, I'd pick the TacMed Snake Bite Kit (A$19.95). For a WHS-aligned workplace kit, I'd pick the Assurance Workplace First Aid Kit 10 (A$169.97). I read both sites, but I did not confirm that either will ship to an overseas address, so check that at checkout.

1. Snake bite kit: TacMed Snake Bite Kit

  • Why it fits: Its site says the kit is configured for correct Australian snakebite first aid in accordance with Australian Resuscitation Council (ARC) guidelines. It contains a pressure immobilisation bandage with printed pressure indicators and a calico triangular bandage for limb immobilisation.
  • Shipping: The site lists a flat rate of $12.95 Australia-wide, with free shipping on orders over $250. Metro delivery is quoted at 3–7 business days.
  • Caveat: The site describes Australia-wide shipping only, so I couldn't confirm delivery outside Australia.
  • Next step: Add the kit to your cart on the product page and check the shipping quote at checkout.
  • Pages relied on: https://tacmedaustralia.com.au/products/tacmed-snake-bite-kit

2. Workplace kit: Assurance Workplace First Aid Kit 10

  • Why it fits: The site describes it as an AS2675 WHS compliant first aid kit designed to cover up to 10 staff. It says it meets Safe Work Australia guidelines for low to moderate risk workplaces of up to 10 people.
  • What it contains: Per its FAQ, the contents include burn gel sachets, sodium chloride eyewash ampoules, thermal blanket, wound dressings, bandages, gloves, and full wound management supplies. The snake bite kit is not listed among those items.
  • Important caveat: The site says kit contents must be based on a risk assessment. So WHS compliance depends on your own workplace risk assessment, not on buying this kit alone. If your site has snake risk, add a snake bite kit or check that the contents cover it.
  • Shipping: Shipping is calculated at checkout. The product page says it is dispatched within 48 hours.
  • Caveat: A search snippet of the same product showed "Out of Stock," while the page I fetched didn't show a stock status. Confirm availability before buying.
  • Next step: Check the risk assessment, then add the kit to your cart and confirm stock and shipping at checkout.
  • Pages relied on: https://assurancefirstaidkits.com.au/products/workplace-first-aid-kit-10

Other options I found but did not read in full:

  • St John snake bite kit (A$25.95): its site says No international shipping.
  • Solmed, LFA First Response, FastAid (Aussie Pharma Direct), and Safetyxpress all sell WHS-related kits. I only saw their listings, not their product pages.

Which to buy: If you need both items, buy the TacMed snake kit and the Assurance kit. If you only need one, your answer depends on whether you need a workplace kit for a team of up to 10 or a snake kit for personal or vehicle use.

Act

Could the agent do the shopper's next step?

The shopper's next request: “Order the snake bite first aid kit you recommend and have it shipped to me.”

  1. Looked for a way to do it on your site

    Your site offers AI agents a tool that does it

Act passed

An agent can do it for the shopper, right on your site.

The shopper's agent found you, though not from its first search, read your site but didn't get its answer there and could act for the shopper.

  1. Find

    Nothing on your site held search back. Other sites ranked higher for this request.

  2. Read

    Say what you offer, where and for how much, in plain words on your pages.

  3. Act

    Passed. A few checks could still be stronger.

These sites are competing with you

SiteLetterFindReadActPerformance
assurancefirstaidkits.com.auBuilt in ClutchAFindPassesReadPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
assurancefirstaidkits.com.auDFind100Read71Act63Performance71
tacmedaustralia.com.auOpened by the AI agent

See assurancefirstaidkits.com.au rebuilt, without these issues

4th of 6 local business sites graded so far. See the board.

How we grade