Performance 5 min read

INP explained: fixing slow interactions on your website

When a tap takes too long to respond, visitors notice. What INP measures and how to improve it.

On this page 9 sections

A page can load quickly and still feel slow. You tap a menu button and nothing happens for a moment. You choose an option in a form and the screen freezes before it updates. Those delays are what Interaction to Next Paint (INP) measures, and they are a common reason business websites fail Core Web Vitals on mobile.

This guide explains what INP is, what a good score looks like, how to find the interactions causing problems, and the fixes that usually make the biggest difference.

The short answer

INP measures how quickly a page responds visually after someone clicks, taps or types. It looks at interactions throughout the visit and reports one of the slowest.

  • Good: 200 milliseconds or less.
  • Needs improvement: between 200 and 500 milliseconds.
  • Poor: more than 500 milliseconds.

Google assesses these at the 75th percentile of real visits, so most visitors need a good experience for a page to pass. INP became one of the three Core Web Vitals in 2024, replacing First Input Delay. web.dev’s guide to Interaction to Next Paint is the reference explanation.

What INP actually measures

Every interaction has three parts:

Part What happens Typical cause of delay
Input delay Time before the browser can start handling the tap The main thread is busy with other JavaScript
Processing time Time to run the code that responds to the tap Heavy or inefficient event handlers
Presentation delay Time to calculate layout and paint the result Large or complex page updates

INP is the total of all three, from the tap to the next frame the visitor sees. A slow score can come from any part, which is why finding the cause matters more than guessing.

Why it matters

  • Visitors notice. A delay of a few hundred milliseconds after a tap makes a site feel broken, and people often tap again, causing more confusion.
  • It affects search. Core Web Vitals are part of how Google evaluates page experience. Our guide to Core Web Vitals explains how they fit together.
  • It hits forms and menus hardest, which are exactly the parts of a site that lead to enquiries.

How to find your INP

Field data first

INP depends on real devices and real interactions, so start with real-user data:

  • PageSpeed Insights shows INP from real Chrome users for your page or whole site, if there is enough traffic. Our guide to reading PageSpeed Insights explains the report.
  • Search Console’s Core Web Vitals report groups pages with INP problems.

Lab tests such as Lighthouse can’t measure INP directly, because there is no real person tapping. They show Total Blocking Time, which often points to the same underlying problem.

Then find the slow interaction

  1. Open the page in Chrome on a mid-range phone, or with CPU throttling in developer tools.
  2. Open the Performance panel and record while you use menus, buttons, tabs and forms.
  3. Look for interactions marked as slow and for long tasks: blocks of JavaScript that run for more than 50 milliseconds.
  4. Note which script or function is running during the delay.

Common causes on business websites

Cause Where it shows up
Third-party scripts Chat widgets, tag managers, ad and tracking scripts competing for the main thread
Heavy page builders Large amounts of JavaScript for animations, sliders and effects
Plugins doing work on every click Analytics events, pop-up checks or form validation that runs too much code
Large DOM Very long pages with thousands of elements, making every update slower
Complex menus and filters Mega menus or product filters that re-render large parts of the page
Animations triggered on interaction Effects that change layout rather than using transform and opacity

On many WordPress sites, the biggest wins come from removing or delaying third-party scripts and unnecessary plugins. Our guide to third-party scripts and website speed covers how to audit them.

Practical fixes

Reduce JavaScript

  • Remove plugins and scripts you don’t need.
  • Load non-essential scripts, such as chat widgets, only after the page is idle or when the visitor asks for them.
  • Avoid loading the same library several times through different plugins.

Break up long tasks

Developers can split long-running code into smaller pieces, so the browser can respond to taps in between. Updating the visible part of the page first and doing the rest afterwards makes interactions feel immediate.

Give immediate feedback

When a task genuinely takes time, such as submitting a form, show a response straight away: a pressed state on the button or a short message. The visitor then knows their tap worked.

Simplify what changes

  • Keep the DOM smaller by removing hidden or duplicated content.
  • Animate with transform and opacity rather than properties that force layout recalculation.
  • Update only the part of the page that needs to change.

Test on real devices

Fast laptops hide INP problems. Test on a mid-range Android phone, which is closer to what many visitors use.

A quick INP checklist for WordPress sites

Many business sites run on WordPress, where a few checks cover most problems:

  1. List active plugins and remove any that are unused or duplicate features.
  2. Check what loads on every page. Contact form, slider and gallery scripts often load everywhere, even where they aren’t used.
  3. Review the page builder’s effects. Entrance animations, parallax and sticky elements all add work on each interaction.
  4. Delay chat and marketing widgets until the visitor scrolls or clicks.
  5. Test the mobile menu and contact form after each change, on a real phone.
  6. Recheck field data in PageSpeed Insights after a few weeks, since real-user data takes time to update.

Make one change at a time and test it, so you know which change helped and nothing breaks unnoticed. Our guide to speeding up a WordPress website covers the loading side of the same work.

Frequently asked questions

Is INP the same as page speed?

No. Loading speed is measured mainly by Largest Contentful Paint. INP measures responsiveness after the page has loaded. A page can load fast and still have poor INP.

Why does my INP look fine on desktop but poor on mobile?

Phones have slower processors, so the same JavaScript takes longer to run. Most INP problems appear first on mobile, which is why Google’s mobile results matter most.

Can a plugin fix INP for me?

Some optimisation plugins help by delaying scripts, but they can also break features if configured carelessly. The most reliable fix is usually removing what isn’t needed, then testing each change.

What to do next

Check your site’s INP in PageSpeed Insights. If it needs improvement, open your heaviest page on a phone and tap every menu and button. The interaction that feels slowest is the place to start.

Our website design and development service builds sites with minimal JavaScript, so interactions stay fast on phones. For an existing site, the Growth care plan in our website maintenance service includes regular speed work.

Written by the PORVIX team

The people who design, build and maintain websites for growing businesses. We write about the questions that come up on real projects, in plain language, and update articles when the advice changes.

Published

How we work

Is your current site costing you enquiries?

A free, plain-language audit, by email within 2 business days.

Get a free audit
Get a free audit

Keep reading

More plain-language guides.

More on performance first, then other guides worth reading next.

All insights

Start here

Let’s build a website that brings in business.

Tell us about your project. You’ll hear back from a real person within one business day, with honest advice either way.

  • Free consultation
  • Fixed written quote
  • Your details stay private