eightyone10.com

My website https://www.eightyone10.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 says when a page does not exist (404) What the grader found: An address that does not exist answers 200 with a normal page. Details: - Status 200 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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: 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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: 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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: Google's Lighthouse finds your ARD catalog invalid, so agents cannot rely on it to find your MCP server. Details: - Lighthouse's ard-schema audit fails 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 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 returned HTML instead of JSON - Agent Skills index returned HTML instead of JSON 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 responds quickly to taps and clicks What the grader found: Total Blocking Time (1,190 ms) Details: - Reduce JavaScript execution time (5.7 s), from audioeye-services.com - Minimize main-thread work (10.7 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 main content shows up quickly on phones What the grader found: Largest Contentful Paint (4.0 s). First Contentful Paint (2.4 s). Speed Index (7.7 s). Lab test on a phone: too few real visitors to measure it. Details: - Render-blocking requests (Est savings of 660 ms) - 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 stay still while they load What the grader found: Cumulative Layout Shift (0.215) Details: - Layout shift culprits - Avoid large layout shifts (10 layout shifts found): <section class="relative w-full h-[65vh] md:h-[70vh] min-h-[420px] max-h-[780px] overflow-…"> - Avoid non-composited animations (7 animated elements found): <iframe class="doorway-launcher-button-frame bounce" scrolling="no" id="ae_iframe_gkg3bop8"> The fix, for a developer: Set width and height on images and embeds, reserve space for late content, and use font-display with a matching fallback font. Source: Web Vitals, Google: https://web.dev/articles/vitals; Cumulative Layout Shift (CLS), Google: https://web.dev/articles/cls 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 490 ms). Details: - Network Round Trip Times (10 ms) - Server Backend Latencies (50 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 472 KiB). Image elements do not have explicit width and height. Details: - Improve image delivery (Est savings of 472 KiB): <img src="https://media.multihub.io/cdn-cgi/image/format=auto,w=960/property/6767906…" srcset="https://media.multihub.io/cdn-cgi/image/format=auto,w=160/property/6767906…" sizes="100vw" alt="Two Adirondack chairs and a cornhole game set up on artificial turf in fro…" loading="lazy" fetchpriority="auto" class="absolute inset-0 w-full h-full object-cover transition-opacity duration-[6…">, from multihub.io 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 are light to download What the grader found: Avoid enormous network payloads (Total size was 4,837 KiB). Reduce unused JavaScript (Est savings of 1,413 KiB). Minify JavaScript (Est savings of 8 KiB). Duplicated JavaScript (Est savings of 4 KiB). Legacy JavaScript (Est savings of 28 KiB). Details: - Avoid enormous network payloads (Total size was 4,837 KiB), from knck.io - Reduce unused JavaScript (Est savings of 1,413 KiB), from knck.io - Minify JavaScript (Est savings of 8 KiB), from multihub.io 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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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 1,262 KiB) Details: - Use efficient cache lifetimes (Est savings of 1,262 KiB), from knck.io - Use efficient cache lifetimes (Est savings of 1,262 KiB), from knck.io - Use efficient cache lifetimes (Est savings of 1,262 KiB), from audioeye-services.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/eightyone10-com/2026-11-11

My website https://www.eightyone10.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. Uses deprecated APIs (1 warning found). Details: - Uncaught TypeError: Cannot read properties of undefined (reading '_loaded') 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/eightyone10-com/2026-11-11