According to DEV Community, one site in a WordPress multisite network had spent months rated "Good" for Interaction to Next Paint (INP) on its content pages. INP measures how long a page takes to visibly respond after a click, tap or keypress. Then more than ten thousand URLs dropped to "Needs Improvement" in Google's Search Console over a short window.
The cause was a performance plugin that holds back non-critical JavaScript until a visitor first interacts with the page. It was set to defer about 400KB of script: a general-purpose front-end library and a page-builder or blocks framework bundle. A fallback timer of around fifteen seconds would load everything anyway if nobody interacted.
The author explains why this backfires for INP. The deferred code starts running at the same moment as the click or tap that INP is scoring. That much script runs as one long task on the main thread, so the browser cannot paint a response to the user's action until it finishes. The technique usually helps load metrics such as Largest Contentful Paint, but here it hurt responsiveness.
The fix had two parts. First, a step-by-step guided-view component used only on some article pages was being loaded sitewide, including on archive and listing pages where it never appears. Its assets were limited to the templates that use it. Second, the fallback timeout was cut from fifteen seconds to about three. The author admits there are no after-fix INP numbers, so the result is not measured.
Why it matters
Optimisation tools trade one metric against another. A setting that improves loading scores can make interaction scores worse, and you will miss it if you only watch the metrics it helps. INP is part of how real visitors experience your pages, so it deserves its own checks after any plugin change.
The case also offers a useful rule of thumb. When thousands of unrelated URLs regress at once, look at shared causes first, such as a plugin, a sitewide script or edge configuration, before digging into individual pages. And scripts for features that only some pages use are easy to load everywhere by accident.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.