F

Not ready for AI agents

Speed: Pass (real visitors, last 28 days)Core Web Vitals, Google

Start here.

These hold your letter down the most
  1. Unknown·Read

    AI agents can read your text without running scripts

    Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    What to do Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Your web team · a few daysSee the check

  2. Unknown·Read

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

    Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    What to do Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Your web team · about a daySee the check

  3. Fail·Find

    Your site's security doesn't turn AI agents away (firewall)

    Your site answered Cloudflare's scan with 403 Forbidden instead of the page.

    What to do Let automated visits to your public pages through the firewall.

    Your web team · about an hourSee the check

73

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

  • Your site's security doesn't turn AI agents away (firewall)CriticalFail

    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.

    What we found: Your site answered Cloudflare's scan with 403 Forbidden instead of the page.

    • Answered 403 Forbidden

    How to fix it

    Let automated visits to your public pages through the firewall.

    Fix with AI

    My website https://etsy.com/ 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's security doesn't turn AI agents away (firewall) What the grader found: Your site answered Cloudflare's scan with 403 Forbidden instead of the page. Details: - Answered 403 Forbidden The fix, for a developer: Find the firewall or bot-protection rule that answers automated requests with a challenge or a 403, and exempt requests for public pages. Run Cloudflare's agent readiness scan again to confirm it gets the page. Source: Web fetch tool, Anthropic: https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-fetch-tool; Is Your Site Agent-Ready?, Cloudflare: https://isitagentready.com/ 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/etsy-com/2026-11-13

    Your web team · about an hour

    Tested by CloudflareWeb fetch tool, Anthropic

    Report an issue with this check
  • Your pages open without unnecessary redirectsImportantFail

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

    What we found: Page has unsuccessful HTTP status code (403). Not measured: Lighthouse could not run "Avoid multiple page redirects" on the home page: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP).

    How to fix it

    Point old addresses straight at the page they now belong to.

    Fix with AI

    My website https://etsy.com/ 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 open without unnecessary redirects What the grader found: Page has unsuccessful HTTP status code (403). Not measured: Lighthouse could not run "Avoid multiple page redirects" on the home page: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP). The fix, for a developer: Link to the final address, and make each redirect reach its destination in one hop, such as one rule that sends http and non-www straight to the final https address. Source: Avoid multiple page redirects, Chrome: https://developer.chrome.com/docs/lighthouse/performance/redirects 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/etsy-com/2026-11-13

    Your web team · about an hour

    Tested by Google LighthouseAvoid multiple page redirects, Chrome

    Report an issue with this check
  • Your site lets AI agents in (robots.txt)CriticalNot measured

    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.

    What we found: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareOverview of OpenAI crawlers, OpenAI

    Report an issue with this check
  • Your site lists its pages for search engines (XML sitemap)ImportantNot measured

    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.

    What we found: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareBuild and submit a sitemap, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseAI features and your website, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseRobots.txt Introduction and Guide, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseInfluencing Title Links in Google Search, Google

    Report an issue with this check
  • Your site says when a page does not exist (404)ImportantPass

    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.

    Tested by ClutchHow Google Search handles HTTP status codes, Google

    Report an issue with this check
  • A page that can be reached at more than one address names its main one (canonical)ImportantPass

    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.

    Tested by Google LighthouseHow to Specify a Canonical with rel="canonical" and Other Methods, Google

    Report an issue with this check

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

  • AI agents can read your text without running scriptsCriticalUnknown

    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.

    What we found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    • our reader was turned away

    How to fix it

    Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Fix with AI

    My website https://etsy.com/ 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 read your text without running scripts What the grader found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does. Details: - our reader was turned away The fix, for a developer: Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader. Source: Understand JavaScript SEO basics, Google Search Central: https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics; HTML Standard, Parsing HTML documents, WHATWG: https://html.spec.whatwg.org/multipage/parsing.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/etsy-com/2026-11-13

    Your web team · a few days

    Tested by ClutchUnderstand JavaScript SEO basics, Google Search Central

    Report an issue with this check
  • Your site tells AI agents what your business is (structured data)ImportantUnknown

    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.

    What we found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does.

    • our reader was turned away

    How to fix it

    Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

    Fix with AI

    My website https://etsy.com/ 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 what your business is (structured data) What the grader found: Your site's firewall turned away our reader, which asks for a page the way an AI agent that runs no scripts does. Details: - our reader was turned away The fix, for a developer: Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader. Source: Intro to structured data, Google: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data; JSON-LD 1.1, W3C: https://www.w3.org/TR/json-ld11/ 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/etsy-com/2026-11-13

    Your web team · about a day

    Tested by ClutchIntro to structured data, Google

    Report an issue with this check
  • 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://etsy.com/ 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/etsy-com/2026-11-13

    Your web team · about a day

    Tested by Google LighthouseLighthouse agentic browsing scoring, Chrome

    Report an issue with this check
  • Every page has a summary for search resultsImportantFail

    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.

    What we found: Document does not have a meta description

    How to fix it

    Write a one or two sentence summary of every page, different on each.

    Fix with AI

    My website https://etsy.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Every page has a summary for search results What the grader found: Document does not have a meta description The fix, for a developer: Add <meta name="description" content="..."> to the head of every page, with a sentence or two unique to that page. Source: How to Write Meta Descriptions, Google: https://developers.google.com/search/docs/appearance/snippet; Document does not have a meta description, Chrome: https://developer.chrome.com/docs/lighthouse/seo/meta-description 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/etsy-com/2026-11-13

    Your web team · about an hour

    Tested by Google LighthouseHow to Write Meta Descriptions, Google

    Report an issue with this check
  • Your site sends AI agents a plain-text version of each page (Markdown)ImportantNot measured

    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: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareMarkdown for Agents, Cloudflare

    Report an issue with this check
  • Your site says how AI may use its content (Content Signals)ImportantNot measured

    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: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareContent Signals, Content Signals

    Report an issue with this check
  • 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.

    Tested by Google Lighthousellms.txt audit, Chrome

    Report an issue with this check
  • 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.

    Tested by Google LighthouseRule html-has-lang: <html> element must have a lang attribute, Deque axe

    Report an issue with this check
