Interaction to Next Paint (INP)
The Core Web Vital that measures how quickly a page responds when someone clicks, taps or types.
The Definition
Interaction to Next Paint (INP) measures the delay between a user interaction (a click, tap or key press) and the next frame the browser paints. It looks at all interactions during a visit and reports one of the slowest. INP replaced First Input Delay (FID) as a Core Web Vital in March 2024.
Why It Matters
INP is one of the three Core Web Vitals Google uses in its page experience signals. A good score is 200 ms or less; above 500 ms is poor. Google judges it on real-user field data at the 75th percentile, so a page that feels fast on your laptop can still fail on mid-range phones.
Best Practices
Break up long JavaScript tasks (over 50 ms) so the main thread can respond between them
Defer or remove third-party scripts that run on every interaction, such as chat widgets and tag managers
Give instant visual feedback (a pressed state or spinner) before doing heavy work
Avoid large DOM updates on input; update only what changed
Judge INP on field data (CrUX or Search Console), not a single lab run
Mistakes to Avoid
- 1
Still optimizing for FID, which Google retired in March 2024
- 2
Testing only on a fast desktop when most visitors use mid-range phones
- 3
Measuring page load only; INP is about interactions after the page has loaded
- 4
Adding heavy event handlers to scroll, input or resize without debouncing
Audit Checks
How Digispot AI identifies and fixes related issues
The page is slow to respond when a visitor interacts with it — taps, clicks and key presses lag (Interaction to Next Paint, or INP, over 200ms).
Impact: INP is a Core Web Vital and Google ranking signal; a laggy interaction makes the page feel broken and drives visitors away.
Break up long JavaScript tasks so the main thread can respond sooner. • Defer or remove scripts that aren't needed for the first interaction. • Move heavy computation off the main thread (web workers).
The biggest thing on the page — usually the hero image or main heading — takes more than 2.5 seconds to appear (its Largest Contentful Paint, or LCP).
Impact: Google uses LCP as a ranking signal, and visitors often leave before a slow page finishes loading.
Compress the largest above-the-fold image and serve it as WebP or AVIF. • Preload that hero image and your main web font so they load first. • Remove or defer render-blocking scripts and CSS.
It takes too long for the first piece of content to appear (slow First Contentful Paint).
Impact: A blank screen for too long makes visitors think the page is broken and leave.
Remove render-blocking CSS and JavaScript. • Reduce server response time. • Inline the critical CSS the first view needs.
The page is busy running JavaScript for too long while loading, blocking interaction (high Total Blocking Time).
Impact: During that time clicks and taps don't respond, which frustrates users and hurts your Core Web Vitals.
Break up long JavaScript tasks into smaller chunks. • Defer or remove scripts that aren't needed at load. • Move heavy work off the main thread (web workers).
Content jumps around as the page loads — buttons or text shift under the reader (a high Cumulative Layout Shift, or CLS, over 0.1).
Impact: Layout jumps frustrate visitors with mis-clicks and lower your Google ranking.
Set explicit width and height on every image and video. • Reserve space for ads, embeds, and banners before they load. • Avoid inserting content above what the reader is already viewing.
The HTML document alone is larger than 2MB — past Google's documented 2MB indexing limit. Images, CSS and JS are fetched separately and do NOT count toward this.
Impact: Google only indexes the first 2MB of HTML, so any content past that point in the document risks never being indexed.
Trim large inline scripts and JSON embedded in the HTML. • Paginate huge lists and move bulk data out of the initial HTML. • Enable server-side compression to shrink the document below 2MB.
Related Terms
Core Web Vitals
Google's metrics for measuring page speed, responsiveness, and visual stability.
Largest Contentful Paint (LCP)
A Core Web Vitals metric measuring when the largest visible element finishes rendering.
Cumulative Layout Shift (CLS)
A Core Web Vitals metric measuring how much page content unexpectedly shifts during loading.
Page Speed
How quickly a web page loads and becomes interactive for users.