Performance
Two years of INP — Core Web Vitals have settled
What changed. It's two years since Interaction to Next Paint (INP) replaced FID as a Core Web Vital (March 2024). The current trio is settled: LCP (loading), INP (responsiveness), and CLS (visual stability). INP is the stricter successor — it measures latency across all interactions, not just the first.
Why it matters. INP punishes heavy JavaScript more than FID ever did, which makes it a quiet ally of AI-readiness: the lean, server-rendered substrate that engines parse cleanly is also the one that scores well on INP. A good INP and a clean DOM tend to come from the same discipline.
What to do. Re-baseline your top templates against the current trio — a target of INP ≤ 200ms is "good." If a page is failing INP, the usual culprit is too much client-side JavaScript; trimming it helps users, vitals, and crawlers at once.
Tracking: Core Web Vitals, INP, LCP, CLS.
Get the Radar monthly
A short monthly digest of everything that moved in the AI web.
No spam. Unsubscribe anytime. We handle your email per our Privacy Policy.