1. Home
  2. Guides
  3. Interaction to Next Paint
Performance guide

Interaction to Next Paint (INP): how to measure and improve it

INP asks one question: when someone clicks, taps or types, how long until the page visibly responds? It replaced First Input Delay as a Core Web Vital in March 2024, and it is mostly a JavaScript problem.

Key points

  • INP is good at 200 ms or less and poor above 500 ms, at the 75th percentile.
  • It covers clicks, taps and key presses across the whole visit, and reports roughly the slowest one.
  • INP is a field metric. Lab runs use Total Blocking Time as the nearest stand-in.

What INP measures

Interaction to Next Paint observes the latency of clicks, taps and keyboard presses during a page visit. For each interaction it measures the time from the input until the browser paints the next frame that reflects the result. The value reported for the page is close to the longest of those interactions (on pages with very many interactions, a rare outlier is ignored). Scrolling and hovering are not counted.

RatingINP
Good≤ 200 ms
Needs improvement200–500 ms
Poor> 500 ms

INP replaced First Input Delay (FID) as a Core Web Vital on March 12, 2024. FID only measured the wait before the first interaction started to be processed, so a page could pass it while still feeling slow later. INP is stricter and closer to how people experience a page.

The three phases of an interaction

  1. Input delay: the time the event waits because the main thread is busy with something else, often a long task from a script.
  2. Processing time: how long your event handlers take to run.
  3. Presentation delay: the time for the browser to recalculate layout, paint and show the result. Large DOMs and heavy style changes make it longer.

Fixing INP means finding which phase dominates for the interaction that is slow.

Measuring INP, and what a lab run can tell you

INP needs real interactions, so it comes from field data: the Chrome User Experience Report, the Core Web Vitals report in Search Console, or the web-vitals JavaScript library running on your own pages. Chrome DevTools can also record individual interactions while you test a page by hand.

A Lighthouse run loads the page without clicking anything, so it cannot report INP. It reports Total Blocking Time (TBT) instead: the sum of the time over 50 ms in each long task between First Contentful Paint and Time to Interactive. Lots of blocking time during loading means the main thread is overloaded, which is also what makes interactions slow. Treat TBT as a warning signal and confirm with field data.

WebsiteHealthLabs shows TBT in the Performance section and labels it as a lab proxy. It does not claim to show your INP.

How to improve INP

Ship and run less JavaScript

  • Remove libraries you no longer use and split large bundles so each page loads only what it needs.
  • Audit third-party scripts: tag managers, chat widgets, A/B testing and ad code are common causes of main-thread contention.

Break up long tasks

A task that runs for more than 50 ms blocks input. Split big jobs into smaller pieces and let the browser handle input in between.

async function processItems(items) {
  for (const item of items) {
    handle(item);
    // Let the browser handle input and paint between chunks.
    await new Promise(resolve => setTimeout(resolve, 0));
  }
}

Where supported, scheduler.yield() does the same job with better scheduling, and it can be feature-detected with a setTimeout fallback.

Keep event handlers light

  • Do the minimum needed to update the interface, then defer analytics, logging and other work until after the next paint.
  • Avoid forcing layout in a loop (reading layout properties after writing styles).

Keep the DOM small

Thousands of elements make every style change and layout slower. Render long lists in pages or with virtualisation, and avoid updating large parts of the page for a small change.

See also: Page weight explained, Accessibility basics.

FAQ

Why does the audit not show my INP?

INP is measured from real visits, and our audit loads the page once in a lab environment without interacting with it. We show Total Blocking Time, which is the closest lab measure, and label it clearly.

Is a low TBT enough to guarantee a good INP?

No. TBT only covers loading. Interactions later in the visit, such as opening a menu or filtering a list, can still be slow. It is a useful early warning, not a guarantee.

What is a long task?

Any task on the browser's main thread that runs for longer than 50 milliseconds. While one runs, the page cannot respond to input.

WebsiteHealthLabs Editorial
Guides explain audit results in plain English. Facts are checked against public documentation from Google, W3C and the browser vendors, and we update them when guidance changes.

↑ ↓ to moveEnter to openEsc to closeAll results