Interaction to Next Paint (INP) is too slow — the fix
Interaction to Next Paint measures how quickly the page visibly responds to real user interactions (taps, clicks, key presses) across the whole visit. Good is 200 ms or under; over 500 ms is poor. INP is reported from real-user field data.
Where this fits: performance in SEO
Performance is both a ranking signal (Core Web Vitals) and a conversion multiplier. Google measures real-user loading (LCP), interactivity (INP), and visual stability (CLS) — and slow sites lose visitors before analytics even registers them. Most performance issues concentrate in a few repeat offenders: unoptimised images, render-blocking resources, and third-party scripts. Fixing the top three usually moves the needle more than fixing the next thirty.
Why interaction to next paint (inp) is too slow hurts your rankings
INP replaced First Input Delay as a Core Web Vital in 2024 and is a Google ranking signal. A high INP means the interface feels laggy and unresponsive, which frustrates users and reduces conversions — it reflects the experience of your actual visitors, not a synthetic test.
This is a high-severity issue: it directly suppresses rankings or click-through on the pages it affects. It belongs in your current sprint, prioritised by how many pages carry it.
How to fix it
Reduce main-thread work so the browser can respond promptly: break up long JavaScript tasks, defer or remove non-critical third-party scripts, debounce expensive event handlers, and move heavy computation to web workers or requestIdleCallback. Use the DevTools/Lighthouse performance trace to find the slowest interactions.
Performance best practices
- Serve images in modern formats (WebP/AVIF), sized to their container, with explicit dimensions.
- Inline critical CSS and defer everything else; eliminate render-blocking third parties.
- Set far-future cache headers on static assets and an ETag on everything.
- Preload the fonts and hero image; font-display: swap to avoid invisible text.
- Measure with real-user Core Web Vitals, not just lab scores — Google ranks on field data.
The full library: SEO best practices, by category.
Frequently asked questions
What does "Interaction to Next Paint (INP) is too slow" mean?
Interaction to Next Paint measures how quickly the page visibly responds to real user interactions (taps, clicks, key presses) across the whole visit. Good is 200 ms or under; over 500 ms is poor. INP is reported from real-user field data.
Why does interaction to next paint (inp) is too slow matter for SEO?
INP replaced First Input Delay as a Core Web Vital in 2024 and is a Google ranking signal. A high INP means the interface feels laggy and unresponsive, which frustrates users and reduces conversions — it reflects the experience of your actual visitors, not a synthetic test.
How do I fix interaction to next paint (inp) is too slow?
Reduce main-thread work so the browser can respond promptly: break up long JavaScript tasks, defer or remove non-critical third-party scripts, debounce expensive event handlers, and move heavy computation to web workers or requestIdleCallback. Use the DevTools/Lighthouse performance trace to find the slowest interactions.
How serious is this issue?
This is a high-severity issue: it directly suppresses rankings or click-through on the pages it affects. It belongs in your current sprint, prioritised by how many pages carry it. It belongs to the performance family of checks.
How do I find every page affected by this on my site?
Run a free Dr Urls audit: it crawls your site, detects interaction to next paint (inp) is too slow on every affected page, shows example URLs, and generates a ready-to-use fix task. Re-scan after fixing to verify the issue is gone.
Does your site have this issue?
A free Dr Urls audit crawls your site, finds every page affected by interaction to next paint (inp) is too slow, and hands you a ready-made fix task.
Check my site free