INP Under 150ms: Why the "Good" Core Web Vitals Threshold No Longer Cuts It

What Google's Core Web Vitals Measure

Core Web Vitals are three real-user experience metrics Google uses to evaluate page performance: Largest Contentful Paint for loading speed, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. Each metric has a defined threshold, good, needs improvement, or poor, and Google evaluates all three at the 75th percentile of real Chrome user data collected through CrUX, the Chrome User Experience Report.

The 75th percentile measurement is a detail that changes how every score should be read. A page is not passing Google Core Web Vitals if it performs well for the average visitor; it needs to perform well for the fourth-slowest visitor out of every four, typically someone on a mid-range phone with a patchy mobile connection, not a developer on a fiber connection running a Lighthouse test from a desktop browser.

The INP Shift: Why FID's Replacement Changed Everything

Google INP replaced First Input Delay as a Core Web Vital in March 2024, and the transition was more significant than a simple metric swap. FID only measured the delay before the browser started processing a user's first interaction, capturing a fragment of the responsiveness picture. INP measures the worst interaction delay across the user's entire visit, including every click, tap, and keypress throughout the session, and captures three distinct phases: input delay, processing time, and presentation delay.

According to data from the HTTP Archive's 2025 Web Almanac, the transition from FID to INP caused a roughly 5 percentage point drop in mobile Core Web Vitals pass rates, because many sites that looked responsive under FID had slower later interactions INP now captures. Filtering, dropdown menus, form inputs, modal dialogs, anything a user touches after the initial page load, all feed into the INP score. A site that sailed through FID compliance may be quietly failing INP without anyone having noticed yet.

Why 200ms Is Not Good Enough Anymore

Google's official good Core Web Vitals Metrics threshold for INP is under 200ms. That is the number Google Search Console and PageSpeed Insights report against. But there is a gap between passing and competitive that real field data continues to widen.

Top-performing sites in competitive niches consistently target sub-150ms INP, well below the official 200ms good threshold, and industry practitioners have widely adopted 150ms as the de facto competitive benchmark. Across performance-sensitive industries, e-commerce, SaaS, media publishing, sites delivering sub-150ms INP are consistently outperforming sites hovering between 150ms and the 200ms passing threshold.

This matters because of how Core Web Vitals Ranking Factor signals function in competitive search. Google has confirmed Core Web Vitals act as a tiebreaker when two pages have comparable content quality and authority. In tight niches, a site passing at 195ms competing against a site delivering 130ms is, in effect, losing the tiebreaker on every comparable query, even though both technically have a good score.

Core Web Vitals SEO: The AI Overviews Connection

There is a newer dimension to this that extends beyond traditional ranking. Field research tracking AI Overview citation patterns has found that slow sites may be filtered out from AI-generated summaries entirely, even when their content quality is strong. If experience is a filter for AI citation alongside content quality, the performance floor for full search visibility, across both classic results and AI-generated answers, has risen in a way that the official passing threshold does not fully reflect.

Core Web Vitals SEO strategy used to focus narrowly on passing thresholds. The current landscape means that the same work now affects visibility across two distinct surfaces simultaneously, traditional rankings and AI-driven citations, making optimization more consequential than it was even two years ago.

The Three Phases of INP and Where Time Actually Gets Lost

Understanding Google INP at the level needed to actually reduce it requires breaking the metric into its three component phases:

A common mistake in Core Web Vitals Optimization work is addressing only the most visible culprit, heavy JavaScript, while leaving input delay or presentation delay untouched. All three phases contribute to the final INP number, which is why a broad main-thread audit tends to reveal more addressable latency than targeting a single, obvious bottleneck.

How to Improve Core Web Vitals INP: Practical Approaches

The INP scores in practice comes down to reducing what the browser has to do between a user's input and the next visual update. A few approaches that consistently produce measurable results:

• Break up long tasks. Tasks running longer than 50ms on the main thread block the browser from responding to input during that time. Splitting heavy JavaScript tasks into smaller chunks, using scheduling APIs like scheduler.yield(), lets the browser respond between them rather than waiting for a long task to complete.

