F

Not ready for AI agents

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

Start here.

These hold your letter down the most
  1. Fail·Performance

    Your main content shows up quickly on phones

    Largest Contentful Paint is 7.1 s for real visitors of your whole site, last 28 days, which Google rates poor. First Contentful Paint is 6.3 s for real visitors of your whole site, last 28 days, which Google rates poor. Speed Index (14.5 s). Measured from real visitors of your whole site, last 28 days; the rest is a lab test on a phone.

    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

  2. Fail·Performance

    Your pages stay still while they load

    Cumulative Layout Shift is 0.27 for real visitors of your whole site, last 28 days, which Google rates poor.

    What to do Stop content from moving as images and fonts load.

    Your web team · about a daySee the check

  3. Fail·Read

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

    llms.txt does not follow recommendations

    What to do Publish /llms.txt with your business name as its title and links to your most important pages.

    Your web team · about an hourSee the check

91

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 lists its pages for search engines (XML sitemap)ImportantFail

    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: Cloudflare found no valid sitemap at /sitemap.xml or in your robots.txt.

    • sitemap.xml not found

    How to fix it

    Publish a sitemap and name it in robots.txt.

    Fix with AI

    My website https://unphc.org/ 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 lists its pages for search engines (XML sitemap) What the grader found: Cloudflare found no valid sitemap at /sitemap.xml or in your robots.txt. Details: - sitemap.xml not found The fix, for a developer: Serve a sitemap.xml (a urlset, or a sitemapindex for several files) and add a Sitemap line with the sitemap's full address to robots.txt. Source: Build and submit a sitemap, Google: https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap; sitemaps.org protocol, XML tag definitions, sitemaps.org: https://www.sitemaps.org/protocol.html#xmlTagDefinitions 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/unphc-org/2026-11-17

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

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

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

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

53

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 · 5 of 9 goals pass

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

    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.

    What we found: llms.txt does not follow recommendations

    How to fix it

    Publish /llms.txt with your business name as its title and links to your most important pages.

    Fix with AI

    My website https://unphc.org/ 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 has a short guide for AI agents (llms.txt) What the grader found: llms.txt does not follow recommendations The fix, for a developer: Serve a Markdown file at /llms.txt with a 200, and keep it clear of any rule that sends unknown paths to the home page or a firewall page. Start it with an H1 naming the site, then sections of links to key pages, as llmstxt.org describes. Source: llms.txt audit, Chrome: https://developer.chrome.com/docs/lighthouse/agentic-browsing/llms-txt 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/unphc-org/2026-11-17

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

    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://unphc.org/ 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/unphc-org/2026-11-17

    Your web team · about a day
  • 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://unphc.org/ 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/unphc-org/2026-11-17

    Your web team · about an hour
  • AI agents can tell what your images show (alt text)ImportantFail

    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.

    What we found: Image elements do not have [alt] attributes

    • Fix any of the following: Element does not have an alt 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 has no title attribute Element's default semantics were not overridden with role="none" or role="presentation": <img decoding="async" src="data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9z…" data-spai="1" width="500" height="262" class="wp-image-42421" data-spai-target="src" data-spai-orig="/wp-content/uploads/2019/10/UNPHC-footer_logo.png" data-spai-exclude="none" data-spai-orig-obs="true">

    How to fix it

    Add a short description to every meaningful image.

    Fix with AI

    My website https://unphc.org/ 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 tell what your images show (alt text) What the grader found: Image elements do not have [alt] attributes The fix, for a developer: Give each meaningful img an alt attribute that says what it shows, an empty alt="" to decorative images, and a text name to image buttons, svg graphics and objects. Source: Image SEO Best Practices, Google: https://developers.google.com/search/docs/appearance/google-images; Understanding Success Criterion 1.1.1: Non-text Content, W3C: https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.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/unphc-org/2026-11-17

    Your web team · a few days
  • Your site sends AI agents a plain-text version of each page (Markdown)CriticalNot 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: Could not check Markdown for Agents: The operation was aborted.

  • 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)CriticalPass

    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.

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

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

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

