Google measures a site's user experience with three main metrics — Core Web Vitals. From 12 March 2024 the "first input delay" (FID) metric in that trio is replaced by a new one: INP (Interaction to Next Paint).
What is INP?
FID only measured how long the very first tap waited for a response. INP looks at all of a visitor's clicks, taps and key presses on the page and reports one of the slowest responses. So the question is: "When you press a button, how quickly does the page react?"
Thresholds
- up to 200 ms — good;
- 200–500 ms — needs improvement;
- over 500 ms — poor.
The other two metrics are unchanged: LCP (loading of the main content, threshold 2.5 seconds) and CLS (visual shifts, threshold 0.1).
How to check it on your site
- PageSpeed Insights: enter the address; if real-user data exists, INP appears there.
- Google Search Console: the "Core Web Vitals" report shows groups of problem pages.
- Browser developer tools: the "Performance" tab shows long tasks.
The most common causes of slow responses
- Heavy JavaScript. Many scripts keep the browser busy and the response to a click is delayed.
- Third-party add-ons: chat widgets, tracking codes, ad scripts.
- Heavy galleries, sliders and animations.
- A very large page structure (thousands of elements).
What to do
- Remove unused scripts and plugins.
- Load third-party scripts deferred (defer/async) and question the real value of each.
- Replace heavy sliders with a simpler solution.
- Simplify long lists and forms.
- Check the metrics 3–4 weeks after a change: real-user data updates slowly.
FAQ
Does hosting affect INP? Only slightly. Server speed mostly affects LCP; INP depends more on the code and scripts on the page.
How important is the INP score? It is one of Google's page-experience signals and does not replace content quality. But a site that responds quickly also keeps its visitors.
If you would like a speed audit of your site and the fixes: website development and SEO.



