Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is INP? A Plain Explanation

Short answer

INP, short for Interaction to Next Paint, measures how long a page takes to show a visible response after you click, tap, or press a key. Google rates an INP of 200 milliseconds or less as good, over 200 up to 500 milliseconds as needs improvement, and over 500 milliseconds as poor, judged at the 75th percentile of real visits.

Key takeaways

  • INP measures the time from a click, tap, or key press until the browser paints the next visible frame.
  • A good INP score is 200 milliseconds or less at the 75th percentile, and a poor score is over 500 milliseconds.
  • INP replaced First Input Delay as a Core Web Vital on March 12, 2024.
  • Only clicks, taps, and key presses count for INP, while scrolling, hovering, and zooming do not.
  • A task over 50 milliseconds on the main thread is a long task and can delay the response to an interaction.

What is INP?

INP, short for Interaction to Next Paint, is the time from a click, tap, or key press until the browser paints the next frame that shows the response.

Google Search Central lists INP as one of three Core Web Vitals, next to Largest Contentful Paint for loading and Cumulative Layout Shift for visual stability. The Core Web Vitals page says the set measures real-world user experience for loading, interactivity, and visual stability.

INP measures responsiveness, not load speed. A page can load its main content fast and still feel slow if taps and clicks take too long to show a result.

What does INP measure on a page?

INP measures the latency of every click, tap, and key press during a visit, from the input until the next visible frame.

The web.dev guide to INP says INP assesses a page's overall responsiveness by observing the latency of all click, tap, and keyboard interactions that occur throughout a visit. The final value is the longest interaction observed, ignoring outliers.

Only 3 interaction types count for INP:

  • Clicking with a mouse
  • Tapping on a touchscreen
  • Pressing a key on a physical or onscreen keyboard

Scrolling, hovering, and zooming do not count. A page with no interactions has no INP value, so some quiet pages show no INP data at all.

What is a good INP score?

A good INP score is 200 milliseconds or less, measured at the 75th percentile of page loads on mobile and desktop separately.

The web.dev guide to INP gives 3 bands, checked in November 2026:

INP valueRatingWhat it means
200 milliseconds or lessGoodThe page responds right away for most visits
Over 200 up to 500 millisecondsNeeds improvementThe delay is noticeable
Over 500 millisecondsPoorThe page feels slow or stuck after input

Google judges the score at the 75th percentile, so the number reflects most visits, not the fastest visit or a simple average. Mobile and desktop are rated separately, because phones often respond more slowly than desktops.

For context, the other two Core Web Vitals have their own good targets. Google Search Central says to aim for a Largest Contentful Paint of 2.5 seconds or less and a Cumulative Layout Shift of 0.1 or less.

How is INP different from FID?

INP replaced First Input Delay, known as FID, as the Core Web Vital for responsiveness on March 12, 2024.

FID measured only the input delay of the first interaction on a page. That is the wait before the browser starts to handle that first click or tap.

INP is stricter in 2 ways. First, it observes all interactions during a visit, not only the first one. Second, it measures the full time until the next paint, including the event handlers and the work to draw the next frame.

A page could pass FID and still fail INP. A slow menu, a slow search box, or a slow checkout button later in the visit can set the INP value, even if the first click was fast.

How does INP work in three parts?

Every INP interaction has three parts: input delay, processing duration, and presentation delay.

Chrome for Developers explains that the Event Timing API splits INP into those 3 subparts. The guide to INP causes names them as input delay, processing duration, and presentation delay.

PartWhat happensCommon cause
Input delayThe input waits until work already running on the main thread finishesA long script task is still running
Processing durationThe event handler code for the interaction runsThe handler does too much work at once
Presentation delayThe browser recalculates styles and layout, then paints the next frameA large page update or heavy rendering work

Input delay

Input delay is the wait before the handler starts. It grows when the main thread is busy with a script, a timer, or a previous interaction.

Processing duration

Processing duration is the time the event handlers take to run. A handler that updates many elements, runs a search, or fires several extra scripts takes longer here.

Presentation delay

Presentation delay is the time to draw the next frame after the handlers finish. Style recalculation, layout, and paint all happen in this part.

The total is the sum of the 3 parts. Finding which part is longest tells you where to start, because each part points to a different fix.

Why does INP matter for a WordPress site?

INP matters because visitors judge a WordPress site by how it reacts, and Google uses Core Web Vitals in its ranking systems.

Google Search Central states that Core Web Vitals are used by its ranking systems, and it recommends that site owners aim for good scores. Relevance and content still matter more, but a slow response can hurt both visitors and search results.

Think about the interactions on a WordPress site. A visitor opens a menu, types in a search box, filters products, adds an item to a cart, or submits a form. If each of those takes over 500 milliseconds to show a change, the site feels broken, even if the first page loaded fast.

What makes INP slow on WordPress?

Long JavaScript tasks are the most common cause, because a task over 50 milliseconds blocks the main thread and delays the response to an interaction.

The web.dev guide to long tasks defines a long task as any task that takes longer than 50 milliseconds. While that task runs, the browser cannot interrupt it to handle input or paint a frame.

On WordPress, long tasks often come from these sources:

  • A theme or plugin that loads a large JavaScript file on every page
  • A chat widget, cookie banner, or tag manager that runs during load
  • A slider, form, or page builder script that does heavy work on click
  • A very large page structure, which makes style and layout work slower

Heavy JavaScript is not the only cause. A handler that reads element sizes after each change can force the browser to recalculate layout again and again. Web.dev calls this layout thrashing, and it adds time to processing and presentation.

If you want a wider speed plan, read our guide to speeding up WordPress. It covers the basic steps that also help INP, such as cutting unused scripts.

