INP replaced FID. What it means for your WordPress site
Interaction to Next Paint became a Core Web Vital in March 2024. What it measures, why WordPress sites often fail it, and the fixes that move the number.
For a few years, the responsiveness part of Google's Core Web Vitals was First Input Delay. Most WordPress sites passed it without trying, which was part of the problem: it only measured the delay before the browser started handling the very first tap or click, not how long the page took to respond.
On 12 March 2024, Interaction to Next Paint (INP) replaced it. Chrome had been testing INP since 2022, and Google announced the switch in May 2023, so it was not a surprise. It is, however, a much harder test.
What INP measures
INP watches every click, tap and key press during a visit and records how long it takes until the screen visibly updates in response. The reported value is close to the worst of those interactions. Google's thresholds, measured at the 75th percentile of real visits:
- Good: 200 milliseconds or less
- Needs improvement: up to 500 milliseconds
- Poor: more than 500 milliseconds
The key word is real. INP comes from the Chrome User Experience Report, which collects data from actual Chrome users on actual phones. A fast laptop on office Wi-Fi tells you very little about it.
Why WordPress sites struggle with it
INP is mostly about JavaScript. When the browser's main thread is busy running a script, it cannot respond to the visitor. On a typical WordPress site the usual suspects are:
- Page builders that ship a lot of script for menus, sliders and animations, even on pages that use none of them.
- Third-party tags: chat widgets, heatmaps, ad and social pixels. Each one is small; together they keep the main thread busy.
- Heavy menus and filters that rebuild large parts of the page on every click.
- Consent banners that block the page while they load.
A phone that is three or four years old feels all of this far more than your test device.
Fixes that move the number
- Measure with real data first. Search Console's Core Web Vitals report and PageSpeed Insights' field data show INP from real visitors. Lab tools such as Lighthouse cannot measure it directly; they use Total Blocking Time as a stand-in.
- Delay what can wait. Chat widgets and tracking pixels rarely need to load before the visitor does anything. Loading them on the first interaction, or a few seconds after the page settles, often makes the biggest single difference.
- Remove scripts where they are not used. A contact form plugin that loads its script on every page is a common culprit. Load it only on the contact page.
- Defer the rest. Scripts that do not affect the first view can be deferred so they run after the page is parsed.
- Check the theme and builder settings. Many builders have options to load fewer features; few sites ever change them.
Do one change at a time and watch the field data for a couple of weeks. INP responds slowly because it is collected over 28 days.
Where Ironhelm fits
Ironhelm's real-user speed feature measures Core Web Vitals, including INP, in your visitors' browsers and shows which pages are slow on phones. Scripts and styles can defer scripts and hold back chat widgets and pixels until the visitor interacts, and the asset manager shows every script a page loads so you can switch off the ones it does not use.
Sources
- web.dev, Interaction to Next Paint (INP)
- web.dev, Interaction to Next Paint is officially a Core Web Vital (March 2024)
- Google Search Central Blog, Introducing INP to Core Web Vitals (May 2023)
- web.dev, Web Vitals
Ironhelm Suite is one WordPress plugin for security, speed, SEO and analytics. See plans or tour the features.