INP for agencies: how to explain and fix responsiveness.

Clients hear "Core Web Vitals" and assume it is one number. Here is how to explain Interaction to Next Paint in plain words, and what usually fixes it.

Key takeaways

  • INP measures how quickly a page responds to all clicks, taps and key presses.
  • It officially replaced FID as a Core Web Vital in March 2024.
  • Good is 200 ms or less at the 75th percentile; over 500 ms is poor.
  • Heavy JavaScript, third-party scripts and large DOMs are the usual causes.

What is INP?

Interaction to Next Paint measures how long a page takes to show a visual response after a user clicks, taps or types, across the whole visit rather than only the first interaction. A low INP means the page feels quick when people use menus, forms and filters. It became an official Core Web Vital in March 2024.

web.dev announced that INP is officially a Core Web Vital, replacing First Input Delay, and Google explains how the metrics relate to Search in Understanding Core Web Vitals.

What is a good INP score?

200 milliseconds or less is good, between 200 and 500 milliseconds needs improvement, and more than 500 milliseconds is poor. The score is taken at the 75th percentile of page views, so most real visitors must have a fast experience, not just the fastest devices on the fastest connections.

Thresholds come from the web.dev INP article.

How to measure it for a client

  • Search Console: the Core Web Vitals report groups URLs with poor INP from real users.
  • PageSpeed Insights: shows field data when the site has enough traffic.
  • Browser DevTools: record an interaction to see which script blocks the main thread.

Which fixes usually improve INP?

Breaking long JavaScript tasks into smaller ones, removing or delaying third-party scripts such as chat widgets and trackers, reducing the size of the page's DOM, and avoiding heavy work inside click handlers. On WordPress and Shopify sites, unused plugins and apps are a frequent cause worth checking first.

How to explain it to a client

Use one sentence: "When someone taps a button on your site, it should react almost instantly; right now it sometimes lags." Show the Search Console report, list the two or three scripts responsible and give a plan. Avoid promising a ranking jump; speed is one signal among many. Technical work is covered in white label technical SEO, the full audit in the technical SEO audit checklist, and site rebuilds in the redesign SEO checklist. See the white label SEO services page for the partner model.

Frequently asked questions

Did INP replace FID?

Yes. INP officially replaced First Input Delay as a Core Web Vital in March 2024.

What is a good INP?

200 milliseconds or less at the 75th percentile of page views.

Will fixing INP raise rankings?

It improves user experience and is one signal among many; no ranking result is guaranteed.

What causes poor INP most often?

Long JavaScript tasks, third-party scripts and very large pages.

Do you fix INP for our clients?

Yes, as part of technical SEO, delivered under your agency's brand.

Juan José Giraldo, senior white label SEO specialist

About the author

Juan José Giraldo is a senior SEO specialist with 5+ years of experience. He works on technical and local SEO for 600+ US car dealerships and supervises the SEO of 18 US e-commerce stores. He runs White Label SEO LATAM from Medellín, Colombia, and delivers white label SEO for agencies in the US, UK, Canada and Australia. Read more · LinkedIn.

Sources

  1. web.dev, Interaction to Next Paint (INP)
  2. web.dev, Interaction to Next Paint is officially a Core Web Vital (March 12, 2024)
  3. Google Search Central, Understanding Core Web Vitals

Ready to test a pilot client?

Book a 30-minute call. You get an honest read on fit, scope and price, with no obligation.