What INP means in plain English
A page can look fully loaded and still feel bad. If a customer taps “Add to cart” or “Submit” and the screen hesitates before anything happens, that lag is friction — and friction is where people give up. INP is Google’s way of measuring that hesitation across the whole time someone spends on the page, not just the first tap.
INP became an official Core Web Vital in March 2024, replacing the older First Input Delay metric, because it captures real responsiveness far better. Per Google’s web.dev guidance, a “good” INP is 200 milliseconds or less at the 75th percentile of visits; 200–500 ms needs work, and anything over 500 ms is poor. In plain terms: if your buttons feel laggy on a mid-range phone, you have an INP problem.
How INP fits with the other Core Web Vitals
INP is one of three Core Web Vitals Google uses as part of its page experience signals. They measure different things, and a site can pass one while failing another — which is why “my homepage scores well” does not mean your checkout does.
The three usual WordPress causes
Most WordPress INP problems trace back to a few repeat offenders, and they are almost all about JavaScript blocking the browser’s main thread when someone tries to interact.
- Too many plugins each loading their own scripts on every page, whether the page needs them or not.
- Third-party tags — tracking, chat widgets, heatmaps, ad scripts, popups — all competing for the same main thread.
- Optimization plugins that combine, defer, or delay JavaScript so aggressively that they break interaction timing instead of helping it.
Where to fix first
Do not start with the homepage unless it is genuinely your main conversion page. Start where customers act: checkout, quote requests, lead forms, calendar bookings, login, and account pages. A sluggish marketing page is a nuisance; a sluggish checkout is lost revenue.
The practical method, straight from web.dev’s optimize-INP guide, is to measure on a real device, find the interaction that responds slowest, and trace which script is hogging the main thread when it fires. Then cut, defer, or replace that script — and re-measure. The usual culprit is plugin sprawl, so a plugin audit often does more than any single tweak. Guessing without measuring is how stores stack five speed plugins and end up slower.
The three Core Web Vitals, in plain English
Each vital measures a different feeling, with its own “good” threshold from web.dev. INP is the one most WordPress sites quietly fail.
| Core Web Vital | What it measures | “Good” score |
|---|---|---|
| LCP — Largest Contentful Paint | How fast the main content appears (load speed). | 2.5 seconds or less |
| INP — Interaction to Next Paint | How fast the page responds when tapped or typed (responsiveness). | 200 milliseconds or less |
| CLS — Cumulative Layout Shift | How much the layout jumps around while loading (visual stability). | 0.1 or less |
Common INP mistakes on WordPress
- Judging the site by its homepage score while checkout and form pages stay slow.
- Stacking multiple caching and “speed” plugins until they fight each other and make INP worse.
- Treating INP as a hosting problem — better servers rarely fix main-thread JavaScript lag.
- Loading chat, tracking, and popup scripts on every page instead of only where they are needed.
- Optimising lab scores in a testing tool while never measuring on a real mid-range phone.
How we approach INP on a managed site
In our experience, INP work is not a one-time fix; every new plugin and tracking tag can quietly add main-thread weight. The job is to keep interaction fast on the pages that matter and to catch regressions before a customer feels them — which is why we fold it into an ongoing WordPress care plan rather than treating it as a one-off audit.
- Measure INP on real devices for checkout, lead, and booking pages, not just the homepage.
- Audit which scripts load where, and stop non-essential tags loading site-wide.
- Re-check responsiveness after every plugin or theme update that adds JavaScript.
- Be conservative with optimization plugins — one well-configured tool beats three fighting.
Frequently asked questions.
What is a good INP score?
Google treats 200 milliseconds or less as good, 200–500 ms as needing improvement, and over 500 ms as poor, measured at the 75th percentile of real visits (web.dev). Aim for under 200 ms on the pages where customers act.
Does better hosting fix INP?
Usually not by itself. INP is mostly a browser-side responsiveness problem caused by JavaScript blocking the main thread, so it is driven by scripts and plugins more than server speed. Faster hosting helps load time (LCP) more than interaction time (INP).
Can a WordPress site pass Core Web Vitals?
Yes, and plenty do. It takes disciplined plugin control, sensible caching, optimised images, script cleanup, and a well-built theme — plus ongoing checks so a future plugin does not quietly break what you fixed.
Did INP replace First Input Delay?
Yes. INP replaced First Input Delay as a Core Web Vital in March 2024 because it measures responsiveness across the whole page visit, not just the first interaction.
Research sources.
This guide was checked against current platform and search documentation before publication.