What Is Interaction to Next Paint (inp)

Photo by Đức Trịnh on Unsplash

When a visitor taps a menu, clicks “Add to Cart,” opens a form, or types into a search box, they expect the page to react immediately. If nothing appears to happen, even for a fraction of a second, the experience feels slow and unreliable. Interaction to Next Paint (INP) is the Core Web Vital designed to measure that responsiveness—and improving it can make your website feel faster, smoother, and easier to use.

What Is Interaction to Next Paint (INP)?

Interaction to Next Paint is a user experience metric that measures how quickly a webpage responds visually after a user interaction. It captures the time from when a user initiates an interaction until the browser presents the next visible update, or “paint,” on the screen.

INP evaluates interactions such as:

• Mouse clicks on buttons, links, menus, tabs, and accordions
• Touches and taps on mobile devices
• Keyboard input, including typing in fields and using keyboard controls

It does not simply measure whether the browser receives an input. Instead, it measures whether the visitor sees a response. For example, if a customer clicks a product filter but the selected state and product list update late, that delay contributes to a poor INP result.

How INP Is Calculated

INP measures the latency of individual interactions across a page visit. Each interaction’s total duration can include three important stages:

• Input delay: The time an interaction waits before the browser can begin processing it. This often happens when the main thread is busy running JavaScript.
• Processing time: The time required to run event handlers, execute scripts, update application state, and perform related work.
• Presentation delay: The time the browser needs to render, style, lay out, and paint the visual response after processing is complete.

Google uses a page visit’s worst interaction, or a near-worst interaction when there are many interactions, to represent INP. This approach prevents an otherwise fast page from receiving a strong score while still delivering one frustratingly slow click, tap, or keyboard action.

INP is generally based on real-user field data and assessed at the 75th percentile of page visits. In practical terms, your site should provide responsive interactions for most visitors—not only for users on high-end devices or fast connections.

What Is a Good INP Score?

Google’s recommended Interaction to Next Paint thresholds are:

• Good: 200 milliseconds or less
• Needs improvement: More than 200 milliseconds and up to 500 milliseconds
• Poor: More than 500 milliseconds

A good INP score is 200 ms or below. At this level, buttons, forms, navigation elements, and other interactive components generally feel immediate. Scores above 500 ms can create obvious lag, causing visitors to repeat clicks, abandon tasks, or assume the website is broken.

Why INP Matters for User Experience and SEO

INP matters because responsiveness is a core part of perceived website speed. A page may load quickly, yet still feel sluggish if its filters, checkout controls, navigation, or contact forms are slow to react. Slow interactions can reduce engagement, hurt conversion rates, and create friction at key points in the customer journey.

INP is also part of Google’s Core Web Vitals and replaced First Input Delay (FID) in Google’s ranking-related page experience metrics. While no single metric guarantees rankings, strong Core Web Vitals support a healthier technical SEO foundation. Better responsiveness can help search engines and users view your site as more usable, stable, and trustworthy.

For SEO teams, INP should be evaluated alongside Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), crawlability, mobile usability, and content quality. It is not a substitute for relevant content or authority, but it can expose technical barriers that weaken real-world user satisfaction.

INP vs. First Input Delay: What Is the Difference?

First Input Delay (FID) measured only the delay before the browser could begin processing a visitor’s first interaction. It did not account for the full event-handler execution or the time needed to paint an on-screen result.

INP is more comprehensive. It assesses responsiveness throughout the visit, considers click, tap, and keyboard interactions, and includes the complete path to the next visual update. That makes INP a more meaningful measure of whether a webpage actually feels responsive during real use.

Common Causes of a Poor INP Score

Poor INP usually indicates that the browser’s main thread is overloaded when users try to interact with the page. Common technical causes include:

• Long JavaScript tasks: Large tasks can block the main thread for hundreds of milliseconds, forcing interactions to wait.
• Excessive JavaScript bundles: Unused code, bulky frameworks, and too many third-party scripts increase parsing, compiling, and execution work.
• Heavy event handlers: Click, input, or touch handlers that perform expensive calculations, DOM queries, or synchronous network work can delay feedback.
• Main-thread blocking: Analytics tags, chat widgets, consent platforms, embedded tools, and advertising scripts may compete with essential interaction work.
• Delayed rendering: Complex layouts, large DOM trees, forced reflows, and expensive style recalculations can postpone the next paint.
• Slow interactive components: Search autocomplete, product filters, modal windows, sliders, and form validation often create latency when poorly implemented.

How to Check Your Website’s INP Score

Use both field data and lab diagnostics. Field data shows what actual visitors experience, while lab tools help developers reproduce, identify, and fix performance bottlenecks.

• PageSpeed Insights: Review Core Web Vitals field data from the Chrome UX Report and see diagnostic opportunities for a specific URL.
• Chrome UX Report (CrUX): Access aggregated real-user performance data for eligible sites and pages, including INP at the 75th percentile.
• Google Search Console: Check the Core Web Vitals report to identify groups of URLs that need attention on mobile and desktop.
• Chrome DevTools: Use the Performance panel to record interactions, inspect long tasks, identify slow event handlers, and analyze rendering activity.

Start with PageSpeed Insights or Search Console to find affected pages. Then use Chrome DevTools to investigate the JavaScript execution, layout work, and rendering delays behind the field-data issue.

How to Improve Interaction to Next Paint

Improving INP means reducing the work that must happen before the browser can show a visual response. Focus on the interactions visitors use most often, especially on mobile devices.

• Reduce JavaScript work: Remove unused code, defer nonessential scripts, code-split large bundles, and limit third-party tags.
• Break up long tasks: Split heavy JavaScript into smaller chunks so the browser can return to the event loop and handle user input sooner.
• Optimize event handlers: Keep click and input handlers lean. Avoid unnecessary DOM reads and writes, expensive loops, and synchronous processing.
• Provide immediate feedback: Update button states, loading indicators, selected filters, or form feedback quickly while longer background work continues.
• Minimize rendering delays: Simplify complex DOM structures, reduce layout thrashing, batch DOM changes, and avoid forced synchronous reflows.
• Audit third-party code: Test the impact of plugins, widgets, tag managers, embedded media, and tracking scripts on main-thread activity.
• Test real workflows: Measure the actions that matter: opening navigation, submitting forms, adding products to a cart, filtering results, and completing checkout.

Does INP Affect Google Rankings?

Yes. INP is a Core Web Vital within Google’s page experience metrics, so it can be a ranking-related signal. However, it is only one part of SEO. A fast, responsive site still needs helpful content, sound technical implementation, relevant search intent targeting, and credible backlinks. Treat INP as an opportunity to improve both search performance and the on-site experience that converts visitors.

Ready to see how your site stacks up? Run a free SEO audit and get a clear picture of what's holding your rankings back.