--- language: en title: "INP: Interaction to Next Paint" description: "INP assesses the visual response to clicks, taps, and keyboard input during a visit. Learn how to investigate interaction delays and interpret the 200-millisecond benchmark." canonical: "https://tropk.ai/en/resources/glossary/inp-interaction-to-next-paint" last_modified: "2026-10-12T16:09:17.873Z" --- # INP: Interaction to Next Paint Reviewed on 2026-10-07. ## What it means INP stands for Interaction to Next Paint. The metric observes the latency of clicks, taps, and keyboard interactions until the browser can present the next visual update. The value represents the slowest interaction during the visit, with outliers handled when there are many interactions. As a Core Web Vital, it describes responsiveness throughout use, beyond the initial impression of loading. ## Why it matters for marketing For marketing, INP helps investigate pages that seem fast until someone tries to use them. Selecting a filter, opening a plan option, or typing in a form may cause a noticeable wait. Identifying these interactions makes it possible to request a specific fix from the development team. The delay needs to be observed in the control and under the conditions of use, without mistaking every wait for a slow connection. ## Example in practice Imagine a store where choosing a size leaves the selector without a visual response while a script processes the entire catalog. An interaction record shows a delay before the next paint. The team prioritizes investigating this processing and tests the selection again. The evidence concerns the control's response; it does not measure the total time for a stock query on the server. ## How to apply or verify Use real-world data with the period and devices specified, complemented by tests that perform the problematic actions. web.dev recommends an INP of up to 200 milliseconds at the 75th percentile of visits. Separate the delay before processing, event-handler execution, and wait for the visual presentation. If no eligible interaction occurs, there may be no INP: a missing measurement should not be recorded as zero. ## Important distinctions INP does not measure scrolling or pointer movement, nor the total time to complete a remote operation. A quick visual update may show that the request is still processing. [TBT](/en/resources/glossary/tbt-total-blocking-time) helps identify blocking in the lab, but does not replace real interactions. A good INP also does not prove fast loading or a stable layout, dimensions assessed by [LCP](/en/resources/glossary/lcp-largest-contentful-paint) and [CLS](/en/resources/glossary/cls-cumulative-layout-shift). ## Sources and references - [Interaction to Next Paint (INP)  |  web.dev]() — Google / web.dev ## Continue a leitura - [Core Web Vitals]() - [LCP: Largest Contentful Paint]() - [TBT: Total Blocking Time]() ## About the author [Vinicius Pacheco]() Responsible for Tropk’s technical content, focusing on crawling, indexing, structured data, and agent access to content. --- [All pages in Markdown]()