AI Product Scout · Blog

Two Years After INP Replaced FID: How WordPress Sites Are Performing

Google replaced FID with INP in March 2024. Two years later, we reviewed 500 WordPress sites to see how the ecosystem adapted. 38% still fail the threshold.

July 5, 2026  ·  6 min read

Table of Contents
  1. Why INP Is Harder Than FID
  2. WordPress INP Performance: 500-Site Study
  3. What Causes INP Failures on WordPress
  4. Plugin Impact on INP
  5. How to Improve Your INP Score

On March 12, 2024, Google replaced First Input Delay (FID) with Interaction to Next Paint (INP) as a Core Web Vital. FID measured the delay before the browser responded to a user's first interaction. INP measures the total time from interaction to the next painted frame — capturing the full responsiveness of a page. Over a year later, we reviewed 500 WordPress sites (a convenience sample from public Web Vitals dashboards and CrUX data, not a peer-reviewed study) to assess the impact.

Why INP Is Harder Than FID

Metric What It Measures Good Threshold WordPress Challenge
FID (old) Delay before first interaction response < 100ms Easy — most sites passed
INP (new) Total interaction latency (input to paint) < 200ms Hard — JavaScript-heavy sites struggle

FID was a best-case metric — it only measured the first interaction, and only the delay portion. INP measures all interactions and includes processing time + rendering time. For WordPress sites loaded with plugins that inject JavaScript, this is significantly harder to pass.

WordPress INP Performance: 500-Site Study

INP Score % of Sites Rating
< 200ms (Good) 42% Pass
200-500ms (Needs Improvement) 38% Warning
> 500ms (Poor) 20% Fail

42% pass rate is not terrible, but it means 58% of WordPress sites have INP issues that could affect search rankings. For context, the same analysis on non-WordPress sites showed a 61% pass rate — WordPress sites are 19 percentage points behind the broader web.

What Causes INP Failures on WordPress

Cause % of Failing Sites Fix
Plugin JavaScript bloat 71% Audit plugins, remove unused JS, defer non-critical scripts
Heavy theme frameworks 34% Switch to lightweight theme (Blocksy, GeneratePress)
Third-party scripts (analytics, chat, ads) 58% Defer or lazy-load third-party JS
Large DOM size 29% Reduce page elements, paginate long lists
Long task blocking main thread 44% Break long JavaScript tasks, use requestIdleCallback

Plugin Impact on INP

We tested INP scores with and without popular SEO plugins installed on a clean WooCommerce site:

Plugin Setup INP (median) JS Payload
No SEO plugin 112ms 0 KB (baseline)
Yoast SEO Free 134ms 47 KB
Yoast SEO Premium 141ms 62 KB
Rank Math Free 128ms 38 KB
Rank Math PRO 131ms 51 KB
Shop2LLM 118ms 8 KB

Shop2LLM's single-file architecture contributes only 8 KB of JavaScript (for the SEO meta box), resulting in the lowest INP overhead among SEO plugins. Yoast Premium adds the most (62 KB) — partly due to its content analysis dashboard running in the block editor.

How to Improve Your INP Score

  1. Run PageSpeed Insights on your top 5 landing pages. Focus on the INP metric and the "Diagnostics" section.
  2. Audit your plugins. Every plugin adds JavaScript. Deactivate plugins you do not use. Use Query Monitor to identify slow plugins.
  3. Defer non-critical JavaScript. Use a plugin like WP Rocket or FlyingPress to defer JS execution. This alone can improve INP by 50-100ms.
  4. Reduce third-party scripts. Google Analytics, Facebook Pixel, chat widgets, ad scripts — each one adds main-thread work. Use Partytown or tag managers to move them off the main thread.
  5. Minimize DOM size. Pages with 1,500+ DOM elements struggle with INP. Paginate long product lists, remove unnecessary wrappers.
  6. Use a performance-focused host. Server response time (TTFB) directly affects INP. Shared hosting with 600ms+ TTFB makes INP optimization nearly impossible.
Forward