26

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

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

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

    What we found: Accessibility tree is not well-formed

    • Links must have discernible text: <a class="et_pb_video_play" href="#">

    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://unphc.org/ fell short on one check of Clutch's Agent Grader, which tests whether AI agents can find, read and use a site. Check: AI agents can see your site's buttons and fields (accessibility tree) What the grader found: Accessibility tree is not well-formed Details: - Links must have discernible text: <a class="et_pb_video_play" href="#"> 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/unphc-org/2026-11-17

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

    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: Browser session timed out.

    • 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://unphc.org/ 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: Browser session timed out. 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/unphc-org/2026-11-17

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

    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://unphc.org/ 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/unphc-org/2026-11-17

    Your web team · a few days
  • Your text stands out clearly from its backgroundImportantFail

    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. Links rely on color to be distinguishable. [user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

    • Fix any of the following: Element has insufficient color contrast of 3.1 (foreground color: #666666, background color: #171814, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1: <p>
    • Fix any of the following: The link has insufficient color contrast of 2.08:1 with the surrounding text. (Minimum contrast is 3:1, link text: #2ea3f2, surrounding text: #666666) The link has no styling (such as underline) to distinguish it from the surrounding text: <a href="your home page">
    • Fix any of the following: user-scalable on <meta> tag disables zooming on mobile devices: <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0">

    How to fix it

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

    Fix with AI

    My website https://unphc.org/ 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. Links rely on color to be distinguishable. [user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5. Details: - Fix any of the following: Element has insufficient color contrast of 3.1 (foreground color: #666666, background color: #171814, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1: <p> 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/unphc-org/2026-11-17

    Your web team · about a day
  • 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-US" class="js js spai_has_js divibar-open">

    How to fix it

    Make every page work from the keyboard alone.

    Fix with AI

    My website https://unphc.org/ 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-US" class="js js spai_has_js divibar-open"> 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/unphc-org/2026-11-17

    Your web team · about a day
  • Other AI agents can find your own AI agent (A2A agent card)ImportantNot measured

    If your business runs its own AI agent, such as one that answers questions or takes bookings, the card lets a customer's agent find it and hand it the job, agent to agent.

    What we found: Could not fetch A2A Agent Card: The operation was aborted.

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

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

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

52

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 main content shows up quickly on phonesCriticalFail

    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 is 7.1 s for real visitors of your whole site, last 28 days, which Google rates poor. First Contentful Paint is 6.3 s for real visitors of your whole site, last 28 days, which Google rates poor. Speed Index (14.5 s). Measured from real visitors of your whole site, last 28 days; the rest is a lab test on a phone.

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

    How to fix it

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

    Fix with AI

    My website https://unphc.org/ 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 is 7.1 s for real visitors of your whole site, last 28 days, which Google rates poor. First Contentful Paint is 6.3 s for real visitors of your whole site, last 28 days, which Google rates poor. Speed Index (14.5 s). Measured from real visitors of your whole site, last 28 days; the rest is a lab test on a phone. Details: - LCP request discovery - LCP breakdown - Render-blocking requests (Est savings of 1,260 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/unphc-org/2026-11-17

    Your web team · a week or more
  • Your pages stay still while they loadCriticalFail

    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.

    What we found: Cumulative Layout Shift is 0.27 for real visitors of your whole site, last 28 days, which Google rates poor.

    • Layout shift culprits
    • Avoid large layout shifts (3 layout shifts found): <div class="et_builder_inner_content">
    • Avoid non-composited animations (13 animated elements found): <div class="et_pb_text_inner">

    How to fix it

    Stop content from moving as images and fonts load.

    Fix with AI

    My website https://unphc.org/ 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 is 0.27 for real visitors of your whole site, last 28 days, which Google rates poor. Details: - Layout shift culprits - Avoid large layout shifts (3 layout shifts found): <div class="et_builder_inner_content"> - Avoid non-composited animations (13 animated elements found): <div class="et_pb_text_inner"> 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/unphc-org/2026-11-17

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

    • Use efficient cache lifetimes (Est savings of 237 KiB), from Facebook
    • Use efficient cache lifetimes (Est savings of 237 KiB), from Facebook

    How to fix it

    Let browsers keep images, scripts and styles between visits.

    Fix with AI

    My website https://unphc.org/ 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 237 KiB) Details: - Use efficient cache lifetimes (Est savings of 237 KiB), from Facebook - Use efficient cache lifetimes (Est savings of 237 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/unphc-org/2026-11-17

    Your web team · about an hour
  • 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: Reduce unused JavaScript (Est savings of 474 KiB). Reduce unused CSS (Est savings of 13 KiB). Legacy JavaScript (Est savings of 8 KiB).

    How to fix it

    Remove code and files the page does not use.

    Fix with AI

    My website https://unphc.org/ 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: Reduce unused JavaScript (Est savings of 474 KiB). Reduce unused CSS (Est savings of 13 KiB). Legacy JavaScript (Est savings of 8 KiB). 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/unphc-org/2026-11-17

    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: Missing source maps for large first-party JavaScript.

    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://unphc.org/ 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: Missing source maps for large first-party JavaScript. 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/unphc-org/2026-11-17

    Your web team · a few days
  • 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: Your home page is served over HTTP/1.1.

    • Network Round Trip Times (0 ms)
    • Server Backend Latencies (20 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://unphc.org/ 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: Your home page is served over HTTP/1.1. Details: - Network Round Trip Times (0 ms) - Server Backend Latencies (20 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/unphc-org/2026-11-17

    Your web team · about a day
  • Your site responds quickly to taps and clicksCriticalPass

    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.

  • Images are sent at the size they are shownImportantPass

    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.

  • 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 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 18 fixes add up to about six weeks of your web team's time.

  • Send to your agency

    An email with what is wrong and a link to this report, so whoever runs the site has every fix and its line for the web team.

    Send to your agency
  • Explore with your AI

    Your own AI reads the report and tells you how to fix each issue and the effort each takes. It gets this, and nothing else:

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

Shopper in Salt Lake City, Utah

Find affordable, safe apartments for low-income families in Salt Lake City, Utah.

Find

Did a search lead the agent to you?

  1. Searched“affordable family apartments Salt Lake City low-income”

    • lowincomehousing.us
    • apartments.com
    • parkvueslc.com
  2. Searched“Salt Lake City Housing Authority apartments”

    • haslcutah.org
    • affordablehousing.com
    • rentalhousingdeals.com
  3. Openedhaslcutah.org

    The site turned the agent away

  4. Openedparkvueslc.com/affordable-housing

  5. Openedhaslcutah.org/properties

    The site turned the agent away

Find failed

Search led the agent to parkvueslc.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 tounphc.org

    The page wasn't there

  2. We sent the agent tounphc.org

    It could read the page right away: 337 words

  3. Openedunphc.org/property-listings

    It could read the page right away: 216 words

Read partly passed

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

The agent's answer

I read Utah Non-Profit Housing Corporation (UNPHC) and it's a reasonable fit for this request, though I could not confirm specific apartments or prices.

Why it fits UNPHC's own site says it focuses on affordable housing for lower-income households. At Utah Non-Profit Housing Corporation, we are dedicated to enhancing the quality of life for low and very low-income individuals and families by providing safe, affordable housing solutions. Its mission is to provide decent, safe, affordable housing, focusing on low and very low-income individuals and families.

What the site says about its services

  • It is located in Salt Lake City at 223 West 700 South Salt Lake City, UT 84101.
  • It has a pre-application process. The home page links to an Pre-application Online form and a downloadable pre-application.
  • OFFICE VISITS BY APPOINTMENT ONLY
  • The properties page has a "Property Listings" section, but the text I could read did not include any listed properties, rents, or eligibility details. I could not verify what properties it currently offers.

Next step Call (801) 364-6117 or email info@unphc.org to ask which properties are open, what income limits apply, and what the rents are. The site says the phone and email are Phone: (801) 364-6117 and Email: info@unphc.org. Because office visits are by appointment, call ahead before going in. You can also start the pre-application online or download it from the home page.

Limits of this answer

  • The home page loaded on my second attempt; the first attempt failed.
  • I did not verify the affordability, safety, or current availability of any specific unit. Ask UNPHC directly about those.

Pages relied on

Act

Could the agent do the shopper's next step?

The shopper's next request: “Help me start a pre-application for a low-income apartment and send it in.”

  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, read your site but didn't get its answer there 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

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

  3. Act

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

These sites are competing with you

SiteLetterFindReadActPerformance
unphc.orgBuilt in ClutchAFindPassesReadPassesActPassesPerformancePassesClutch rebuilds it from its address, without these issues. Free to preview.Get this site
unphc.orgFFind91Read53Act26Performance52
parkvueslc.comOpened by the AI agent

See unphc.org rebuilt, without these issues

3rd of 3 organization sites graded so far. See the board.

How we grade