Back to report
Signal 10 of 10

How cheaply AI can read your pages

66/100Solidhadlerinsurance.com
66/100
Solid

How cheaply AI can read your pages

This signal is usable, with a few gaps still costing visibility.

You vs peer median
Peer median 60

Why this matters

AI crawlers pay a token and compute cost to read bloated pages. When raw HTML is full of markup, scripts, and delayed client rendering, the crawler spends more budget before it reaches the facts a buyer needs.

Lighter raw-HTML pages get read more often and more cheaply. The goal is simple: useful facts should appear in the first server response, with less script hydration tax between the crawler and your offer.

The gold standard
  • Substantive business facts visible in raw HTML before client scripts run
  • HTML-to-visible-text ratio below 10:1, with clean semantic markup
  • Low script hydration tax: under 12 script tags and under 8 external script references
  • UCP, ACP, and AP2 files valid enough for agents to parse without guessing
  • ACP product feed specification present for machine-readable catalog access

What we found on your site

HTML-to-visible-text ratio28.8:1. Lower ratios mean crawlers reach useful facts with less parsing cost.
Script count35 script tag(s) and 23 external script reference(s) detected.
Hydration tax35 script tag(s), 23 external reference(s), 30,147 script byte-weight units
First fact in raw HTMLThe server response contains substantive text before scripts run.
UCP manifest validityCatalog discovery data is missing or not valid enough for reliable parsing.
ACP config validityCheckout configuration is missing or malformed.
AP2 mandates validityTrust mandates are missing or malformed.
ACP product feed specificationNo product feed specification found in the ACP configuration.

What to do next

  1. Reduce markup noise and boilerplate so the visible content is a larger share of the raw HTML response.
  2. Cut unnecessary client scripts, defer nonessential hydration, and keep buyer-critical content available before scripts execute.
  3. Validate the UCP manifest so catalog facts can be parsed directly.
  4. Validate the ACP configuration and include the required product feed specification.
  5. Publish valid AP2 mandates for trust-sensitive transactions.