INP in Core Web Vitals: what the new metric means for your website

  • Home
  • INP in Core Web Vitals: what the new metric means for your website
INP in Core Web Vitals: what the new metric means for your website

INP (Interaction to Next Paint) is a metric of page responsiveness. On March 12, 2024 it replaced FID in the Core Web Vitals set, as confirmed by the web.dev post on the INP launch. What does that mean for a website owner?

Basically one thing: with the INP Core Web Vitals metric, Google now rates how quickly a site responds to every click, not just the first one. Has PageSpeed Insights or Search Console shown you a new item rated “needs improvement”? You are not the only one. Below, step by step: what this measure covers, where a bad score comes from, where to check it and what to ask your contractor to do.

What is INP in Core Web Vitals and what exactly does it measure?

INP is the time from a click, a tap on the screen or a key press to the moment the browser shows a response to that action on the screen. That is all. The metric takes into account interactions from the whole visit, so the first click counts just as much as the tenth.

On a company website this will be opening a menu or typing text into a form field, in a store - using a product filter or the add to cart button. The measurement happens on its own, through a browser API, so the site does not have to report anything (which is good, one thing less to keep an eye on). We describe how this metric fits into the whole set in our article on Core Web Vitals and SEO.

INP instead of FID: what changed in March 2024

FID rated only the delay of the first interaction. INP checks responsiveness throughout the whole visit. Hence the surprise: a site with a good FID can now get a weaker rating. Chrome tools, that is PageSpeed Insights and the Web Vitals extension, show the new metric among the three main indicators, and the Core Web Vitals assessment in PageSpeed Insights itself includes it in place of its predecessor. According to the schedule given by the Chrome team, the transition period ended on September 9, 2024, and since then FID is no longer shown in these tools.

What does this mean in practice? A worse rating does not mean the site suddenly started running slower. The measure has changed. It covers more situations than before and brings to the surface delays that simply were not visible in reports earlier.

Where to check INP in PageSpeed Insights and Search Console

You will find the score in two places: in PageSpeed Insights, in the section with data from real users, and in the Core Web Vitals report in Search Console. Field data comes from the Chrome User Experience Report, for which a site has to qualify. If it qualifies, a picture for the whole domain is always available, and in some cases for a single URL as well. The thresholds for the “good”, “needs improvement” and “poor” ratings are given in the INP metric documentation on web.dev, and in my opinion that is the best reference for your readings.

But with low traffic, field data may be missing. What then? What remains is clicking through typical user paths by hand, because they show the problems best: opening the product list, filtering, adding to cart, submitting a form. Before you talk to your contractor, note down:

  • URLs or groups of URLs rated “needs improvement” or “poor”,
  • whether the problem affects mobile devices, desktops, or both,
  • which elements respond with a noticeable delay,
  • which plugins and marketing scripts were added in recent months.

What hurts page responsiveness

The main culprit is JavaScript that occupies the browser’s main thread at the very moment the user clicks something. The main thread is a queue in which the browser does most of its work: it runs scripts, recalculates the layout and paints changes. And a long task is a piece of code that runs long enough that nothing else gets handled in the meantime. The click waits. The most common sources of such blocking:

  • heavy JavaScript in the theme or application,
  • large plugins, especially page builders and add-ons loaded on every subpage,
  • third-party scripts: chat, analytics, advertising pixels, maps,
  • long tasks triggered by a click, for example reloading the entire product list,
  • a complex page structure with a very large number of elements.

The problem shows up more often on phones than on desktops. No wonder, because a weaker processor needs more time to run the same code. On sites built on WordPress, the first suspects are usually add-ons, which we cover in more detail in our guide on how to improve WordPress speed and performance.

How to improve INP: what to ask your contractor to do

In general, the point is to reduce JavaScript work and split it up, so that the browser can respond quickly to the user’s action. I recommend ordering the scope of work from the simplest things to the most time-consuming ones:

  1. Reviewing and removing unnecessary plugins and third-party scripts.
  2. Deferred loading of non-critical code, for example chat only after the first interaction.
  3. Splitting long tasks into shorter ones, between which the browser can handle a click.
  4. Simplifying click and form handling so that they show a visible response immediately.
  5. Slimming down the page structure: fewer nested elements and sections.
  6. Measuring again on field data.

You can often handle the first point yourself by turning off unused add-ons and old tracking codes. The rest is a job for a developer, especially when the site runs on a JavaScript framework - this is where the know-how that comes with frontend optimization in React and similar libraries comes in handy. Not sure where to start? A website audit can be the starting point for identifying the causes.

What to expect after the fixes

You have to wait for the effect in the reports. Field data is collected from real users over a longer period, so the chart will not move right away. The real benefit appears earlier: the menu, filters and cart respond faster, and the site is simply easier to use. The customer feels it regardless of what the tool shows.

And one more thing. Check the score after every larger deployment, because a new plugin or marketing script can undo earlier work (there is no point pretending that something done once stays done forever). So treat INP Core Web Vitals as a fixed step in signing off changes to the site: before you accept another add-on, click through the most important paths on your phone and compare the reading with the previous one.

Frequently asked questions

Will a poor INP score lower my site’s position in Google?

INP is one of the components of Core Web Vitals, and these are among the signals that describe the quality of the page experience. But there is no honest way to predict how a single metric will translate into the visibility of a specific site. Something else is certain: a slow-responding site makes it harder for users to complete the task they came for.

Why does PageSpeed Insights not show INP for my site?

Most often because the Chrome User Experience Report does not have enough data for the URL being checked. It also happens that the score is available only for the whole domain and not for a single subpage. In that case, what remains is manual testing of typical user paths.

Do I still need to deal with FID?

No. The metric is no longer part of Core Web Vitals and has been removed from Chrome tools, so its readings no longer matter. It is better to direct attention and the optimization budget to Interaction to Next Paint.

Book a free consultation

Provide your phone number or schedule a meeting