What this means. The typical site is just slower than Google wants. Servers are slow to answer: only 13 of 57 send the first byte within Google’s 0.8-second target (web.dev). 42 of 79 homepages weigh more than 4 MB. For scale, the median mobile home page on the web was 2.6 MB in July 2025, so these pages carry more than one and a half times the typical load (HTTP Archive Web Almanac 2025). We did not prove that weight causes the slow loads: heavy and light sites had similar load times.
Accessibility. 47 of 79 sites have at least one critical accessibility error (a missing form label, an unnamed button, a broken ARIA reference). That is in line with the web as a whole: WebAIM’s February 2026 scan of the top one million home pages found WCAG failures on 95.9% of them, 56.1 errors per page on average (WebAIM Million 2026).
Can an AI assistant read the site? 45% of B2B buyers used AI during a recent purchase (Gartner, 2026) and 10% of engineers already list generative AI among the places they routinely look for product information (GlobalSpec 2025, p. 11). We ran Google’s own check for this, the Lighthouse “agentic browsing” audit (Chrome for Developers). It looks at the accessibility tree, the page structure a machine reads, which Google calls the agent’s “primary data model” (17 of 79 pass), and for an llms.txt file, a short text summary of the site at its root (12 of 79 have one). One caveat: llms.txt is a community proposal (llmstxt.org); Lighthouse checks for it, but Google’s John Mueller said in June 2025 that “no AI system currently uses llms.txt” (Search Engine Roundtable). We report it because Google’s audit does; it is a cheap signal, not a proven ranking factor.