DeltaV Digital
Back to Glossary

Interaction to Next Paint (INP)

Interaction to Next Paint (INP) is a Core Web Vitals metric that measures the time between a user’s interaction with a page (clicks, taps, or key presses) and the moment the browser visually updates in response, capturing the worst-case responsiveness a visitor actually experiences during their session.

What Interaction to Next Paint Means in Practice

INP replaced First Input Delay (FID) as the official responsiveness metric in Google’s Core Web Vitals in March 2024. The change wasn’t cosmetic. FID only measured the delay before the browser *started* processing the first interaction on a page. INP measures the full latency of *every* interaction throughout a session and reports the worst one (with some outlier adjustment). That’s a fundamentally different lens on responsiveness, and it caught a lot of sites off guard.

Here’s the distinction that matters. A page could pass FID with flying colors because the first click happened before any heavy JavaScript loaded. But if the fifth or tenth interaction triggered a layout recalculation, a long-running script, or a forced synchronous reflow, the user would feel that lag. FID ignored it. INP doesn’t.

In practice, INP is most relevant for pages where users do things: navigate menus, fill out forms, open accordions, filter product listings, interact with maps, or click through image galleries. A static blog post with no interactive elements will almost always have a good INP score because there’s nothing to interact with. An ecommerce product page with filters, variant selectors, and add-to-cart buttons is where INP problems surface. A healthcare provider directory with location search, insurance filtering, and appointment booking modals is another common offender.

The threshold for a “good” INP score is 200 milliseconds or less. Between 200ms and 500ms is classified as “needs improvement.” Anything above 500ms is “poor.” These thresholds are measured at the 75th percentile of page loads in the Chrome User Experience Report (CrUX), meaning Google evaluates INP based on real user data, not lab simulations. Your Lighthouse score in a development environment won’t tell you what your actual visitors experience.

One common misconception is that INP is purely a front-end development concern. It’s not. INP problems frequently originate from third-party scripts (analytics tags, chat widgets, ad scripts, consent management platforms) that hijack the main thread during user interactions. A marketing team that adds a new tracking pixel or a customer support team that installs a live chat tool can degrade INP without anyone on the development team touching a line of code.

Another point of confusion is the relationship between INP and page speed. Page speed (and its related metric, Largest Contentful Paint) measures how fast content *loads*. INP measures how fast the page *responds* after it’s loaded. A page can load in under two seconds and still have terrible INP if the JavaScript running on that page blocks the main thread when users try to interact with it. These are related but distinct performance dimensions, and optimizing for one doesn’t automatically fix the other.

Why Interaction to Next Paint Matters for Your Marketing

INP directly affects whether your website converts visitors into leads, patients, or customers. When a user clicks a “Book Appointment” button and nothing happens for 400 milliseconds, they don’t think “the browser is processing my request.” They think the button is broken, and they click again, or they leave. That friction compounds across every interaction on every page for every visitor.

Google’s own research on web performance shows that sites meeting all three Core Web Vitals thresholds (including INP) are significantly less likely to see users abandon a page before completing their intended task. For businesses running paid media campaigns to landing pages, poor INP means you’re paying to send traffic to a page that frustrates users at the moment of conversion. That’s not a technical problem. That’s a revenue problem.

The business case becomes more concrete when you consider that INP is now a ranking signal. Google confirmed that Core Web Vitals, including INP, are part of the page experience signals used in search ranking. A site with poor INP won’t get penalized into oblivion, but when two pages are otherwise comparable in content quality and relevance, the one with better Core Web Vitals has an edge. Over hundreds of pages and thousands of keywords, that edge compounds. We cover the full relationship between performance metrics and search visibility in our analysis of website speed and SEO.

How Interaction to Next Paint Works

INP works by observing every discrete interaction a user performs during a page visit and measuring the time from the input event to the next frame the browser paints in response. The metric considers three phases for each interaction.

Input delay is the time between the user’s action and when the browser’s event handler starts running. If the main thread is busy executing another task (a long JavaScript function, a layout recalculation, or a third-party script), the input sits in a queue. This is where most INP problems originate.

Processing time is how long the event handler itself takes to run. If a click triggers a complex state update, an API call with synchronous rendering, or a heavy DOM manipulation, processing time stretches. Frameworks that batch state updates and use virtual DOMs (React, Vue) can help here, but only if the component logic is efficient.

Presentation delay is the time from when the event handler completes to when the browser actually paints the updated frame to the screen. This phase includes style recalculation, layout, and compositing. Forced reflows (where JavaScript reads a layout property immediately after changing one) are a frequent cause of long presentation delays.

