# Interaction to Next Paint (INP)

Category: [Performance & Core Web Vitals](https://seo-geo-glossary.com/en/glossary/category/performance-core-web-vitals/) › [Core Web Vitals & metrics](https://seo-geo-glossary.com/en/glossary/category/performance-core-web-vitals/core-web-vitals-metrics/) · Also known as: INP

**Interaction to Next Paint (INP)** is a Core Web Vitals metric for how quickly a page responds. It measures the time from a user interaction until the browser paints the next frame, across all interactions during a visit.

## What does INP measure?

Clicks, taps and key presses count. Scrolling, hovering and zooming do not. The time covers input delay, the processing in event handlers and the rendering of the next frame. The reported value is usually the slowest interaction of a visit, with outliers ignored: one highest interaction is dropped for every 50. Google evaluates the 75th percentile of page views.

| Rating | INP |
|---|---|
| Good | up to 200 ms |
| Needs improvement | 201 to 500 ms |
| Poor | over 500 ms |

## INP and FID

Since March 12, 2024, INP has replaced First Input Delay as a Core Web Vital. FID looked only at the delay before the first interaction. INP covers all interactions and includes the time until the visible result.

## Typical causes of poor values

Long tasks on the main thread, heavy event handlers and large amounts of JavaScript, for example on pages with filters, menus or search.

## At a glance

- **Measures:** Latency of all clicks, taps and key presses during a visit, up to the next painted frame
- **“Good” threshold:** 200 ms or less
- **Assessment:** 75th percentile of page views
- **Data source:** Field data preferred, also measurable in the lab
- **Core Web Vital:** yes (responsiveness), since March 12, 2024
- **Docs:** [web.dev: Interaction to Next Paint (INP)](https://web.dev/articles/inp)

Last checked: October 8, 2026

## Thresholds

- **INP** (Interaction to Next Paint): good ≤ 200 ms, needs improvement ≤ 500 ms, poor > 500 ms ([Source](https://web.dev/articles/inp))

Assessed at the 75th percentile of page loads, mobile and desktop separately.

## Web Vitals metrics compared

| Metric | Measures | Core Web Vital? | Field or lab | “Good” per web.dev |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | Render time of the largest image, text block or video visible in the viewport, from the start of navigation | yes (loading) | field and lab | 2.5 s or less |
| INP (Interaction to Next Paint) | Latency of interactions across the whole visit until the next paint; one value that all (or nearly all) interactions fall below | yes (interactivity), since 2024-03-12 | field; in the lab only with simulated interactions, Lighthouse does not measure INP | 200 ms or less |
| CLS (Cumulative Layout Shift) | Largest burst of unexpected layout shifts during the entire lifecycle of the page | yes (visual stability) | field and lab | 0.1 or less |
| TTFB (Time to First Byte) | Time from the start of navigation until the first byte of the response arrives | no (helps diagnose LCP) | field and lab | 0.8 s or less |
| FCP (First Contentful Paint) | Time from the start of navigation until any part of the page's content is rendered | no (helps diagnose LCP) | field and lab | 1.8 s or less |
| TBT (Total Blocking Time) | Total time after FCP during which the main thread was blocked long enough to prevent input responsiveness | no (lab proxy for INP) | lab; web.dev does not recommend field measurement | less than 200 ms on average mobile hardware |
| Speed Index | How quickly content is visually displayed during page load (from a video of the load) | no | lab (Lighthouse) | Threshold according to Lighthouse: mobile up to 3.4 s “fast” (web.dev gives no value) |
| FID (First Input Delay), historical | Time from the first interaction until the browser can begin processing event handlers | until 2024-03-12, replaced by INP | field only | 100 ms or less |

Sources: [web.dev: Web Vitals](https://web.dev/articles/vitals); [web.dev: Largest Contentful Paint (LCP)](https://web.dev/articles/lcp); [web.dev: Interaction to Next Paint (INP)](https://web.dev/articles/inp); [web.dev: Cumulative Layout Shift (CLS)](https://web.dev/articles/cls); [web.dev: Time to First Byte (TTFB)](https://web.dev/articles/ttfb); [web.dev: First Contentful Paint (FCP)](https://web.dev/articles/fcp); [web.dev: Total Blocking Time (TBT)](https://web.dev/articles/tbt); [web.dev: First Input Delay (FID)](https://web.dev/articles/fid); [web.dev Blog: Interaction to Next Paint is officially a Core Web Vital (2024-03-12)](https://web.dev/blog/inp-cwv-launch); [Chrome for Developers: Lighthouse – Speed Index](https://developer.chrome.com/docs/lighthouse/performance/speed-index). Last checked: October 8, 2026

*Diagram: The three phases of an interaction.* Every interaction consists of input delay, processing duration and presentation delay. Long tasks on the main thread extend the input delay. According to web.dev, INP is the slowest interaction of a visit for most sites.

## Core Web Vitals: from launch to today

- **May 5, 2020:** Google introduces Web Vitals. The first Core Web Vitals are LCP, FID and CLS. ([Source](https://blog.chromium.org/2020/05/introducing-web-vitals-essential-metrics.html))
- **May 28, 2020:** Google announces a page experience ranking signal that combines Core Web Vitals with existing signals. ([Source](https://developers.google.com/search/blog/2020/05/evaluating-page-experience))
- **November 10, 2020:** Google sets the date: the signals are to be used in ranking from May 2021. ([Source](https://developers.google.com/search/blog/2020/11/timing-for-page-experience))
- **April 19, 2021:** Postponed: gradual rollout from mid-June 2021, full effect only by the end of August 2021. ([Source](https://developers.google.com/search/blog/2021/04/more-details-page-experience))
- **June 15 to August 2021:** Page experience update for mobile: Core Web Vitals become part of the ranking systems. ([Source](https://developers.google.com/search/blog/2021/04/more-details-page-experience))
- **February 22 to March 3, 2022:** Page experience update for desktop, using the same Core Web Vitals thresholds as on mobile. ([Source](https://status.search.google.com/incidents/zDCQR5mxLU3ZrQeQvwqN))
- **May 10, 2023:** INP is no longer experimental. Google announces that INP will replace FID as a Core Web Vital in March 2024. ([Source](https://web.dev/blog/inp-cwv))
- **March 12, 2024:** INP replaces FID. Since then the Core Web Vitals are LCP, INP and CLS. Articles citing “FID 100 ms” as a threshold are out of date. ([Source](https://web.dev/blog/inp-cwv-launch))
- **September 9, 2024:** Chrome tools end support for FID. ([Source](https://web.dev/articles/fid))

## Not to be confused with

- [First Input Delay (FID)](https://seo-geo-glossary.com/en/glossary/first-input-delay/index.md): measured only the delay of the first interaction, not the processing and not the time until the visible result. It was a Core Web Vital until March 12, 2024.

## Related terms

- [Core Web Vitals](https://seo-geo-glossary.com/en/glossary/core-web-vitals/index.md)
- [First Input Delay (FID)](https://seo-geo-glossary.com/en/glossary/first-input-delay/index.md)
- [Largest Contentful Paint (LCP)](https://seo-geo-glossary.com/en/glossary/largest-contentful-paint/index.md)
- [Cumulative Layout Shift (CLS)](https://seo-geo-glossary.com/en/glossary/cumulative-layout-shift/index.md)
- [Total Blocking Time (TBT)](https://seo-geo-glossary.com/en/glossary/total-blocking-time/index.md)

## Sources

- [Interaction to Next Paint (INP) – web.dev](https://web.dev/articles/inp)
- [INP becomes a Core Web Vital on March 12 – web.dev](https://web.dev/blog/inp-cwv-launch)
- [Interaction to next paint – MDN](https://developer.mozilla.org/en-US/docs/Glossary/Interaction_to_next_paint)

---

Last updated: October 8, 2026
URL: https://seo-geo-glossary.com/en/glossary/interaction-to-next-paint/