57

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

  • AI agents can move around your pages without a mouseImportantFail

    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.

    What we found: Document does not have a main landmark.

    • Fix all of the following: Document does not have a main landmark: <html lang="en">

    How to fix it

    Make every page work from the keyboard alone.

    Fix with AI

    My website https://etsy.com/ 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 move around your pages without a mouse What the grader found: Document does not have a main landmark. Details: - Fix all of the following: Document does not have a main landmark: <html lang="en"> The fix, for a developer: Wrap the page's content in one main element, add a skip link to it, keep tabindex at 0 or less, and remove meta refresh redirects. Source: Accessibility for agents, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/accessibility-for-agents; Understanding Success Criterion 2.1.1: Keyboard, W3C: https://www.w3.org/WAI/WCAG22/Understanding/keyboard.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/etsy-com/2026-11-13

    Your web team · about a day

    Tested by Google LighthouseAccessibility for agents, Chrome

    Report an issue with this check
  • 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.

    What we found: Not measured: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    • PageSpeed's "WebMCP tools registered" audit lists no tool

    How to fix it

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

    Fix with AI

    My website https://etsy.com/ 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: Not measured: Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this. Details: - PageSpeed's "WebMCP tools registered" audit lists no tool 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/etsy-com/2026-11-13

    Your web team · about a day

    Tested by Google LighthouseCloudflareWebMCP for developers, Chrome

    Report an issue with this check
  • 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://etsy.com/ 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/etsy-com/2026-11-13

    Your web team · a few days

    Tested by ClutchSEP-2127: MCP Server Cards, Model Context Protocol

    Report an issue with this check
  • Your site tells AI agents about its other servicesImportantNot measured

    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 turned Cloudflare's scan away (403 Forbidden), so it could not check this, Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this, Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this, and Your site turned Cloudflare's scan away (403 Forbidden), so it could not check this.

    Tested by CloudflareRFC 8288, Web Linking, IETF

    Report an issue with this check
  • AI agents can see your site's buttons and fields (accessibility tree)CriticalPass

    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.

    Tested by Google LighthouseAccessibility for agents, Chrome

    Report an issue with this check
  • 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.

    Tested by Google LighthouseRule aria-roles: ARIA roles used must conform to valid values, Deque axe

    Report an issue with this check
  • Your text stands out clearly from its backgroundImportantPass

    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.

    Tested by Google LighthouseRule color-contrast: Elements must meet minimum color contrast ratio thresholds, Deque axe

    Report an issue with this check
  • Buttons and links are big enough for an agent to clickImportantPass

    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.

    Tested by Google LighthouseAccessible tap targets, Google

    Report an issue with this check
  • Videos and embedded content have text AI agents can readImportantPass

    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.

    Tested by Google LighthouseAccessibility for agents, Chrome

    Report an issue with this check
