Chrome field data reports poor Interaction to Next Paint
ShipReady received origin-level Chrome UX Report field data with an INP 75th percentile above 500 ms.
Why it matters
Poor origin-level field data is a reason to investigate representative interactions with page-level tooling.
How ShipReady detects it
What it inspects
ShipReady sends one request to the Chrome UX Report API for the scanned origin and reads interaction_to_next_paint p75 and its open-ended poor histogram bucket.
What triggers a finding
It triggers only when CrUX returns an INP p75 strictly greater than 500 ms; threshold values, the middle band, absent metrics, and no-data are not reported.
What the evidence shows
The evidence proves Google’s origin-level Chrome field dataset reported the displayed INP p75 and poor-bucket share for its trailing field-data window.
Limits of this check
This is origin-level field data, not a measurement of the scanned page or a specific interaction. ShipReady does not render the application, inspect handlers, identify cause, or guarantee data exists for low-traffic origins.
Without CRUX_API_KEY the check is inert; API failures are incomplete and no field data produces no finding.
How to fix it
Review the observed evidence
Use representative interaction traces and browser performance tooling to find relevant work on affected pages and devices.
How to verify the change
Verify the intended behavior
Recheck the deployed origin’s field data after sufficient traffic and compare it with controlled page-level investigation.
Expected: The origin-level INP p75 moves out of the poor band.