How do you check INP on your site?

Check INP in PageSpeed Insights and Search Console, because both show field data from real Chrome users.

Google's About PageSpeed Insights page says field data comes from the Chrome User Experience Report, known as CrUX. It covers the previous 28-day collection period and is updated daily, as of November 2026.

Follow these steps to check a page:

  1. Open PageSpeed Insights and enter the full URL of the page.
  2. Run the test for mobile first, then check desktop.
  3. Read the field data at the top, under the heading about what real users experience.
  4. Find the INP value and its band: good, needs improvement, or poor.
  5. Open Search Console, then the Core Web Vitals report, to see the same bands across many pages.

Field data is the number that counts for the Core Web Vitals assessment. Lab data from Lighthouse is a single simulated load, and it is useful for finding causes, but it cannot measure real interactions from real visitors.

Chrome DevTools can help you find the slow interaction. The Google codelab on INP shows how to use the Performance panel, where the Interactions track lists each interaction with its input delay, processing duration, and presentation delay. That INP codelab is a useful way to see the 3 parts in action.

How do you improve a poor INP score?

Start with the slowest interaction in field data, find which of the 3 parts is longest, then fix that part first.

Web.dev's advice for optimizing INP starts with the same idea: break up long tasks and yield to the main thread often. A long task split into smaller pieces lets the browser handle a waiting click between pieces.

Use these fixes, in order:

  • Break up long tasks so no single task runs far over 50 milliseconds.
  • Yield to the main thread between chunks of work, with scheduler.yield() where it is supported and setTimeout as a fallback.
  • Do less work inside event handlers, and move work that does not change the next frame to a later task.
  • Defer scripts that are not needed for the first interaction, such as chat widgets and extra tags.
  • Avoid layout thrashing by not reading sizes right after changing the page layout.
  • Use content-visibility to lazily render off-screen elements, so the browser does less layout work.

A theme change can also help, because a lighter theme often ships less JavaScript. Compare options in our Astra vs GeneratePress vs Kadence speed guide before you switch.

Check your host too, since slow hosting adds delay to every step. Our guide to choosing WordPress hosting explains what to look for.

After a fix, allow time for field data to change. The field window covers 28 days, so a fix enters the data gradually as new visits replace old ones. A fresh lab test can show the change at once, but the field score moves more slowly.

What are common myths about INP?

No, a high Lighthouse score does not prove good INP, because Lighthouse is a lab test and INP is a field metric.

These myths cause the most confusion:

  • Myth: INP is the same as page load speed. INP measures response to input after the page loads, not how fast the page first appears.
  • Myth: Scrolling and hovering count. Only clicks, taps, and key presses count, so a slow scroll does not change INP.
  • Myth: One fast click means a good score. INP reports the longest interaction observed, ignoring outliers, so one slow interaction can set the value.
  • Myth: Fixing Largest Contentful Paint fixes INP. Loading and responsiveness are different metrics, and each needs its own fix.
  • Myth: INP only matters on the home page. INP is measured per page, so a slow checkout or contact page can fail on its own.

What mistakes should you avoid?

The biggest mistake is chasing the lab score while ignoring field data from real visitors.

Avoid these mistakes:

  • Judging INP from a single lab run, instead of the 28-day field data in PageSpeed Insights.
  • Testing only on desktop, when most visitors may use phones and mobile INP is often worse.
  • Adding more plugins to fix speed, when each new script can add long tasks and make INP worse.
  • Fixing the first click only, when a later interaction, such as a menu or cart button, is the slow one.
  • Changing many things at once, then not knowing which change helped the field score.

Fix one slow interaction at a time, then wait for new field data before you judge the result. That steady loop is how most WordPress sites move from poor to good INP.

Frequently asked questions

Is INP the same as page speed?

No. Page speed usually means how fast a page loads, while INP measures how fast a page responds after you click, tap, or press a key. A page can load fast and still have poor INP if its JavaScript handlers are slow. Both matter, but they measure different parts of the visit.

What INP score should I aim for on WordPress?

Aim for 200 milliseconds or less at the 75th percentile, separately for mobile and desktop. That is the good band in Google's guidance. Over 200 up to 500 milliseconds needs improvement, and over 500 milliseconds is poor. Check both mobile and desktop, since mobile is often slower.

Why does my site have no INP data in PageSpeed Insights?

INP only exists when visitors interact with a page, and field data only appears when there are enough real Chrome visits in the last 28 days. A new page or a quiet page may show no field data. Check the origin-level data, or test a busier page on the same site first.

Can a plugin cause poor INP?

Yes. A plugin can add JavaScript that runs on every page, runs long tasks on the main thread, or does heavy work inside a click handler. Chat widgets, sliders, forms, and page builders are common sources. Remove plugins you do not need, and test the slowest interaction after each change.

How long does it take for an INP fix to show in the score?

Field data covers the previous 28 days and updates daily, so a fix enters the score gradually as new visits replace old ones. It can take up to 28 days for the full effect to show. A lab test in Chrome DevTools can show the change at once, but it does not replace field data.

Does INP affect Google rankings?

Google Search Central says Core Web Vitals are used by its ranking systems, and it recommends good scores for search success. INP is one of the three Core Web Vitals. Relevance and content still matter more, so INP alone will not rank a weak page, but a poor score can hold back a good one.

Sources

  1. Interaction to Next Paint (INP) web.dev
  2. Understanding Core Web Vitals and Google search results Google Search Central
  3. Identify causes of poor INP Chrome for Developers
  4. About PageSpeed Insights Google for Developers
  5. Understanding Interaction to Next Paint (INP) Google Codelabs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test