← Back to blogGLOSSARY

What is INP?

INP (Interaction to Next Paint) measures how quickly your site responds to user interactions. Since March 2024, the successor to FID as a Core Web Vital.

What is INP?

INP stands for Interaction to Next Paint. It measures the time between a user interaction — a click, tap or keystroke — and the moment the browser shows the next visual change on screen. Since March 2024, INP officially replaced First Input Delay (FID) as a Core Web Vital, because FID only measured the first interaction while INP assesses responsiveness across the entire session.

The thresholds

Google uses three clear categories, measured at the 75th percentile of your page visits:

ScoreRating
Under 200msGood
200ms – 500msNeeds improvement
Over 500msPoor

Why INP matters

INP has been an official Core Web Vital since May 2024, alongside Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS). Core Web Vitals are part of Google's broader page experience signals, which indirectly factor into ranking. More importantly: a slow INP score is something visitors feel directly — a button that responds sluggishly, a menu that stutters — and that costs conversions regardless of SEO.

How do you measure INP?

Use PageSpeed Insights or the Chrome User Experience Report (CrUX) for field data from real users — that's what matters, not Lighthouse's simulated lab data. Chrome DevTools (the Performance tab, or Performance Insights) lets you visually identify long tasks above 200ms while testing on your own device.

How do you improve INP?

Most INP problems are a JavaScript architecture issue, not something you can fix with better images or caching alone.

  1. Reduce main-thread work by removing or deferring unnecessary scripts.
  2. Split long tasks using scheduler.yield() or setTimeout(fn, 0), so the browser gets breathing room.
  3. Optimise event handlers: debounce or throttle functions that fire often, such as on typing or scrolling.
  4. Use requestIdleCallback for work that doesn't need to be visible immediately.
  5. Lazy-load third-party scripts such as chat widgets and A/B testing tools, or load them only after user interaction.

Want to know how your site scores on INP?

Request a performance check →
FREQUENTLY ASKED QUESTIONS

Need a quick answer?

What exactly did INP replace?

First Input Delay (FID), officially deprecated in March 2024. FID only measured the first interaction on a page; INP assesses the responsiveness of every interaction across the whole session.

Is INP the same as load speed?

No. Load speed is measured by Largest Contentful Paint (LCP). INP measures responsiveness during interaction, after the page has loaded — they are two different Core Web Vitals.

What score do I need for a good Core Web Vitals rating?

An INP under 200ms for at least 75% of your page visits (the 75th percentile), per Google's official definition.

What usually causes a poor INP score?

Heavy JavaScript execution on the main thread: third-party scripts, hydration in single-page apps, and expensive event handlers are the most common causes.

Can I fix INP without a developer?

To a limited extent. Small fixes like deferring scripts can sometimes be done via a page builder or plugin settings, but structural improvement usually requires code-level changes.

DIY or outsource?

Ready to apply what you just read? These are the logical next steps if you'd rather leave it to an agency.

Keep reading

In this series

Slow site, lost conversions?

Fix your INP issues
before customers drop off.

We analyse your site for long tasks and third-party scripts and improve responsiveness measurably.