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

    Your site responds quickly to taps and clicks

    Total Blocking Time (1,060 ms)

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

    Your web team · a week or moreSee the check

  3. Partial·Performance

    Your main content shows up quickly on phones

    Largest Contentful Paint (26.6 s). First Contentful Paint (2.7 s). Speed Index (15.1 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

93

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

  • Your site says when a page does not exist (404)ImportantFail

    When a missing page says so, Google drops the address from search. When it answers like a normal page, Google flags a soft 404, and every mistyped address looks like a real page.

    What we found: An address that does not exist answers 429 instead of 404 or 410.

    • Status 429

    How to fix it

    Make a mistyped address show a page that says it was not found, with a 404 status behind it.

    Fix with AI

    My website https://kailashmansarovaryatra.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 when a page does not exist (404) What the grader found: An address that does not exist answers 429 instead of 404 or 410. Details: - Status 429 The fix, for a developer: Return 404 (or 410 for a page that is gone) for unknown routes. A single-page app needs its server to answer unknown paths with the not-found page and a 404 status, since a redirect to the home page makes every address look real. Source: How Google Search handles HTTP status codes, Google: https://developers.google.com/crawling/docs/troubleshooting/http-status-codes; RFC 9110, section 15.5.5 404 Not Found, IETF: https://www.rfc-editor.org/rfc/rfc9110#section-15.5.5 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/kailashmansarovaryatra-com-au

    Your web team · about an hour
  • A page that can be reached at more than one address names its main one (canonical)ImportantPartial

    Google shows only one address for a page. When you name it, the page's standing stays in one place and searchers land on the version you chose, in their language. When you don't, Google guesses.

    What we found: Document does not have a valid rel=canonical.

    How to fix it

    Give each page one main address that search engines treat as its own.

    Fix with AI

    My website https://kailashmansarovaryatra.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: A page that can be reached at more than one address names its main one (canonical) What the grader found: Document does not have a valid rel=canonical. The fix, for a developer: Add one absolute <link rel="canonical"> to the head of every page, pointing at that page's preferred address. Give each hreflang a valid language code and an absolute address. Source: How to Specify a Canonical with rel="canonical" and Other Methods, Google: https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls 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/kailashmansarovaryatra-com-au

    Your web team · about an hour
  • Your site's security doesn't turn AI agents away (firewall)CriticalPass

    Many sites sit behind a firewall or bot-protection service that blocks automated visits. An agent stopped at the door reads nothing, so it answers from other sites. Claude's web fetch, for example, gets only what your site sends back.

  • Your site lets AI agents in (robots.txt)CriticalPass

    AI services send crawlers, robots that read sites for them. One your robots.txt blocks cannot use your pages, so answers about your business come from other sites. OpenAI, Anthropic and Perplexity each say their crawlers obey robots.txt.

  • Search engines may show your pages in their resultsCriticalPass

    A page search engines may not list is missing from Google's and Bing's results, and from AI answers built on them, such as Google's AI Overviews. Brave's search, which some AI agents use, follows Google's rules.

  • Your instructions to AI agents and search engines have no errors (robots.txt)ImportantPass

    Google's crawler skips any line of robots.txt it cannot read, so a rule you meant to set never applies. A page you wanted found may be left out, or one you wanted kept out may be read.

  • Your site lists its pages for search engines (XML sitemap)ImportantPass

    Google and Bing use a sitemap to find your pages, though neither promises to list every page in it. A page must be in Google's index to appear in its AI answers.

  • Every page has a titleImportantPass

    Google builds the link to your page in its results from the page's title, and may rewrite one that is missing, vague or repeated. A clear title keeps your own words in front of searchers.

  • Your pages open without unnecessary redirectsImportantPass

    Each extra redirect is another trip across the network that can delay the page by hundreds of milliseconds. Every visitor waits for every hop.

80

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 10 goals pass

  • 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: ARD manifest is invalid

    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://kailashmansarovaryatra.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: ARD manifest is invalid 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/kailashmansarovaryatra-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://kailashmansarovaryatra.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/kailashmansarovaryatra-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://kailashmansarovaryatra.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/kailashmansarovaryatra-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.

  • Headings give each page a clear outlineImportantPass

    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.

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

48

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

    • Elements must only use supported ARIA attributes: <span class="brxe-nndgly brxe-button bricks-button lg bricks-background-primary" data-interactions="[{&quot;id&quot;:&quot;dwdqbd&quot;,&quot;trigger&quot;:&quot;click&quot;,&quot;action&quot;:&quot;toggleOffCanvas&quot;,&quot;offCanvasSel…" data-interaction-id="148daa" data-brx-toggle-offcanvas="true" tabindex="0" aria-expanded="false" aria-label="Open" data-interaction-loop-id="vypidf:0:post:2183">
    • Buttons must have discernible text: <button id="brxe-efcwbg" class="brxe-back-to-top visible">
    • Links must have discernible text: <a class="brxe-image social-icon tag" href="https://www.facebook.com/KailashVisionTreks" target="_blank" aria-describedby="brx-new-tab-link-description">

    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://kailashmansarovaryatra.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: - Elements must only use supported ARIA attributes: <span class="brxe-nndgly brxe-button bricks-button lg bricks-background-primary" data-interactions="[{&quot;id&quot;:&quot;dwdqbd&quot;,&quot;trigger&quot;:&quot;click&quot;,&quot;action&quot;:&quot;toggleOffCanvas&quot;,&quot;offCanvasSel…" data-interaction-id="148daa" data-brx-toggle-offcanvas="true" tabindex="0" aria-expanded="false" aria-label="Open" data-interaction-loop-id="vypidf:0:post:2183"> - Buttons must have discernible text: <button id="brxe-efcwbg" class="brxe-back-to-top visible"> 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/kailashmansarovaryatra-com-au

    Your web team · about a day
  • AI agents can complete tasks when they visit your site (WebMCP)ImportantFail

    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.

    How to fix it

    Let agents do every task a customer can do on your site, through WebMCP.

    Fix with AI

    My website https://kailashmansarovaryatra.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 when they visit your site (WebMCP) What the grader found: Your home page offers agents no tasks to complete through WebMCP. The fix, for a developer: Register a WebMCP tool for every task a customer can do as the page loads: call document.modelContext.registerTool() with a name, a description, an input schema and an execute function, or add toolname and tooldescription attributes to the form. A name is 1 to 128 letters, digits, _, - or . Source: WebMCP for developers, Chrome: https://developer.chrome.com/docs/ai/webmcp; WebMCP, Draft Community Group Report, W3C Web Machine Learning Community Group: https://webmachinelearning.github.io/webmcp/ 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/kailashmansarovaryatra-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 429

    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://kailashmansarovaryatra.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 429 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/kailashmansarovaryatra-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 loading="lazy" allow="accelerometer; autoplay; clipboard-write; encrypted-media; fullscreen; gyr…" referrerpolicy="strict-origin-when-cross-origin" data-src="https://www.youtube.com/embed/2wwwsU9-tWE?wmode=opaque&amp;rel=0&amp;enablejsapi=1…" class="bricks-lazy-hidden">
    • 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 loading="lazy" allow="accelerometer; autoplay; clipboard-write; encrypted-media; fullscreen; gyr…" referrerpolicy="strict-origin-when-cross-origin" data-src="https://www.youtube.com/embed/8SJ00IYNvN0?wmode=opaque&amp;rel=0&amp;enablejsapi=1…" class="bricks-lazy-hidden">
    • 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 loading="lazy" allow="accelerometer; autoplay; clipboard-write; encrypted-media; fullscreen; gyr…" referrerpolicy="strict-origin-when-cross-origin" data-src="https://www.youtube.com/embed/Ria1pmFJyCU?wmode=opaque&amp;rel=0&amp;enablejsapi=1…" class="bricks-lazy-hidden">

    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://kailashmansarovaryatra.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 Details: - 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 loading="lazy" allow="accelerometer; autoplay; clipboard-write; encrypted-media; fullscreen; gyr…" referrerpolicy="strict-origin-when-cross-origin" data-src="https://www.youtube.com/embed/2wwwsU9-tWE?wmode=opaque&amp;rel=0&amp;enablejsapi=1…" class="bricks-lazy-hidden"> 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/kailashmansarovaryatra-com-au

    Your web team · a few days
  • Hidden labels on your buttons and fields are accurate (ARIA)ImportantPartial

    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.

    What we found: [aria-*] attributes do not match their roles.

    • Fix all of the following: ARIA attribute is not allowed: aria-expanded="false": <span class="brxe-nndgly brxe-button bricks-button lg bricks-background-primary" data-interactions="[{&quot;id&quot;:&quot;dwdqbd&quot;,&quot;trigger&quot;:&quot;click&quot;,&quot;action&quot;:&quot;toggleOffCanvas&quot;,&quot;offCanvasSel…" data-interaction-id="148daa" data-brx-toggle-offcanvas="true" tabindex="0" aria-expanded="false" aria-label="Open" data-interaction-loop-id="vypidf:0:post:2183">

    How to fix it

    Fix the ARIA errors Google's PageSpeed Insights lists and use standard buttons and fields where they exist.

    Fix with AI

    My website https://kailashmansarovaryatra.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: Hidden labels on your buttons and fields are accurate (ARIA) What the grader found: [aria-*] attributes do not match their roles. Details: - Fix all of the following: ARIA attribute is not allowed: aria-expanded="false": <span class="brxe-nndgly brxe-button bricks-button lg bricks-background-primary" data-interactions="[{&quot;id&quot;:&quot;dwdqbd&quot;,&quot;trigger&quot;:&quot;click&quot;,&quot;action&quot;:&quot;toggleOffCanvas&quot;,&quot;offCanvasSel…" data-interaction-id="148daa" data-brx-toggle-offcanvas="true" tabindex="0" aria-expanded="false" aria-label="Open" data-interaction-loop-id="vypidf:0:post:2183"> The fix, for a developer: Use native elements first, give each ARIA role its required attributes and children, remove attributes the role does not allow, and keep ids unique. Source: Rule aria-roles: ARIA roles used must conform to valid values, Deque axe: https://dequeuniversity.com/rules/axe/4.13/aria-roles; Accessible Rich Internet Applications (WAI-ARIA) 1.2, W3C: https://www.w3.org/TR/wai-aria-1.2/ 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/kailashmansarovaryatra-com-au

    Your web team · a few days
  • 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 1.87 (foreground color: #ffffff, background color: #f5b042, font size: 10.7pt (14.3244px), font weight: bold). Expected contrast ratio of 4.5:1: <div id="brxe-bkbxpo" data-script-id="bkbxpo" class="brxe-code">

    How to fix it

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

    Fix with AI

    My website https://kailashmansarovaryatra.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 1.87 (foreground color: #ffffff, background color: #f5b042, font size: 10.7pt (14.3244px), font weight: bold). Expected contrast ratio of 4.5:1: <div id="brxe-bkbxpo" data-script-id="bkbxpo" class="brxe-code"> 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/kailashmansarovaryatra-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 (204px by 19px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 16.2px instead of at least 24px.: <a href="your home page">

    How to fix it

    Make small buttons and tightly packed links bigger on phones.

    Fix with AI

    My website https://kailashmansarovaryatra.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 (204px by 19px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 16.2px instead of at least 24px.: <a href="your home page"> 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/kailashmansarovaryatra-com-au

    Your web team · about an hour
  • Your site tells AI agents about its other servicesImportantPartial

    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 site has no API catalog. Your site has no Agent Skills index. Your site has no A2A agent card.

    • API Catalog returned status 429
    • Agent Skills index returned status 429
    • A2A Agent Card returned status 429

    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://kailashmansarovaryatra.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 site has no API catalog. Your site has no Agent Skills index. Your site has no A2A agent card. Details: - API Catalog returned status 429 - Agent Skills index returned status 429 - A2A Agent Card returned status 429 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/kailashmansarovaryatra-com-au

    Your web team · about a day
  • 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.

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

63

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

  • Your site responds quickly to taps and clicksImportantFail

    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 (1,060 ms)

    • Reduce JavaScript execution time (3.4 s), from hcaptcha.com
    • Minimize main-thread work (5.9 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://kailashmansarovaryatra.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 (1,060 ms) Details: - Reduce JavaScript execution time (3.4 s), from hcaptcha.com - Minimize main-thread work (5.9 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/kailashmansarovaryatra-com-au

    Your web team · a week or more
  • 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 980 KiB)

    • Use efficient cache lifetimes (Est savings of 980 KiB), from Stripe
    • Use efficient cache lifetimes (Est savings of 980 KiB), from hcaptcha.com
    • Use efficient cache lifetimes (Est savings of 980 KiB), from Facebook

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://kailashmansarovaryatra.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 980 KiB) Details: - Use efficient cache lifetimes (Est savings of 980 KiB), from Stripe - Use efficient cache lifetimes (Est savings of 980 KiB), from hcaptcha.com - Use efficient cache lifetimes (Est savings of 980 KiB), from Facebook 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/kailashmansarovaryatra-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 (26.6 s). First Contentful Paint (2.7 s). Speed Index (15.1 s). Lab test on a phone: too few real visitors to measure it.

    • LCP request discovery
    • LCP breakdown
    • Render-blocking requests (Est savings of 2,430 ms)

    How to fix it

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

    Fix with AI

    My website https://kailashmansarovaryatra.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 (26.6 s). First Contentful Paint (2.7 s). Speed Index (15.1 s). Lab test on a phone: too few real visitors to measure it. Details: - LCP request discovery - LCP breakdown - Render-blocking requests (Est savings of 2,430 ms) 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/kailashmansarovaryatra-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 90 KiB).

    • Improve image delivery (Est savings of 90 KiB): <img width="2030" height="2371" src="/wp-content/uploads/Kailash-2027-Hand…" class="brxe-image css-filter size-full" alt="kailash mansarovar yatra 2027 itinearary" id="brxe-hgukbw" loading="eager" decoding="async" srcset="/wp-content/uploads/Kailash-2027-Hand…" sizes="(max-width: 2030px) 100vw, 2030px">

    How to fix it

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

    Fix with AI

    My website https://kailashmansarovaryatra.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 90 KiB). Details: - Improve image delivery (Est savings of 90 KiB): <img width="2030" height="2371" src="/wp-content/uploads/Kailash-2027-Hand…" class="brxe-image css-filter size-full" alt="kailash mansarovar yatra 2027 itinearary" id="brxe-hgukbw" loading="eager" decoding="async" srcset="/wp-content/uploads/Kailash-2027-Hand…" sizes="(max-width: 2030px) 100vw, 2030px"> 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/kailashmansarovaryatra-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 10,920 KiB). Reduce unused JavaScript (Est savings of 465 KiB). Reduce unused CSS (Est savings of 33 KiB). Minify JavaScript (Est savings of 4 KiB). Minify CSS (Est savings of 2 KiB). Legacy JavaScript (Est savings of 19 KiB).

    • Avoid enormous network payloads (Total size was 10,920 KiB), from hcaptcha.com
    • Reduce unused JavaScript (Est savings of 465 KiB), from Stripe

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://kailashmansarovaryatra.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 10,920 KiB). Reduce unused JavaScript (Est savings of 465 KiB). Reduce unused CSS (Est savings of 33 KiB). Minify JavaScript (Est savings of 4 KiB). Minify CSS (Est savings of 2 KiB). Legacy JavaScript (Est savings of 19 KiB). Details: - Avoid enormous network payloads (Total size was 10,920 KiB), from hcaptcha.com - Reduce unused JavaScript (Est savings of 465 KiB), from Stripe 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/kailashmansarovaryatra-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.

    • Failed to load resource: the server responded with a status of 400 (Bad Request)

    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://kailashmansarovaryatra.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: - Failed to load resource: the server responded with a status of 400 (Bad Request) 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/kailashmansarovaryatra-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 20 fixes add up to about seven 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 kailashmansarovaryatra.com.au, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/kailashmansarovaryatra-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 kailashmansarovaryatra.com.au, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/kailashmansarovaryatra-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 kailashmansarovaryatra.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

I want to go on a Kailash Mansarovar pilgrimage from Kathmandu in 2027. Which operators offer an all-inclusive overland tour with experienced guides and help with the Tibet and Nepal permits?

Find

Did a search lead the agent to you?

  1. Searched“Kailash Mansarovar yatra overland from Kathmandu 2027 all-inclusive”

    • kailashmansarovaryatra.com.au
    • adventurealtitudetreks.com
    • nilavoyages.com
  2. Searched“Kailash Mansarovar tour operator Kathmandu Tibet permit help”

    • mercyholidays.com
    • itibettravel.com
    • himalayanglacier.com
  3. Openedhimalayanglacier.com/trips/kailash-and-lake-mansarovar-yatra

  4. Openednilavoyages.com/kailash-overland-kathmandu

  5. Openedkailashjourneys.com/kailash-mansarovar-yatra

Find failed

Search led the agent to himalayanglacier.com, nilavoyages.com and kailashjourneys.com, never to you. A real shopper's agent would have stopped there, so we sent ours to your site to see the rest.

Read

Did your site answer the shopper's question?

  1. We sent the agent tokailashmansarovaryatra.com.au

    It could read the page right away: 743 words

Read passed

Your site answered what the shopper asked.

The agent's answer

I read the homepage of Kailash Mansarovar Yatra (kailashmansarovaryatra.com.au). It's a possible fit, but I only read the homepage, so some of your questions aren't answered yet.

Why it fits: It runs a 2027 overland Nepal–Tibet pilgrimage that starts from Kathmandu. They offer Kailash Mansarovar Yatra to pilgrims through the Nepal–Tibet route. We organise the itinerary, arrange the permits, and guide the participants throughout the journey. That covers your permit question directly. The site's description also calls it an all-inclusive pilgrimage with expert guides, sacred rituals at Lake Mansarovar.

What the site says about the overland tour:

  • Overland package: 13 Nights | 14 Days, May - September season, priced at AUD $3,197 per person.
  • Included features listed include Mount Kailash Kora (3-Day Trek), Lake Mansarovar Rituals and Parikrama, and Comfort and Support Throughout.
  • There is a promotion: Save up to AUD $800 on a limited-time early bird offer.
  • Reviews: Based on 157 reviews on Tripadvisor. One verified reviewer wrote that the trip was planned good with all amenities provided, food was excellent and Sherpas were very helpful.
  • The site also offers a helicopter version for AUD $5,780, which is outside your overland request.

Gaps: The homepage doesn't give a detailed list of what the price includes, the guides' credentials, or how the permit process works. The site's own pages on cost and inclusions, Tibet visa, and Nepal visa likely cover these, but I haven't read them. The homepage also describes itself as an "Authorised" operator, but I did not verify that claim against any official source.

Next step: The site offers a free consultation and an enquiry form, and it says you can submit your details to download our Comprehensive Overland Yatra 2027 Itinerary and Information Pack. Before paying, I'd ask them in writing what the AUD 3,197 covers, who the guides are and how experienced they are, and who handles the Tibet and Nepal permits.

Pages I relied on: Only the homepage, https://kailashmansarovaryatra.com.au/.

Act

Could the agent do the shopper's next step?

The shopper's next request: “Book my place on the 2027 overland Kailash Mansarovar tour and tell me what paperwork and deposit I need to send.”

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

    Your site offers AI agents no way to do it

Act failed

The agent couldn't do it, so the shopper is left with a form, a phone number or a contact page.

The shopper's agent didn't find you, got its answer from your site and couldn't act for the shopper.

  1. Find

    Other sites ranked higher for this request, and your report found checks that hold search back.

  2. Read

    Passed. A few checks could still be stronger.

  3. Act

    Let AI agents do the shopper's next step on your site.

These sites are competing with you

SiteLetterFindReadActPerformance
kailashmansarovaryatra.com.auBuilt in ClutchAFindPassesReadPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
kailashmansarovaryatra.com.auDFind93Read80Act48Performance63
himalayanglacier.comOpened by the AI agent
nilavoyages.comOpened by the AI agent
kailashjourneys.comOpened by the AI agent

See kailashmansarovaryatra.com.au rebuilt, without these issues

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

How we grade