Core Web Vitals
What is INP?
Interaction to Next Paint measures how long the page takes to respond visually after a visitor clicks, taps, or types. It replaced First Input Delay as the Core Web Vitals responsiveness metric.
Plain-English version
How quickly the page responds to taps and clicks.
Target
Under 200ms
INP thresholds
Use thresholds as a triage tool. Field data matters most when there is enough real Chrome traffic for the page.
Good
≤ 200ms
Needs work
200–500ms
Poor
> 500ms
Why it matters
What a visitor feels when INP is bad.
Why INP matters
INP is what makes a site feel responsive or stuck. Slow interactions are especially painful on mobile, checkout pages, filters, menus, and forms.
What a poor result usually means
A poor INP usually means JavaScript is keeping the main thread busy, third-party scripts are doing too much work, event handlers are expensive, or rendering after an interaction is heavy.
nimo audit lens
How nimo reads INP in an audit.
The glossary explains the metric. The free audit checks the page, separates field data from lab diagnostics, and points at the first review step.
How nimo interprets it
nimo treats INP as an interaction bottleneck after the page loads, especially on menus, filters, forms, and checkout steps.
Source to trust first
Trust CrUX INP when available. Use Lighthouse long tasks and TBT as lab clues because one Lighthouse run cannot replace field INP.
Evidence to inspect
- Field INP by device when Chrome data is available.
- Long tasks and script work around interaction-heavy moments.
- Third-party scripts active during clicks, taps, or typing.
- Hydration and component rerenders after user input.
First fix to review
Reduce the work triggered by the slowest user action before trimming unrelated JavaScript.
How to validate
Rerun lab diagnostics to check TBT and long tasks, then validate INP with field data after enough Chrome traffic is collected.
What to fix first
Do not chase the score. Fix the bottleneck.
The right fix depends on the metric, the page template, and whether the issue appears in real visitor data.
- Find the slowest interactions, not just the largest JavaScript files.
- Break up long tasks and defer non-critical JavaScript.
- Reduce third-party script work during interaction-heavy moments.
- Move expensive work off the main thread where possible.
- Simplify components that re-render too much after clicks or typing.
How nimo helps
Run the free audit, then ask: “Why is my INP high and how can I improve responsiveness?”
nimo connects responsiveness warnings to real visitor data and helps separate one noisy script from the interaction that users actually feel.
No signup needed. Takes about 30 seconds.