Understanding the 0–100 Readiness Score
The score is not a vibe. It is a weighted sum of capability checks, and each point maps to a fix you can ship.
Every audit ends with a number between 0 and 100. It is not a branding exercise — it is a weighted aggregate of the capability checks run against the rendered page, designed so a single number can track progress across deploys.
What the score is
The scanner starts at 100 and deducts for failing checks. Critical failures remove the most, because they stop an agent from completing a task outright. Warnings remove less, and optimizations nudge the final few points.
| Severity | Weight | Example |
|---|---|---|
| Critical | Heavy | Empty page without JS, unlabeled inputs, missing title |
| Warning | Medium | Missing alt text, dead links, no main landmark |
| Optimization | Light | Semantic nav, heading polish |
Severity bands
- 85+ — Agent-ready: core actions, labels, and structure are legible.
- 60–84 — Needs work: several barriers block common flows.
- Under 60 — High friction: critical gaps make automation unreliable.
Reading your own score
Treat the score as a ranked backlog. Fix the criticals first — each one is typically a one-line markup change — and the number moves fast. Re-run the audit to confirm, and keep a saved copy to watch the trend over time.
See what agents read on your own site.
Run a free scan of any page and get a 0–100 readiness score with copy-pasteable fixes.