80

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 8 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 32 KiB)

    • Use efficient cache lifetimes (Est savings of 32 KiB), from captcha-delivery.com
    • Use efficient cache lifetimes (Est savings of 32 KiB), from captcha-delivery.com
    • Use efficient cache lifetimes (Est savings of 32 KiB), from captcha-delivery.com

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://etsy.com/ 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 32 KiB) Details: - Use efficient cache lifetimes (Est savings of 32 KiB), from captcha-delivery.com - Use efficient cache lifetimes (Est savings of 32 KiB), from captcha-delivery.com - Use efficient cache lifetimes (Est savings of 32 KiB), from captcha-delivery.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/etsy-com/2026-11-13

    Your web team · about an hour

    Tested by Google LighthousePrevent unnecessary network requests with the HTTP Cache, Google

    Report an issue with this check
  • Your server answers quicklyImportantPartial

    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.

    What we found: Document request latency (Est savings of 80 ms).

    • Network Round Trip Times (0 ms)
    • Server Backend Latencies (0 ms)

    How to fix it

    Speed up its first response, for example with a CDN in front of it.

    Fix with AI

    My website https://etsy.com/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: Your server answers quickly What the grader found: Document request latency (Est savings of 80 ms). Details: - Network Round Trip Times (0 ms) - Server Backend Latencies (0 ms) The fix, for a developer: 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. Source: Reduce server response times (TTFB), Chrome: https://developer.chrome.com/docs/lighthouse/performance/server-response-time 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/etsy-com/2026-11-13

    Your web team · about a day

    Tested by Google LighthouseReduce server response times (TTFB), Chrome

    Report an issue with this check
  • 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 7 KiB).

    • Improve image delivery (Est savings of 7 KiB): <img src="//static.captcha-delivery.com/captcha/assets/set/e0aa99be678965d8c0263bcfd…" class="captcha__header__logo" data-dd-captcha-header-logo="">, from captcha-delivery.com

    How to fix it

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

    Fix with AI

    My website https://etsy.com/ 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 7 KiB). Details: - Improve image delivery (Est savings of 7 KiB): <img src="//static.captcha-delivery.com/captcha/assets/set/e0aa99be678965d8c0263bcfd…" class="captcha__header__logo" data-dd-captcha-header-logo="">, from captcha-delivery.com 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/etsy-com/2026-11-13

    Your web team · about a day

    Tested by Google LighthouseProperly size images, Chrome

    Report an issue with this check
  • 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. Page lacks the HTML doctype, thus triggering quirks-mode.

    • Failed to load resource: the server responded with a status of 403 (Forbidden)

    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://etsy.com/ 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. Page lacks the HTML doctype, thus triggering quirks-mode. Details: - Failed to load resource: the server responded with a status of 403 (Forbidden) 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/etsy-com/2026-11-13

    Your web team · a few days

    Tested by Google LighthouseBrowser errors were logged to the console, Chrome

    Report an issue with this check
  • Your main content shows up quickly on phonesImportantNot measured

    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: Lighthouse could not run "Largest Contentful Paint" on the home page: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP), Lighthouse could not run "First Contentful Paint" on the home page: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP), and Lighthouse could not run "Speed Index" on the home page: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP).

    Tested by Google LighthouseWeb Vitals, Google

    Report an issue with this check
  • Your site responds quickly to taps and clicksImportantNot measured

    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: Lighthouse could not run "Total Blocking Time" on the home page: The page did not paint any content. Please ensure you keep the browser window in the foreground during the load and try again. (NO_FCP)

    Tested by Google LighthouseTotal Blocking Time (TBT), Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseWeb Vitals, Google

    Report an issue with this check
  • 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.

    Tested by Google LighthouseWhy HTTPS matters, Google

    Report an issue with this check
  • Your pages are light to downloadImportantPass

    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.

    Tested by Google LighthouseAvoid enormous network payloads, Chrome

    Report an issue with this check
  • 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.

    Tested by Google LighthouseRequests the geolocation permission on page load, Chrome

    Report an issue with this check

Fix it,

or see it rebuilt

These 13 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 the Agent Grader report for etsy.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/etsy-com/2026-11-13 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 etsy.com, which tests whether AI agents can find, read and use the site: https://clutch.io/grade/etsy-com/2026-11-13 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 etsy.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

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.

See etsy.com rebuilt, without these issues

67th of 67 sites graded so far. See the board.

Let plain requests for your public pages through your firewall's bot challenge. Our reader asks for a page the way an AI agent that runs no scripts does, and names itself ClutchGrader.

How we grade