Skip to content
Raptor home
Menu

Response to taps (INP)

performance.cwv_inp_needs_work
Priority
Low
Severity
Warning

What we look for

Google's data from real Chrome visits shows these pages, or the whole site where a page has too few visits, taking more than 200 milliseconds to react to a tap, click or key press (INP, Interaction to Next Paint).

Why it matters

INP is one of Google's Core Web Vitals (page experience scores), and this range, short of Poor, is rated Needs Improvement. A lag after each tap makes the page feel sluggish.

How to fix

Cut the JavaScript that runs when visitors interact: remove scripts you do not need, split long tasks into shorter ones and load third-party widgets only when they are used. Chrome's Performance panel shows your developer the slow parts.

What it cannot know

Where a page has too few visits, the figure is the whole site's, so that page may respond faster than shown.

Where you’ll see it

The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.

Terminal
When it is one of the five findings under Fix first, raptor crawl prints the id under it.
Check: performance.cwv_inp_needs_work
crawl.json and the CSV
The crawl JSON names the finding by this id, and so do the CSV and raptor_query.
"check_id": "performance.cwv_inp_needs_work"
The HTML report
This link opens the finding in the report, and each finding shows its id.
crawl.html#finding=performance.cwv_inp_needs_work
MCP
raptor_findings with this check_id returns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.
raptor_findings {
  "job_id": "...",
  "check_id": "performance.cwv_inp_needs_work"
}