What Is INP (Interaction to Next Paint) and How to Improve It in WordPress

You have optimized your images, enabled caching, and yet the site still “feels” slow when someone taps a button or opens the menu. This is where INP comes in, and if you are wondering how to improve INP in WordPress, the good news is that almost every cause is known and fixable. INP (Interaction to Next Paint) measures how quickly your site responds visually to a visitor’s real actions, not just how fast it loads the first time.

What INP is and why it replaced FID

INP is one of the three Core Web Vitals and, since March 2024, it has replaced the old FID (First Input Delay). The difference matters: FID measured only the delay of the first interaction, while INP tracks all interactions during the visit and reports, in practice, the slowest one.

In other words, INP reflects how “responsive” the site feels throughout the whole session: every click, tap, or key press. Poor INP is exactly why a site that “loads fast” can still feel sluggish the moment you interact with it.

How INP is measured and what a good score means

INP is measured in milliseconds and takes the slowest relevant interaction into account. Google uses three clear thresholds worth remembering:

• Under 200 ms — good, interactions feel instant.
• Between 200 and 500 ms — needs improvement, the user senses hesitation.
• Over 500 ms — poor, the site feels stuck or “frozen”.

Every interaction has three phases: input delay, processing time, and the presentation delay until the next paint. The diagram below shows exactly this path.

Why WordPress struggles with INP

In WordPress, the main culprit is almost always JavaScript. “All-in-one” themes, page builders like Elementor, and dozens of plugins add scripts that run on the main thread. When the user taps something, the browser must first finish its current work and only then respond.

Sliders, popups, live chats, tracking scripts, and third-party widgets are the usual suspects. Any piece of JavaScript that blocks the main thread for more than 50 ms creates a “long task” that delays the next paint. On a mid-range phone, where the CPU is slower, the effect becomes clearly visible.

How to improve INP in WordPress, step by step

The question “how to improve INP in WordPress” actually has a fairly direct answer: reduce and control JavaScript. You do not need complicated rewrites — a few well-chosen steps move the score from red to green:

• Reduce the number of plugins — remove those that load scripts across the whole site even though you use them on a single page.
• Defer and lazy-load JavaScript — with LiteSpeed Cache or a similar plugin you can delay non-essential scripts until after the first interaction.
• Drop heavy third-party scripts — load GA4 tracking late and remove widgets you do not use.
• Break up long tasks — if you have custom code, yield to the main thread periodically so the browser can respond between operations.
• Choose a lightweight theme — a clean Astra child theme runs far less code than an overloaded template.

If you want a complete approach that ties INP to the rest of the metrics, see our WordPress speed optimization guide — there we handle LCP, CLS, and INP together, because they influence each other.

Test in the field, not just in the lab

One essential detail: INP is a “field” metric (field data). Lighthouse gives you a lab estimate, but the real score comes from CrUX data, collected from real users over the last 28 days. Tools such as the official INP documentation on web.dev and PageSpeed Insights show you the real value from the field.

Common mistakes that hurt INP

A few traps show up again and again on WordPress sites. It is worth avoiding them from the start:

• Combining every JS file into one huge bundle that blocks the main thread on the first interaction.
• Running heavy animations at the exact moment of a click.
• Ignoring mobile testing — on desktop everything looks fast while the real problem stays hidden.

How to check your progress after optimizing

After each change, measure again and compare. Do not rely on a single run: INP varies with the device and with how much the visitor interacts. Test on a real, mid-range phone, because that is where the biggest delays appear. Repeat the test a few times and follow the trend, not one isolated value.

If the score stays stubbornly high and you cannot find the source, we can run a free audit that pinpoints exactly which scripts are blocking the main thread.

Conclusion

INP is the metric that most faithfully shows how pleasant your site feels in real use. In WordPress, almost everything comes down to controlling JavaScript: fewer plugins, deferred scripts, and a lightweight theme. Make the changes one at a time, measure in the field, and you will watch interactions become instant — and your visitors stay.