• Reduce event handler complexity. Complex processing triggered directly by a click or keypress delays the next paint. Where possible, deferring non-critical work until after the visual update through requestAnimationFrame or similar approaches reduces perceived latency.

• Audit and limit third-party scripts. Third-party scripts from ad networks, analytics platforms, and recommendation widgets frequently contribute unexpected main thread blocking. Running a session recording alongside an INP trace often reveals interactions that look clean in code but slow down significantly in real-user conditions due to third-party execution.

• Optimize for mobile specifically. Google primarily uses mobile CrUX data for Core Web Vitals evaluation. Mid-range Android devices running real-world network conditions regularly expose INP problems that a high-end developer machine, even on a throttled connection, can miss entirely.

Core Web Vitals Audit: Reading the Right Data Source

The audit work needs to draw from field data, not lab data, and this distinction trips up a significant share of performance optimization work. Lighthouse and PageSpeed Insights lab scores represent a synthetic test environment. The numbers Google Search Console and CrUX report reflect what real Chrome users actually experienced across the past 28 days.

A site can achieve a perfect 100 Lighthouse score while still failing Core Web Vitals in the field, because the lab environment cannot replicate the real-world combination of device capability, network conditions, and user interaction patterns that CrUX captures. Treating a good Lighthouse score as confirmation of good Core Web Vitals is one of the more consistent mistakes in this space.

For a genuinely useful Core Web Vitals Audit, the primary data source should be Google Search Console's Core Web Vitals report, which shows URL groups failing at the 75th percentile of real user data, and PageSpeed Insights' field data tab showing the CrUX numbers for specific pages. Lab scores are useful for diagnosing specific technical issues once the field data confirms a problem exists.

Core Web Vitals Best Practices for Different Page Types

The best practices shift somewhat by page type, since different pages carry different interaction patterns and different default performance challenges:

• E-commerce product and category pages typically struggle most with INP from filtering and sorting interactions, and with LCP from large product images loaded without explicit size or priority attributes.

• Content and editorial pages tend to be lighter on interaction but heavier on layout shift from lazy-loaded images and dynamically inserted ad units.

• SaaS application pages often carry the heaviest JavaScript loads, since application UI components build on frameworks that can introduce significant processing time for even simple interactions.

• Landing pages built on lightweight templates generally have the easiest time passing all three thresholds, but third-party tracking and exit-intent scripts can introduce hidden INP problems at the moment of highest conversion intent.

Core Web Vitals Impact on SEO: What the Evidence Shows

The impact on SEO is consistently framed by Google as a tiebreaker, not a primary ranking determinant. Content quality and authority remain dominant signals. But the tiebreaker framing undersells the real-world consequence for sites in genuinely competitive niches. Google has documented results like Vodafone Italy seeing 8% more sales from a 31% improvement in LCP, Tokopedia experiencing a 23% increase in average session duration after reducing LCP by 55%, and Nykaa achieving 28% more organic traffic after improving LCP by 40%. These are real-user outcomes from real-site changes, not synthetic projections.

A Core Web Vitals Strategy built purely around staying just inside the good threshold treats Core Web Vitals as a compliance exercise. A strategy built around genuine performance, aiming for sub-150ms INP and sub-2s LCP, tends to produce measurable user experience improvements that affect conversion alongside rankings, compounding the business value beyond any single search visibility gain.

Connecting Core Web Vitals to the Broader Agency Audit Workflow

A Core Web Vitals Audit sits naturally inside the broader technical review agencies run on client sites. Technical health, crawlability, structured data, and now performance benchmarks that affect both traditional rankings and AI citation eligibility, all belong in the same connected workflow rather than being managed through separate, disconnected tools.

Agency Dashboard's website audit tools connect technical site health flagging to the same reporting system used for rank tracking and keyword monitoring, so Core Web Vitals findings do not sit in a separate performance tool nobody revisits after the initial onboarding audit.

Optimize Beyond the Benchmark

Passing Google's official Core Web Vitals thresholds is a floor, not a goal. In competitive niches, the gap between good enough to pass and performing at a level that genuinely differentiates has become a real competitive variable. Sites treating INP as a threshold to clear and forget, rather than a continuing performance target, are leaving ranking and conversion gains on the table that their faster competitors are picking up.

Frequently Asked Questions