Skip to content

Technical SEO

How to Fix a Poor INP Score

By Shayan Ahmad · · 6 min read

How to Fix a Poor INP Score (WhiteLinko blog banner)

A poor INP score means the page is slow to react after someone clicks, taps or presses a key. The first paint may look acceptable, then the menu, the filter, the add-to-cart button or the accordion hangs before anything changes. Interaction to Next Paint is the Core Web Vital that captures that delay. This guide is for developers who need to find the long tasks and heavy scripts behind it, and fix them in a way that shows up in field data, not only in a lab report.

INP looks at interactions throughout the visit, not only the first one. That is why a page can pass a load-focused test and still fail INP once real users start using the interface.

What a Poor INP Score Is Telling You

For each interaction, the browser has to handle the event, run your JavaScript, and paint the next frame. INP records how long that takes, and the page's score is based on the slower interactions, not the best case. Google currently treats 200 milliseconds or less as good, and values above 500 milliseconds as poor. Those thresholds are a target, not a substitute for watching the page on a mid-range phone.

The work is almost always on the main thread. If a long task is already running, the click has to wait. If your click handler then does too much work, the wait gets worse. If the DOM update is large, the paint itself is slow. Your job is to find which of those three is dominating, on the templates that Search Console has marked as poor.

Find the Interactions and the Long Tasks

Start with field data so you are not debugging the wrong page. In Search Console, open the Core Web Vitals report, switch to INP, and note which URL groups fail. Product pages, collection filters and article templates are common. Then open a representative URL in Chrome, with Performance or the Web Vitals tooling enabled, and use the page the way a customer would: open the menu, change a variant, apply a filter, add to cart, open a drawer.

What to look for in the performance trace

  • Long tasks around the moment you clicked, especially those over 50 milliseconds, and whether they started before or after the input.
  • Event handlers that do too much in one go: large DOM writes, forced layout, expensive loops, or work that could be deferred.
  • Third-party scripts, tag managers, chat widgets, reviews apps and A/B testing tools running on the main thread at the same time.
  • Hydration or framework boot work that still has not finished when the user tries to tap.

If you cannot reproduce a delay in the lab, look at real-user traces if you have them, or test on a slower device and a throttled CPU. Many INP problems appear only when the CPU is busy, which is the normal state of a mid-range phone on a store page full of apps. A first pass with our free page speed check will not replace a trace, but it will often name the heavy scripts that belong in the investigation.

Fix the Causes You Actually Find

There is no single INP patch. The right fix depends on what the trace shows.

Break up or defer long tasks

If the main thread is busy with work that does not need to finish before the next paint, split it. Yield, schedule it after the interaction, or move it off the critical path. That includes third-party initialisation that currently runs on load. Chat widgets, analytics enhancers and recommendation carousels can usually wait until the user has had a chance to interact, or until they are close to the part of the page that needs them.

Make the click handler cheap

The handler should update the interface first and do the heavy work after. If adding to cart requires several network calls and a large re-render, show an immediate state change, then finish the rest. Avoid layout thrashing, and do not query and write the DOM in a tight loop. If a framework re-renders a large tree for a small change, narrow the update.

Reduce the script weight on the template

INP often improves most when you remove or delay code that should not have been on the page at all. Audit app embeds, leftover tag-manager containers, unused polyfills and scripts that still load on templates that do not use them. Stores are frequent offenders because apps are added quickly and removed slowly. This is one of the first things we look at in technical SEO reviews of slow templates, and it is a common theme when we compare technical SEO approaches that go beyond a lab score.

Pay Special Attention to Filters, Menus and Cart Actions

The interactions that usually drag INP down are the ones customers use most:

  • Mobile menus and drawers. Large hidden DOM, animated transitions and extra scripts that run when the menu opens.
  • Faceted filters. Re-rendering the whole product grid on every tap, or waiting for a slow request before any visual feedback.
  • Variant pickers and add to cart. Synchronous work, heavy cart drawers, and third-party upsell scripts hooked into the same click.
  • Accordions and tabs. Simple UI that has been over-wrapped in a library, or that causes a large layout recalculation.

Fix those patterns at the template level. One good product page fix will not move the Search Console group if the rest of the template is unchanged. After you ship, watch the INP group in Search Console for a few weeks. Field data lags, so do not judge the release on the next day's lab run alone.

If the same page also has conversion issues, handle the two together. A faster filter is both an INP fix and a usability fix, which is why this work often sits next to conversion rate optimisation on product and listing pages.

How to Confirm the Fix

Measure the specific interaction before and after, on a throttled CPU, and confirm the long task has gone or been split. Then wait for field data. If INP stays poor while the lab looks clean, you are probably missing a script that only loads for some users, such as a chat widget, a consent tool or a personalisation tag. Check those paths separately.

Also confirm you have not broken the interaction itself. A delayed widget is fine. A filter that no longer updates, or a cart button that fails while you optimise the handler, is not.

FAQs

Why is INP poor when LCP looks fine?

They measure different moments. LCP is about showing the main content. INP is about responding after the user interacts. A page can paint its hero image quickly and still run heavy JavaScript when someone taps a filter.

Can I fix INP by delaying all JavaScript?

Delaying work that is not needed for the first interaction often helps. Delaying the script that actually powers the button will make INP worse, or make the control look broken. Be selective.

Do third-party tags really affect INP that much?

They can, especially when several of them run on the main thread around the same click, or when they start heavy work on every page load just as the user tries to interact. Measure them rather than assuming, then delay or remove the ones that show up in the trace.

How long before Search Console shows an improvement?

Field data is collected over time and reported with a delay. Expect to wait weeks, not hours, and make sure enough users are hitting the updated template before you judge the result.

Need Help Isolating an INP Problem?

If you can feel the delay but the traces are noisy, or you need a clear list of which scripts to delay first, a technical review will save a lot of trial and error. Start with a free SEO audit and we will point you at the templates and interactions that are doing the most damage.

  • inp
  • core web vitals
  • javascript
  • page speed
  • technical seo

Have a question about this for your own site?

A 15-minute call is usually enough to tell whether it applies to you and what to do first.

Book a 15-min callGet My Free SEO Audit

Related posts

Core Web Vitals Explained for Business Owners (WhiteLinko blog banner)

Technical SEO

Core Web Vitals Explained for Business Owners

LCP, INP and CLS explained in plain English for business owners: what each Core Web Vital measures, why it matters for sales, and how to read a report.

All blog posts →

Talk to WhiteLinko

Want this applied to your site?

Book a 15-minute call to talk through your goals, or start with a free SEO audit: a prioritised list of fixes, reviewed by a specialist.

Free PDF · 2026 edition

The WhiteLinko SEO Checklist

Six pages of tick boxes: technical, on-page, content, local, links, AI search and GA4.

Get the checklist
Free SEO Audit