INP doesn’t just capture the single worst interaction. It uses a formula that selects the interaction with the highest latency, with one outlier excluded per 50 interactions. For most sessions, this effectively reports the worst interaction. For very long sessions with many interactions, it provides a slightly more forgiving measure that still reflects real responsiveness problems.

What separates good INP from bad INP comes down to main thread management. Sites with good INP keep long tasks off the main thread by breaking work into smaller chunks (using requestIdleCallback, setTimeout, or the newer scheduler.yield()), deferring non-critical JavaScript, and minimizing the number of third-party scripts that compete for execution time. Sites with poor INP typically have one or more of these problems: render-blocking JavaScript that hasn’t been deferred, bloated third-party tag managers with dozens of scripts, event handlers that trigger expensive layout recalculations, or heavy client-side rendering without proper code splitting.

External Resources

Frequently Asked Questions

What is Interaction to Next Paint in simple terms?

Interaction to Next Paint (INP) measures how quickly your website responds when someone clicks, taps, or types. It looks at every interaction a visitor makes during their session and reports the slowest one. A good INP score is 200 milliseconds or less, meaning the page visually updates within a fifth of a second after the user acts. If your site regularly exceeds that threshold, visitors are experiencing noticeable lag that feels like the page is frozen or unresponsive.

Why did Google replace FID with INP?

First Input Delay (FID) only measured the delay before the browser started processing the very first interaction on a page. That meant a page could score well on FID even if every subsequent interaction was sluggish. INP captures responsiveness across the entire session, giving a more accurate picture of what users actually experience. Google made INP the official Core Web Vitals responsiveness metric in March 2024 because it better reflects real-world usability.

How do I check my site’s INP score?

You can check INP through several tools. Google PageSpeed Insights shows field data (real user measurements from CrUX) alongside lab data for any URL. Google Search Console’s Core Web Vitals report shows INP status across your entire site, grouped by “good,” “needs improvement,” and “poor.” For page-level debugging, Chrome DevTools’ Performance panel lets you record interactions and identify which event handlers are causing long delays. The field data in PageSpeed Insights and Search Console is what Google actually uses for ranking, so prioritize those numbers over lab-only tools like Lighthouse.

How does INP relate to website optimization services?

INP is one of the three Core Web Vitals that Google uses as page experience signals for search ranking. Optimizing INP requires a combination of front-end performance engineering (main thread management, JavaScript optimization, third-party script auditing) and ongoing monitoring to catch regressions. DeltaV’s website optimization services include Core Web Vitals diagnosis and remediation as part of the technical performance layer, ensuring that performance improvements compound across your entire site rather than degrading page by page as new features and scripts are added.

Does INP affect mobile and desktop rankings differently?

Google evaluates Core Web Vitals separately for mobile and desktop. Mobile INP scores are typically worse because mobile devices have less processing power and are more susceptible to main thread congestion from heavy JavaScript. Since Google uses mobile-first indexing for most sites, your mobile INP is the score that matters most for rankings. A site that passes INP on desktop but fails on mobile still has a Core Web Vitals problem in Google’s eyes.

Is a perfect INP score necessary for good SEO?

No. Core Web Vitals, including INP, are one signal among many in Google’s ranking algorithm. Content relevance, E-E-A-T, backlink authority, and topical depth carry more individual weight. But Core Web Vitals act as a tiebreaker and a compounding factor. If your content is competitive and your INP is consistently “good” (under 200ms) while a competitor’s is “poor” (over 500ms), that difference contributes to your ranking advantage over time. The goal isn’t perfection. It’s consistently meeting the “good” threshold across your pages.

Related Resources

Related Glossary Terms

  • Core Web Vitals: Google’s set of three page experience metrics (LCP, INP, CLS) that measure loading, interactivity, and visual stability. INP is the interactivity component, replacing FID in March 2024.
  • Page Speed: The broader measure of how fast a page loads and becomes usable. Page speed encompasses multiple metrics including INP, but INP specifically isolates post-load responsiveness rather than initial load time.
  • Largest Contentful Paint (LCP): The Core Web Vitals metric that measures loading performance by tracking when the largest visible content element finishes rendering. LCP measures how fast content appears; INP measures how fast the page responds after content is visible.
  • Cumulative Layout Shift (CLS): The Core Web Vitals metric that measures visual stability by tracking unexpected layout shifts during a page visit. CLS and INP are both session-level metrics, but CLS measures visual stability while INP measures interactivity.