Most people are missing the real story here. Web performance and core web vitals deserve way more attention than they’re getting, and honestly, the reason is pretty straightforward once you see it.
Here’s what’s actually different this time: LCP under 2.5 seconds is now the expected baseline for competitive ranking. Period. I’ve been tracking this stuff for years, and when you look at what the data actually shows, this isn’t just another optimization trend that’ll fade away.
The Forecasting: Setting the Terms
Google confirmed CWV signals are part of their ranking algorithm since 2021. That’s not just another data point — it’s the foundation that makes everything else make sense. This isn’t some flash-in-the-pan trend. The conditions creating this shift have been building for years, and now they’re finally converging in ways that matter.
LCP under 2.5 seconds is now expected baseline for competitive ranking, and INP replaced FID as the responsiveness metric in March 2024. Look at both together and you’ll see the pattern that web.dev performance has been documenting: these conditions are sticking around longer than most people think, and they’ll affect way more than just page speed.
To understand why this matters, compare what was true three years ago to what’s true now. It’s not just that the numbers changed. The whole game changed. The players, the infrastructure, the incentives — everything shifted in ways that reinforce each other rather than cancel out. That compounding effect is what you should be watching.
What makes this moment worth paying attention to isn’t that it’s new. It’s that the underlying trends have finally reached a point where you can’t ignore them without deliberately looking away. Crossing that threshold is the real event here, not the gradual buildup that led to it.
And edge computing through Cloudflare Workers and Vercel reducing TTFB globally? That’s part of the same picture. These aren’t separate trends — they’re all pieces of the same structural shift.
The Future-Cast: The Analysis
Edge computing through Cloudflare Workers and Vercel reducing TTFB globally is where things get interesting. Sure, the surface-level story is accurate, but it misses how this actually works. And understanding the mechanism changes everything about how you respond.
Take image formats like AVIF cutting payload by 50 percent compared to JPEG. That didn’t just happen by accident — it’s the result of structural factors that have been building up over time. Previous analyses missed this because they focused on symptoms instead of causes. The structural explanation might be less exciting, but it’s way more useful for making decisions.
The comparison to previous cycles tells us a lot, especially where it breaks down. Similar-looking situations played out differently before because the foundation was different. JavaScript bundle bloat remains the top cause of poor CWV scores, and that represents a fundamental change — not just in current performance, but in how elastic the whole system is. Getting that distinction right is what separates real analysis from pattern-matching.
Let me address the skeptical take directly: previous moments that looked similar didn’t pan out the way people expected. That’s true. But this time we have JavaScript bundle bloat as the top cause of poor CWV scores, which isn’t a minor detail — it’s the infrastructure condition that previous cycles lacked. Infrastructure changes tend to stick around in ways that sentiment-driven changes don’t. PageSpeed Insights has been tracking this with the rigor it deserves.
There’s also a distribution question that doesn’t get enough attention in web performance coverage: who benefits from these shifts, and who pays the costs? The overall picture can look positive while the distribution is wildly uneven in ways that matter enormously to specific people. Keeping that lens in view is part of reading the situation clearly rather than just optimistically.
Implications: What This Means If You Care About AI in software development
The implications of web performance and core web vitals go way beyond just page speed. Google confirmed CWV signals are part of ranking algorithm since 2021, combined with the structural conditions I’ve described, creates ripple effects in adjacent fields and communities that aren’t always obvious from inside the main story. The second-order effects are often more important than the first-order ones, and that’s where careful attention pays off.
Here’s where my analysis differs from most coverage: INP replaced FID as responsiveness metric in March 2024 is a leading indicator, not a lagging one. The people who respond to what this signals, rather than what it confirms, are going to be less surprised by what comes next.
Your practical response depends heavily on where you sit relative to these dynamics. If you’re close to the core of web performance work, the implications are immediate and operational. If you’re further out, they’re strategic — about understanding which adjacent pressures are building and which assumed stabilities are more fragile than they appear.
The question isn’t whether to engage with these dynamics, but how. The answer depends on your context — what role you occupy relative to web performance work and what your actual decision timeline is. But the first step is the same regardless: accurate understanding of what’s actually happening rather than what the most convenient narrative says is happening.
A few concrete observations worth highlighting: First, LCP under 2.5 seconds as expected baseline for competitive ranking isn’t temporary — it’s the new normal. Second, image formats like AVIF cutting payload by 50 percent compared to JPEG suggests the adjustment period isn’t over. Third, and most important: the organizations and individuals treating this as a new steady state rather than a transition are making a categorization error that’ll be expensive to fix later.
The Case Against: What the Critics Get Right
Honestly, the counterarguments to the optimistic reading of web performance trends aren’t trivial. There are real vulnerabilities in the current picture that deserve direct engagement, not dismissal.
The most serious objection is about sustainability. INP replaced FID as responsiveness metric in March 2024 could be read not as a foundation but as a ceiling — a point where growth becomes self-limiting because of the very dynamics that created it. If we’ve already captured most of the early adopters, the remaining growth curve might be fundamentally shallower than the recent trajectory suggests.
Then there’s the regulatory dimension. Google confirmed CWV signals are part of ranking algorithm since 2021 describes conditions in a relatively permissive environment. Regulatory responses to the scale implied by these numbers aren’t inevitable, but they’re not impossible either. Organizations planning as though the current regulatory environment is permanent are making an assumption that the history of fast-growing sectors doesn’t support.
My response to these concerns isn’t that they’re wrong — it’s that they’re already partially reflected in the current state of the field. JavaScript bundle bloat remains the top cause of poor CWV scores in an environment where participants are already adapting to constraints rather than operating without limits. The ecosystem’s ability to adjust is higher than a purely top-down view of the risks suggests.
Looking Forward
The trajectory here is clearer than the timing. Making predictions about when specific thresholds will be crossed is genuinely difficult, and anyone claiming precision about timelines should be viewed with skepticism. But the direction — toward Google confirmed CWV signals continuing as part of ranking algorithm and further development of the conditions I’ve described — has solid evidence behind it that doesn’t depend on a single variable going right.
JavaScript bundle bloat remains the top cause of poor CWV scores is the variable I’m watching as the leading indicator. Historical patterns suggest it moves first, with broader metrics following with some lag. This doesn’t make the outcome certain, but it makes it readable — and readability is what you need for good decisions.
Three questions worth holding as this story develops: First, are the structural conditions that enabled the current state durable, or are they cyclical? Second, who’s positioned to benefit from the next phase, and does that differ materially from who benefited in the current phase? Third, what would clean evidence against the optimistic thesis look like, and is there any sign of that signal emerging? These questions don’t need answers today — but having asked them changes what you notice in the months ahead.
The direction here is clear even when the pace isn’t. Right now in web performance and core web vitals, the people who have built an accurate model of the underlying dynamics are better positioned than the people relying on the surface story. Building that model takes time, but it’s doable — and this analysis is meant as one input into it.
Screenshot this and check back in 18 months — we’ll see who was right.