Interaction to Next Paint (INP) Benchmarks by

Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital in March 2024. INP measures the latency of all user interactions throughout a page visit, not just the first one. Google considers an INP of 200 milliseconds or less as “good” and anything above 500 milliseconds as “poor.”

Why INP Is Harder to Optimize Than FID

FID only measured the delay before the browser could begin processing the first interaction. INP captures the full lifecycle of every interaction — from input to the next visual update — across the entire page session. This makes INP a far more demanding metric because it exposes slow interactions that occur after initial load, such as filtering product lists, opening menus, or submitting forms.

Many sites that passed FID with flying colors discovered they had significant INP problems. Heavy JavaScript frameworks, complex event handlers, and long main-thread tasks all contribute to poor INP scores.

How Industries Compare

E-commerce sites face substantial INP challenges with a median of 220ms. Product filtering, cart interactions, and search-as-you-type features all create complex JavaScript execution that blocks the main thread. Top performers achieve 120ms through aggressive code splitting, web workers for heavy computation, and optimized rendering pipelines.

SaaS websites perform better at 180ms median INP. While dashboards and interactive components can be complex, SaaS sites benefit from more predictable interaction patterns and often use modern frameworks with built-in performance optimizations.

Media sites have the slowest INP at 280ms median. Ad scripts competing for main-thread time, infinite scroll implementations, and video player interactions all contribute to sluggish responsiveness.

Healthcare sites sit at 210ms median, with form-heavy pages and patient portal interactions being the primary bottlenecks.

Finance sites lead with a 170ms median. Streamlined interfaces and rigorous performance standards in the financial sector drive better optimization practices.

Strategies for Better INP

Improving INP requires reducing main-thread blocking time during interactions. Key strategies include breaking long tasks into smaller chunks using scheduler.yield(), moving non-critical work off the main thread with web workers, debouncing rapid-fire events like scroll and resize handlers, and minimizing DOM manipulation during interactions. Third-party script management is also critical — audit and defer any scripts that add event listeners or run heavy callbacks.

Auditite monitors INP across all your pages using real user data, identifying specific interactions that exceed the 200ms threshold and pinpointing the JavaScript responsible for the delay.