Back to report
Signal 10 of 10

How cheaply AI can read your pages

33/100Needs workwww.onemagicalweekend.com
33/100
Needs work

How cheaply AI can read your pages

This signal needs work before it can reliably support buyer discovery.

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 ratio97.4:1. Lower ratios mean crawlers reach useful facts with less parsing cost.
Script count1 script tag(s) and 0 external script reference(s) detected.
Hydration tax1 script tag(s), 0 external reference(s), 3,244 script byte-weight units
First fact in raw HTMLThe raw server response lacks enough fact-bearing text for low-cost parsing.
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. Move the first useful business facts into server-rendered HTML so crawlers do not need scripts to understand the page.
  2. Reduce markup noise and boilerplate so the visible content is a larger share of the raw HTML response.
  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.