Your site loads fast, but Search Console still flags pages with “INP issue: longer than 200ms”. Visitors tap a menu or a button, and nothing happens for a moment. That delay costs you trust, and sometimes it costs you the lead.
I fix slow WordPress and Next.js sites for small businesses, and INP is the metric owners find hardest to understand. This guide explains how to improve INP score step by step, starting with the fixes that usually help most.
Quick answer: To improve INP score, find the slow interactions in field data first. Then remove or delay heavy third-party scripts, reduce JavaScript that runs on page load, and break long tasks into smaller pieces. Show visual feedback right away and move non-urgent work until after the next paint.
What INP Measures and What a Good Score Looks Like
Interaction to Next Paint (INP) measures how long a page takes to show a visual response after a click, a tap or a key press. Scrolling and hovering don’t count. It became a Core Web Vital on March 12, 2024, replacing First Input Delay.
According to web.dev, Google judges INP at the 75th percentile of page visits:
| INP value | Rating |
|---|---|
| 200 ms or less | Good |
| 201 to 500 ms | Needs improvement |
| Over 500 ms | Poor |
Every interaction has three parts, and each needs a different fix:
- Input delay: the browser is busy with other work, so your code can’t start yet.
- Processing time: your event handlers run.
- Presentation delay: the browser calculates layout and paints the new frame.
Find the Slow Interactions First
Don’t start deleting plugins at random. Before you decide how to improve INP score on your site, find out which pages and which clicks are slow.
- Google Search Console. Open the Core Web Vitals report and look for groups of URLs with INP issues. Similar pages usually share the same template, so one fix can clear many URLs.
- PageSpeed Insights. Check the field data at the top of the report for real INP values on mobile and desktop.
- Chrome DevTools. Open the Performance panel, record, and click the element you suspect. Long tasks show as blocks with red corners.
- Real user monitoring. If you have traffic, a RUM tool tells you exactly which element caused the slow interaction.
One warning: a Lighthouse lab test can’t measure INP, because no real person clicks anything during the test. A 95 Lighthouse score doesn’t mean your INP is good.
How to Improve INP Score: 9 Proven Fixes
1. Remove or Delay Third-Party Scripts
Chat widgets, heatmaps, ad tags, review widgets and several tracking pixels all compete for the main thread. On small business sites, they’re one of the most common causes of input delay. Remove the tools nobody uses, and load the rest after the page becomes interactive.
2. Cut JavaScript That Runs on Page Load
Every script the browser parses and runs early can block the first taps. On WordPress, deactivate unused plugins and stop plugins from loading their scripts on pages that don’t need them. On Next.js, split code so each page loads only what it uses.
3. Break Up Long Tasks
A long task is any task over 50 ms, and while it runs, the browser can’t respond. Split big functions into smaller steps and yield to the main thread between them. Chrome’s scheduler.yield() guide shows the method, with a setTimeout fallback for browsers that don’t support it yet.
4. Show Feedback First, Do the Heavy Work Later
When someone clicks “Add to cart”, update the button right away, then send analytics events and run other background work after the next frame. The visitor sees an instant response, and that visible response is what INP measures.
5. Avoid Layout Thrashing
If your code changes styles and then reads sizes like offsetHeight in the same task, the browser must calculate layout again and again. Group your reads together, then your writes.
6. Keep the DOM Small
Big pages with thousands of elements take longer to render after each interaction. Page builders often wrap one line of text in many nested containers. Simplify heavy sections, and use the CSS content-visibility property for long pages so off-screen content renders later.
7. Debounce Search Boxes and Filters
A live search box that runs a full update on every key press is a classic INP problem. Wait until the person pauses typing before running the expensive update.
8. Replace Heavy Sliders, Menus and Pop-ups
Sliders, animated mega menus and pop-up builders often attach large scripts to every tap. A simple CSS menu or a static hero image is usually faster, and it rarely hurts conversions.
9. Move Heavy Calculations to a Web Worker
Price calculators, filtering of large lists and data processing can run in a web worker, away from the main thread. The page stays responsive while the work happens in the background.
Which Fix to Try First
The quickest way to work out how to improve INP score on a specific page is to match the symptom to the phase. It saves hours of guessing:
| What you see | Likely phase | Start with |
|---|---|---|
| Slow taps in the first seconds after load | Input delay | Fixes 1 and 2 |
| One button is always slow | Processing time | Fixes 3, 4 and 9 |
| Slow typing in a search or form field | Processing time | Fix 7 |
| Slow response on long, complex pages | Presentation delay | Fixes 5, 6 and 8 |
After you ship a fix, be patient. Search Console and PageSpeed Insights field data come from the Chrome UX Report, which uses a rolling 28-day window, so improvements show up gradually.
If you’d rather have someone find and fix the problem for you, my website speed optimization service covers INP, LCP and CLS together.
Frequently Asked Questions
What is a good INP score?
A good INP score is 200 milliseconds or less, measured at the 75th percentile of page visits. Between 200 and 500 milliseconds needs improvement, and anything above 500 milliseconds is poor. Aim to keep mobile INP under 200 milliseconds, because phones have slower processors and usually show the worst results.
Does INP affect Google rankings?
Yes, but only as one part of page experience. Google says Core Web Vitals are used by its ranking systems, but helpful, relevant content matters much more. A better INP won’t rescue weak content, although it can help when competing pages are similar. It also improves how visitors feel about your site.
Why is my INP poor when my PageSpeed score is high?
The PageSpeed performance score comes from a lab test that loads the page without real clicks, so it can’t measure INP. INP comes from real visitors interacting with your pages. Scripts that run after load, like chat widgets, pop-ups and trackers, often cause slow interactions that a lab test never sees.
How long does it take for INP improvements to show in Search Console?
Search Console uses Chrome UX Report data collected over the previous 28 days. After you fix the problem, the numbers improve gradually as new visits replace old ones. Expect about four weeks before the change is fully visible, then use the Validate Fix button to confirm the issue is resolved.
Can WordPress sites pass INP?
Yes. Many WordPress sites pass INP easily. The usual problems are too many plugins, heavy page builders and third-party scripts, not WordPress itself. Removing unused plugins, delaying scripts and replacing heavy sliders or menus fixes most cases. A lightweight theme also helps a lot.
Final Thoughts
Learning how to improve INP score is mostly about respecting the main thread. Measure real interactions first, cut the scripts you don’t need, split long tasks and show feedback before doing heavy work. Most sites pass after a few focused fixes, not a full rebuild.
If Search Console keeps flagging your pages, I can check what’s slowing them down in a technical SEO audit. You can also send me a message with your URL, and I’ll tell you where I’d start.
Comments
Be the first to share your thoughts or ask a question.
Leave a comment
Your email will not be published. Comments appear after review.