Skip to content

Home / Blog / Improve INP

Web Development

Interaction to Next Paint (INP): What It Is and How to Fix It on WordPress and Shopify

Interaction to next paint measures how quickly a page responds after a click, tap or key press, and a good score is 200 milliseconds or less. This guide shows how to measure it and fix the usual causes on WordPress and Shopify.

By Ragnar Studio's24 October 202612 min read
Tap ripple on a glass screen sending a glowing pulse along a timeline with a stopwatch dial

A fast-loading page can still feel broken if the menu hangs or the cart button waits a second before reacting. Interaction to next paint, or INP, is the Core Web Vital that catches this, and in October 2026 it is still the vital that trips up many small business sites.

The fixes are less mysterious than they look. Most come down to fewer scripts, shorter click handlers and a lighter page. Related reading: website speed optimization tips, web app vs website and our WordPress development service.

What interaction to next paint actually measures

Interaction to next paint (INP) records how long a page takes to respond visually after someone clicks, taps or presses a key. The clock starts at the input and stops when the browser paints the next frame that shows a result. A tap on "Add to cart" that takes nearly a second to show any change is a slow interaction, even if the page loaded fast.

Every interaction is split into three parts, and knowing which part is slow decides the fix:

  • Input delay: the wait before your code can even start, usually because the main thread is busy with another script.
  • Processing time: how long your event handlers take to run.
  • Presentation delay: the time the browser needs to recalculate styles, lay out the page and paint the new frame.

During a visit the page may see dozens of interactions. Interaction to next paint reports roughly the worst one, ignoring one outlier for every 50 interactions. This is why a single sluggish menu or a heavy chat widget can spoil an otherwise quick site.

INP thresholds you need to hit

Google assesses interaction to next paint at the 75th percentile of real page visits, separately for mobile and desktop. That means three out of four visits must be at or under the line for the page to pass.

RatingINP valueWhat it feels like
Good200 ms or lessFeels instant
Needs improvementOver 200 ms up to 500 msNoticeable lag
PoorOver 500 msFeels broken or frozen

These values come from Google's web.dev guide to INP. Interaction to next paint replaced First Input Delay as a Core Web Vital in March 2024. FID only looked at the delay before the first interaction; INP covers the whole visit, so it is much harder to pass by accident. If you have not looked at the other two vitals yet, read our guide to Core Web Vitals for small business websites first.

Why INP matters for a business site

Interaction to next paint is one of the three Core Web Vitals, which feed into Google's page experience signals. Content relevance still matters far more for rankings, so do not expect a pass to lift a weak page. The stronger reason to care is plain: visitors who tap and see nothing tap again, get confused and leave.

Think about where sluggishness hurts revenue. A slow variant selector on a product page, a filter that hangs on a collection, a form that freezes on submit, a mobile menu that opens after a pause. Each of these sits right on the path to an enquiry or an order. Our article on how to get more leads from your website covers what happens when those moments go wrong.

Treat the metric as a usability check that Google also happens to read. Fix it for people first.

How to measure INP properly

The most important rule: field data beats lab data. Interaction to next paint needs real input from real people on real phones, so a one-off lab test can show a good score while customers suffer. Use these tools in this order.

  1. PageSpeed Insights. Enter a URL and read the real user experience block. It shows INP from the Chrome User Experience Report when your site has enough traffic.
  2. Google Search Console. The Core Web Vitals report groups URLs that fail on mobile and desktop. See our Search Console guide for beginners if you have not set it up.
  3. Chrome DevTools. Open the Performance panel, record while you click through a real journey, and look at the interactions track. It splits each slow interaction into input delay, processing and presentation.
  4. The web-vitals library. Add its onINP function to send real measurements to your own analytics. This is the best way to find which element on which page is slow.

Low-traffic sites often show "not enough data" in PageSpeed Insights. In that case rely on DevTools and test by hand, using a mid-range Android phone if you can. Lab tools can miss slow interactions, so click everything a customer would click: menus, tabs, filters, sliders, cart, forms.

Not sure why your site feels slow? Ragnar Studio's can audit interaction to next paint on your WordPress or Shopify site and list the exact scripts to cut. See website speed optimization or message us on WhatsApp.

