Speed and performance

INP — Interaction to Next Paint

Interaction to Next Paint measures how quickly a page can present a visual response to user interactions such as clicks, taps and keyboard input. It evaluates interaction responsiveness during the page visit rather than only the first interaction.

Published: Updated: 3 min read
Diagram: INP - Interaction to Next Paint. Entrance - Service - View.

What does INP stand for?

Interaction to Next Paint measures how quickly a page can present a visual response to user interactions such as clicks, taps and keyboard input. It evaluates interaction responsiveness during the page visit rather than only the first interaction. It replaced First Input Delay in the Core Web Vitals set, so guidance focused solely on FID no longer describes the current metric.

Stages of a slow interaction

An event may wait for other tasks to complete, take a long time to execute its own logic, or wait for an effect to be displayed. Each stage requires a different repair. The button shortcode may still respond late when the main thread blocks the analyst. Costly layout recalculation can also delay the image after the operation itself is completed.

Filtering example

The store counts thousands of products after each character and rebuilds the entire list synchronously. The field appears frozen. Reduce unnecessary work, organize system reads and writes, and choose how to handle larger calculations. The user needs quick and meaningful feedback. Simply showing an animation does not fix an insecure or malfunctioning process.

How to diagnose?

Reproduce real tasks: menu, cart, search and form. Record performance traces and examine long tasks and interaction phases. Break your work into smaller parts when it makes sense, remove unnecessary scripts and reduce re-rendering. Test weaker devices. A deferred operation cannot lose your typed text or spoil your keyboard.

Measurement errors

Laboratory opening of the website may not perform the actions that customers have problems with. Removing button support would seemingly improve the load, but would destroy the function. Artificial delays can change what is measured without addressing the cause. The assessment should cover actual behavior, not just the green section of the report.

How to check the result?

Good INP is up to 200 milliseconds at the 75th percentile. Use user data when there is enough of it and for quick diagnostic testing of specific interactions. Confirm that forms and purchases work after the fix. Analyze templates and action types separately so that a single heavy widget doesn't disappear into the overall site average.

How can you reproduce a slow interaction?

Select a specific task: opening a filter, changing a variant, adding a product or entering text. Save the run on a device with realistic performance and see what is occupying the main thread. A long calculation loop, an expensive DOM update, and an external script can all produce a similar symptom. API response latency alone does not explain the entire INP; it is also important to be able to show the user how the interface responds.

Break up the hard work, reduce unnecessary rendering, and avoid performing expensive calculations on each character. Debounce can help search, but it shouldn't hide the lack of button response. Check the waiting state and error handling. Test the entire path after a change: a faster click is not a success if the product variant has stopped updating the price or the form has lost validation.

Sources and further reading

Use the primary documentation to check the principles and limitations described in this article.

How we prepare the glossary

These articles combine original editorial work, AI support for editing and translation, and checks against linked primary documentation. Examples are illustrative unless stated otherwise; they do not represent client results. Dates refer to publication and actual content changes.

From knowledge to action

Need help putting this into practice?

Tell us about your website or process. We will define the scope and the next practical step.

Discuss your project