INP, the Core Web Vital That Replaced FID: How to Fix It

●1 ●11 ●67
calendar_today • schedule1 min read
— Originally published at built2winweb.com

Interaction to Next Paint tracks how fast a page shows a visible reaction to a click, tap or key press. It took over from First Input Delay as a Core Web Vital on March 12, 2024. Good is 200 milliseconds or less and poor is over 500, measured at the 75th percentile of real visits. Many sites that passed FID easily fail INP because it covers every interaction in a visit and includes running your code and painting the result.

In the guide I explain what counts as an interaction (clicks, taps and key presses, not scrolling or hovering) and the three phases of each one: input delay, processing duration and presentation delay. Knowing which phase is slow tells you which fix applies.

Measurement starts with field data from CrUX, PageSpeed Insights and Search Console, then moves to DevTools with CPU throttling to reproduce problems. The web-vitals library's attribution build tells you which element was slow for real visitors and how long each phase took.

The fixes come in three groups: break up long tasks and yield to the main thread (with scheduler.yield() where supported); cut rendering work by avoiding layout thrashing, keeping the DOM small and using content-visibility; and tame input handlers with debouncing while deferring or removing third-party scripts. I'm clear about limits too: INP isn't a ranking shortcut, field data moves slowly, and a fast spinner doesn't fix slow work.

Key takeaways

  • Good INP is 200 ms or less at the 75th percentile
  • Each interaction has input, processing and presentation phases
  • Use field data first; Lighthouse doesn't measure INP
  • Break up long tasks and yield to the main thread
  • Debounce heavy handlers and audit third-party scripts

Related on BuiltToWinWeb: Core Web Vitals explained

Read the full guide on BuiltToWinWeb: The full INP explainer and fixes

A summary by Jacob Campbell of an article first published on built2winweb.com on October 6, 2026.

🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

How to Fix Core Web Vitals: LCP, CLS & INP | FloxoLab

floxolab - Oct 16

Core Web Vitals Benchmarks for Shopify Stores (2026 Data)

ApogeeWatcherverified - Sep 16

How AI Is Changing Web Development, and What Developers Still Need to Understand

Daniel Decker - Nov 10

The Memory Leak in addEventListener You’re Ignoring

Joemetry - Oct 15

Understanding INP: The Newest Core Web Vital and Why It Matters

ApogeeWatcherverified - Apr 23
chevron_left
3.5k Points • 79 Badges
Worldwide • built2winweb.com
35Posts
12Comments
52Connections
100% custom PHP code from scratch. One-time flat fee — no monthly fees, no plugin bloat. Lightning-f... Show more

Related Jobs

View all jobs →

Commenters (This Week)

6 comments
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!