Diagnose which phase is slow before you fix anything

Guessing wastes days. Record a slow interaction in DevTools and read the breakdown, then use this table to choose a direction.

Slow phaseTypical causeWhere to look
Input delayLong tasks from scripts, tags and widgetsThird-party scripts, startup JavaScript
Processing timeHeavy event handlersYour theme or plugin click code
Presentation delayLarge DOM, forced layout, big style recalculationPage builders, huge menus, long lists

Fixing one slow interaction often reveals the next, so work in rounds: measure, fix the worst, measure again. Also check iframes. Each embedded frame has its own main thread, and a slow interaction inside a booking or chat frame will not be solved by editing your theme.

Fix input delay: stop long tasks from blocking the page

Any task that holds the main thread for more than 50 ms can delay a tap. Most long tasks come from JavaScript that parses, compiles or runs while the visitor is already trying to use the page.

  • Remove what you do not use. Every extra script adds main thread contention. Audit analytics tags, heatmaps, chat widgets and old plugins.
  • Defer non-essential scripts. Load chat, reviews and tracking after the page is interactive, or on first user interaction.
  • Split big bundles. Ship only the code a page needs. A product page should not load the checkout widget code until required.
  • Use web workers for genuinely heavy work such as parsing large data, so it runs off the main thread.

On most small business sites this single step, cutting scripts, delivers more than any clever code change. Our website speed optimization service starts with exactly this audit.

Fix slow event handlers: yield and do less per click

When a click handler does ten jobs at once, the browser cannot paint until all ten finish. The principle is simple: do the minimum needed to show feedback first, then push everything else to later.

For example, when someone opens a filter panel, show the panel in the callback. Updating analytics, saving state and counting results can run afterwards. A common pattern is to schedule the extra work with setTimeout so the browser gets a chance to paint in between. You do not need to yield after every function call, only before the work that is not needed for the first visible response.

  • Keep handlers short and move calculations out of them.
  • Debounce search boxes so every keystroke does not trigger a full re-render.
  • Avoid synchronous network calls inside click handlers.
  • Show a loading state immediately, even if data takes longer.

Newer browsers also offer scheduler.yield() for the same purpose; check browser support before depending on it.

Fix presentation delay: keep layout work small

After your code runs, the browser must work out styles and layout. A big, deeply nested page makes that slow. Three habits help.

  • Keep the DOM small. Page builders can output thousands of nested elements. Simplify sections, and avoid hidden duplicate menus for desktop and mobile.
  • Avoid layout thrashing. Do not read a size or position right after changing a style in the same task. Batch reads first, then writes.
  • Defer off-screen rendering. The CSS property content-visibility: auto lets the browser skip work for sections far down the page.

Animation matters too. Animating width, height or top forces layout on every frame, while transform and opacity do not. Our guide to speeding up a WordPress website covers the wider performance picture.

Improving INP on WordPress

WordPress sites usually fail for the same reasons: too many plugins, a heavy page builder and third-party tags. A practical order of work:

  1. Test your top five pages in PageSpeed Insights and note the INP values.
  2. Deactivate plugins one at a time on a staging copy and re-test. Slider, popup, social feed and "all in one" plugins are frequent offenders.
  3. Check which scripts load on every page. Use a plugin or code to stop contact form and slider scripts from loading on pages that do not use them.
  4. Choose a lightweight theme and avoid stacking several page builders. Our comparison of Elementor vs Gutenberg explains the trade-off.
  5. Delay chat widgets and tracking until the first interaction.
  6. Use a caching setup, but remember caching helps load speed more than interaction speed. Script weight is the real fix.

If the site is old and layered with years of plugins, a rebuild can be cheaper than patching. See our notes on website redesign signs and checklist.

Improving INP on Shopify

On Shopify you cannot edit the platform core, so the work happens in the theme and the installed apps. Shopify's developer documentation lists the usual trouble spots: variant selectors, cart drawers, mega menus, search and collection filters.

