In this article · 10 sections
Interaction to Next Paint (INP) is the Core Web Vital that measures responsiveness: how long it takes from a tap, click or key press until the page visibly updates. A "Good" INP is 200 milliseconds or less. If your menus, buttons or forms feel laggy, especially on budget phones, here's how to improve INP.
What causes poor INP
- Long JavaScript tasks blocking the main thread
- Heavy third-party scripts (chat widgets, multiple trackers, ad scripts)
- Expensive event handlers that do too much work on click
- Large DOM (thousands of elements) making updates slow
- Layout thrashing: repeatedly reading and writing layout in loops
- Hydration of large JavaScript frameworks
Step 1: Find slow interactions
- PageSpeed Insights / Search Console: real-user INP for pages and templates
- Chrome DevTools → Performance panel: record while clicking menus, filters, buttons; look for long tasks (over 50ms)
- The Web Vitals extension or
web-vitalsJS library to log INP in the field
Step 2: Reduce JavaScript
- Remove unused libraries and plugins
- Load non-critical scripts later (
defer, on interaction) - Split large bundles
See reduce unused JavaScript and third-party scripts.
Step 3: Break up long tasks
Let the browser paint between chunks of work:
button.addEventListener('click', async () => {
showLoading(); // quick visual feedback first
await new Promise(r => setTimeout(r)); // yield to the browser
doHeavyWork();
});
Newer browsers also offer scheduler.yield() for this purpose.
Step 4: Give instant visual feedback
Update the UI first (pressed state, spinner, open menu), then do heavier work. Users perceive the site as responsive.
Step 5: Optimise event handlers
- Debounce input handlers (search-as-you-type)
- Avoid reading layout (
offsetHeight) and writing styles repeatedly in loops - Use CSS for animations instead of JavaScript where possible. See CSS animation tutorial
Step 6: Keep the DOM lean
Paginate long lists, lazy-render hidden content, and avoid enormous mega menus with thousands of links.
Step 7: WordPress specifics
Heavy page builders, sliders and many plugins are common INP culprits. See speed up WordPress.
Track progress
Field data in Search Console updates over 28 days. Watch the trend after deploying fixes.
FAQs
Is INP a ranking factor?
INP is part of Core Web Vitals, which Google uses as page experience signals. Relevance still matters most, but responsiveness affects users and conversions.
Why is INP worse on mobile?
Phones have slower processors, so the same JavaScript takes longer to run.
Joboo Web builds lightweight sites that respond instantly on budget phones. Get a speed review.
Was this article helpful?
Your answer helps us improve our guides