The prediction is re-measured, not repeated
- Predict Every fix ships with a predicted range against field data and the arithmetic behind it.
- Prove After the client's team ships, the included re-runs measure the page again — 2 within 30 days. The comparison on your dashboard reports, finding by finding, whether the problem is still detected, judges field metrics against a stated noise floor, and marks a lone lab-score move as what it is: not proof.
- Confirm Real users decide last. CrUX aggregates a rolling 28-day window, so a real improvement surfaces as a four-week ramp; the free Core Web Vitals watch emails the day-28 verdict.
Do the predictions hold? In the published calibration pilot — 8 controlled cases — the realised saving was
never smaller than the estimate: 1.0–1.9× the prediction.
Read the pilot and its limits →
The same decision trail as JSON — schema pagespeed-audit/findings@1, excerpt with the worked example's values
{
"schema": "pagespeed-audit/findings@1",
"run": {
"binding_constraint": "field p75 TTFB 1.6 s — passing in the lab, absent from all 21 flags",
"adjudication_counts": { "confirmed": 4, "false_positive": 6, "deprioritized": 9, "platform_blocked": 2 }
},
"adjudications": [
{
"audit_id": "render-blocking-resources",
"disposition": "confirmed",
"claim": "save 2,330 ms",
"evidence": "Field p75 LCP = 2,784 ms; the lab saving is a counterfactual on a different baseline — impact recomputed against field data"
}
]
}