By the Seovoro Team · Last updated October 27, 2026
Key takeaways
- INP measures how quickly a page responds to clicks and taps. 200 milliseconds or less is good.
- It replaced FID as a Core Web Vital in March 2024.
- A slow INP is usually caused by too much JavaScript, especially third-party scripts.
- Remove unused scripts first, delay the rest, and test on a mid-range phone.
INP stands for Interaction to Next Paint. It measures how quickly your page reacts when someone clicks, taps or types. If a button feels laggy, your INP is probably poor.
In this guide
- What a good INP is
- How to measure it
- Why INP is slow
- The fixes that usually work
- Does INP affect rankings?
- A worked example: a laggy menu button
- A quick review of third-party scripts
- Keep it fixed
- How Seovoro can help
- FAQ
- Sources
What a good INP is
Google uses these thresholds, based on what real visitors experience:
- Good: 200 milliseconds or less
- Needs improvement: 200 to 500 milliseconds
- Poor: over 500 milliseconds
INP replaced the older FID metric as a Core Web Vital in March 2024. It looks at all interactions during a visit, not just the first one.
How to measure it
- Search Console: the Core Web Vitals report shows pages grouped as good, needs improvement or poor, using real visitor data.
- PageSpeed Insights: shows real-user data when available, plus a lab test. Try our Site Speed Tester and PageSpeed Checker.
- Chrome DevTools: the Performance panel helps you find which script blocks a click.
Note that lab tests cannot always reproduce INP, because it depends on real clicks. Field data is more reliable.
Why INP is slow
Almost always, the browser is busy running JavaScript when the visitor clicks. The page cannot respond until that work finishes. Common causes:
- Too many or too large JavaScript files.
- Third-party scripts such as chat widgets, ad tags, trackers and A/B testing tools.
- Heavy page builders and plugins.
- Slow click handlers that do a lot of work at once.
- A very large page (thousands of elements).
The fixes that usually work
- Remove what you do not need. Delete unused plugins and old tracking scripts. This is the biggest single win on most sites.
- Delay non-essential scripts. Load chat widgets and trackers after the page is ready, or only when needed.
- Break up long tasks. If you write your own code, split big jobs into smaller ones so the browser can respond in between.
- Keep click handlers light. Show the visual response first, then do the heavy work.
- Reduce page size. Fewer elements and simpler layouts mean less work per interaction.
- Test on a mid-range phone. A fast laptop hides problems your visitors will feel.
Does INP affect rankings?
Core Web Vitals are part of Google's page experience signals, but content relevance matters far more. Treat INP as a way to make your site better for visitors first. A site that feels fast tends to convert better too.
A worked example: a laggy menu button
A visitor taps the mobile menu on a shop's website and nothing happens for almost a second. The cause is that the page is still running a big script from a marketing tool, so the browser cannot respond to the tap. The fix is not to rewrite the menu. It is to find the script that is blocking it, delay it until the page is idle or remove it if it is no longer used, and test the menu again.
A quick review of third-party scripts
- List every script that loads on your key pages (the Network tab in Chrome DevTools shows them).
- For each one, ask: who added this and do we still use it?
- Remove anything you do not use.
- Delay chat widgets, pop-ups and heatmap tools until after the page is ready.
- Test again, and note the difference.
Keep it fixed
- Test after installing any new plugin or tracking tool.
- Check the Core Web Vitals report in Search Console each month.
- Look at slow pages first. A fix on a shared template improves many pages at once.
How Seovoro can help
Our website SEO audit includes speed checks, and we can fix the causes we find. Request a free review.
FAQ
Is INP the same as page load speed?
No. Load speed is how fast the page appears. INP is how fast it reacts afterward.
Why is my INP bad only on mobile?
Phones have slower processors, so JavaScript takes longer to run. That is why mobile scores are often worse.
How long until Search Console shows my fix?
The report uses a rolling window of real visits, so it can take several weeks to fully update.
Sources
- web.dev: Interaction to Next Paint (INP)
- web.dev: Optimize Interaction to Next Paint
- Search Console Help: Core Web Vitals report
Want a second pair of eyes on your website? Request a free technical SEO audit or run our free Site Audit now.
Written by Seovoro SEO Team
SEO, AEO & AI Search specialists at Seovoro. View author profile