Interaction to Next Paint (INP): Fixing a Sluggish Small Business Site
Short answer: Interaction to Next Paint, or INP, measures how long a page takes to visibly respond after a tap, click or key press. Under 200 milliseconds is good, and above 500 milliseconds is poor. Search Console's Core Web Vitals report shows which URL groups fail, and Chrome DevTools shows which interaction is slow and why. The most common causes on small sites are third-party scripts such as chat widgets, tag managers and sliders, plus heavy menus. Remove what you do not use, delay what you can, then retest the same interaction.
What INP actually measures
INP looks at every interaction a visitor makes during a visit, then reports a value close to the slowest typical one. The clock starts when the input happens and stops when the browser paints the next frame that shows the response. A menu that opens after 350 milliseconds, or a button that visibly changes after half a second, will count against you even if the page loaded quickly.
INP replaced an older measure called First Input Delay in 2024. It covers more interactions, so a site that felt fine on first load can still fail once people start using it.
Find the slow pages in Search Console
Open Search Console, go to the Core Web Vitals report and switch to the INP view. It groups URLs into good, needs improvement and poor, separately for mobile and desktop. The report uses real visitor data over a rolling period, so changes take time to appear after a fix.
Note the groups of pages that fail, not just single URLs. Most problems come from a template, such as the product pages or the blog posts, and fixing the template fixes many URLs at once.
Find the slow click in Chrome DevTools
- Open the failing page in Chrome and press F12 to open DevTools.
- Go to the Performance panel and start recording.
- Click the menu, the add to basket button or the chat icon, then stop recording after the screen updates.
- Look for long tasks, which appear as long grey or yellow blocks in the main thread. Click one to see the script or event handler behind it.
Repeat for each interaction you suspect. Take notes of the script names, because they tell you which plugin or app is responsible.
The usual culprits
- Chat widgets and live chat launchers. They often load a large script on every page, even when nobody opens the chat.
- Tag managers with many tags. Each added tag competes for the main thread. Old tags for tools you no longer use are common.
- Sliders and carousels. They recalculate layout and images while the visitor is trying to tap something else.
- Mega menus. A menu with hundreds of links may build its content during the first tap.
- Page builders on WordPress. They can ship a lot of script for features a page does not use.
- Shopify apps. Each app can add its own script to the theme, including review widgets and pop-ups.
Fix in the right order
- Remove what you do not use. Delete apps, plugins and tags that no longer serve a purpose. This is the cheapest and largest win.
- Delay what can wait. Load the chat widget only after a visitor clicks the chat button, and load review widgets after the main content is visible.
- Simplify the menus. Build submenus when the visitor opens them, rather than rendering every link at the start.
- Limit sliders. Replace a carousel with a single image or a short block of text, unless the carousel earns its space.
- Break up the long tasks. If a script runs for more than 50 milliseconds, ask the developer to split the work or defer parts of it.
Test each change alone, then retest the interaction in DevTools. If you change five things at once, you will not know which one helped.
Check the result
After a fix, the lab measurement in DevTools should show the interaction finishing sooner. The field data in Search Console will change more slowly, often over several weeks, because it reflects real visits across a rolling period. Do not panic if it does not move in the first few days.
Measure before and after
Record the interaction in DevTools before you change anything, and save the trace. After each fix, repeat the same click on the same device under the same conditions. Lab numbers vary between runs, so take three runs and compare the typical value rather than the best one.
Field data in Search Console responds more slowly, so keep a dated list of the changes you made. When the report moves, you can match the improvement to the change that caused it. A note that says which plugin was removed on which day is worth more than a vague line saying the site was tidied up.
Plugins versus code
Most small sites reach a fix through plugins, so check whether a plugin is the cause before you disable anything permanently. Deactivate one plugin at a time, retest the same click, and reactivate it if nothing changed. Some plugins add scripts that look harmless but run on every page, and one poor setting can add a long task to every interaction.
FAQ
Is INP a ranking factor?
Core Web Vitals are part of Google's page experience signals, but relevance and content still matter more. Treat INP as a usability fix, because slow clicks drive visitors away whether or not they affect rankings.
Do I need a developer to fix INP?
Many fixes are settings or removals that a site owner can do. Scripts that need splitting or deferring usually need a developer.
Why is my desktop score fine but mobile poor?
Phones have less processing power, so the same script takes longer to run. Test on a real phone or a throttled profile in DevTools.
Will a faster server fix INP?
Not on its own. INP is about what happens in the browser after the page loads, so client-side scripts are usually the cause.
If you would like us to find the slow interactions on your site and fix the worst ones first, tell us which platform you use.