What it is
Interaction to Next Paint measures how quickly the page responds when someone taps or clicks. Above 200ms it feels sluggish, and the cause is usually heavy JavaScript blocking the main thread. Interaction to Next Paint above ‘good’. Sluggish interactivity harms UX.
Why does inp > 200ms matter for AI search?
Sluggish interactivity harms UX.
How do you fix it?
Reduce long tasks; optimise event handlers.
How do you find it on your site?
- Read INP from PageSpeed Insights field data and the Search Console Core Web Vitals report.
- Reproduce slow interactions and profile the main thread in DevTools Performance.
- Break up long JavaScript tasks and defer non-essential work.
- Re-measure INP after reducing main-thread blocking.
Which ranking and citation factors does it touch?
INP replaced FID as a Core Web Vital. Responsiveness is both a ranking input and a major driver of how usable the page feels.
What is the impact?
Low-medium. Direct.
What is the evidence?
INP ‘good’ < 200ms (replaced FID in 2024). web.dev, Core Web Vitals (Google); Google Search Central, Understanding page experience in Google Search results
Sources
Frequently asked questions about inp > 200ms
What does "INP > 200ms" mean?
Interaction to Next Paint above ‘good’.
How do you fix iNP > 200ms?
Reduce long tasks; optimise event handlers.