Problem spotWhy it is slowBetter approach
Variant selectorUpdates price, image and button in several stepsBatch DOM reads and writes
Cart drawerAnimates width or top, forcing layoutAnimate with transform
Mega menuInserts a large DOM on hoverKeep markup in place, toggle visibility
App scriptsSynchronous code in click handlersRemove, defer or replace the app

Apps are the biggest lever. Remove apps you no longer use and check that uninstalled apps left no code behind in the theme files. Remove duplicate functions, for example two review apps. Many app vendors ship lighter versions over time, so it is fair to ask app makers about their script impact before you install, and again when a store feels slow.

For a Shopify store that needs a performance clean-up, see our Shopify store development work and the product page optimization guide.

A practical INP checklist

  1. Pull field data from PageSpeed Insights and Search Console; note the worst URLs.
  2. Record the slowest interaction in DevTools; label it input delay, processing or presentation.
  3. List every third-party script on that page and remove or delay at least one.
  4. Shorten the handler: show feedback first, defer the rest.
  5. Reduce DOM size and animate with transform only.
  6. Retest on a real mid-range phone.
  7. Wait. Field data uses a rolling window, so improvements take about a month to appear in CrUX.

Keep a short log of what you changed and the value before and after, so a later plugin update that brings the problem back is easy to spot.

Common mistakes when trying to improve interaction to next paint

  • Chasing the lab score. A 95 in a lab test says little about INP on a customer's phone.
  • Adding a speed plugin on top of a heavy site. Fewer scripts beat more optimisation layers.
  • Ignoring mobile. Phones have slower processors, so mobile is where most sites fail.
  • Testing only the home page. Product pages, checkout and forms are where interactions are heaviest.
  • Fixing once and forgetting. New apps, banners and tags quietly bring the problem back.

Frequently asked questions

What is a good INP score?

A good score is 200 milliseconds or less at the 75th percentile of real visits. Between 200 and 500 ms needs improvement, and anything above 500 ms is poor. Mobile and desktop are assessed separately.

What replaced First Input Delay?

Interaction to next paint replaced First Input Delay as a Core Web Vital in March 2024. FID measured only the delay before the first interaction, while INP measures responsiveness across the whole visit.

How do I check INP on my website?

Open your URL in PageSpeed Insights and read the real user data section, or check the Core Web Vitals report in Search Console. For a single slow interaction, record it in the Chrome DevTools Performance panel. Small sites may lack field data, so test by hand on a phone.

Does INP affect Google rankings?

It is part of the Core Web Vitals used in Google's page experience signals, but relevance and content quality still carry more weight. A poor score is unlikely to sink a strong page, yet slow interactions do hurt conversions and are worth fixing for visitors.

Why is my Shopify store's interaction to next paint poor?

The usual cause is app JavaScript competing for the main thread, plus heavy theme code in variant selectors, cart drawers and menus. Remove unused apps, defer non-essential scripts and test on mobile. See our Shopify SEO guide for Indian stores for related checks.

How do I fix INP on WordPress?

Cut plugins and scripts first, then reduce page builder bloat and delay chat and tracking widgets. Test each change on a staging copy. If the theme itself is heavy, a rebuild may be more cost effective than patching.

How long until INP improvements show in Search Console?

Field data uses a rolling 28 day window, so expect around four weeks before a fix is fully visible. Lab tools and DevTools show the effect immediately, so use them to confirm the fix works.

Can Ragnar Studio's fix INP for my site?

Yes. We audit scripts, themes and apps, then clean up WordPress and Shopify sites. You can message us on WhatsApp +91 92865 18510 or use the contact page.

Interaction to next paint rewards simple discipline: measure with real data, find the slow phase, remove weight and keep handlers short. Start with your top five pages this week, and if you want a second pair of eyes, talk to Ragnar Studio's.

Free quote

Tell us about your project

Fill this short form and send it on WhatsApp. We reply with questions or a quote. Nothing is charged on the website.

  • Takes about two minutes
  • Goes straight to Ragnar Studio's on WhatsApp
  • Prefer email? Write to info@ragnarstudio.com

By sending, you agree that Ragnar Studio's may reply on WhatsApp about this enquiry.

Ready to start your project?

Tell us what you need. We reply on WhatsApp with questions, next steps and a quote.