For years, the conversation around WordPress performance has followed a familiar pattern: install a caching plugin, compress your images, maybe add a CDN, and hope for the best. But something shifted with WordPress 6.8. The updates that landed in early 2025 weren’t just maintenance patches or block editor refinements. They addressed performance at the core level in ways that are still being unpacked by developers well into 2026.
The questions coming out of forums and community threads aren’t abstract, either. Site owners want to know whether these updates actually move the needle on Core Web Vitals without layering on additional plugins. That’s a fair and practical question, and the answer is more nuanced than a simple yes or no.
What’s actually new in 6.8 on the performance front
The WordPress 6.8 release announcement highlights two updates worth taking seriously: speculative loading and improvements to Interaction to Next Paint (INP) scores.
Speculative loading is the more technically interesting of the two. The idea is that the browser can begin fetching and rendering pages before a user actually clicks a link, based on the likelihood that they will. WordPress 6.8 introduces native support for the Speculation Rules API, which allows WordPress to hint to the browser about which pages are worth prefetching or prerendering based on link hover behavior and other signals.
In plain terms, this means that for visitors browsing a site, the next page they’re likely to visit can feel nearly instant because the browser has already started loading it in the background. That’s a meaningful experience improvement, particularly on content-heavy sites where readers move from post to post.
The INP improvements are a different kind of fix but equally important. INP, which replaced First Input Delay as a Core Web Vitals metric in 2024, measures how quickly a page responds to user interactions like clicks, taps, and keyboard input. It’s a metric that WordPress sites have historically struggled with, largely because of JavaScript execution overhead in the block editor’s front-end output. The work done in 6.8 reduces some of that overhead, which shows up as faster, more responsive interactions for real users.
Does this replace the need for a performance plugin?
Honestly, not entirely. But that framing might be the wrong way to look at it.
What WordPress 6.8 does is raise the performance floor. A default WordPress installation with a reasonably well-built theme now starts from a better baseline than it did two versions ago. Sites that were already optimized will see incremental gains. Sites that were underperforming due to core-level inefficiencies may see more noticeable improvements.
But speculative loading doesn’t help if images aren’t properly sized or lazy-loaded. INP improvements at the core level don’t cancel out a theme that loads three separate JavaScript libraries for a contact form. The fundamentals of WordPress performance still matter, and they still require attention.
What’s changed is that developers and site owners are no longer fighting against the platform itself as much as they used to. That’s not a small thing.
How speculative loading works in practice
The Speculation Rules API that powers this feature is still a relatively new browser technology, which means support isn’t universal across all browsers yet. Chromium-based browsers (Chrome, Edge, and others built on the same engine) support it well. Firefox and Safari are still catching up.
For WordPress sites, this means speculative loading delivers its benefits to a significant portion of visitors right now, with broader coverage expected as browser support matures. WordPress core handles the implementation automatically, so there’s no configuration required on the site owner’s end. The Speculation Rules are injected into the page output based on sensible defaults.
One thing worth understanding is the difference between prefetching and prerendering. Prefetching downloads the resources for a page in advance. Prerendering goes further and actually renders the page in a background tab so it’s ready to display instantly. WordPress 6.8 uses a conservative approach by default, which is appropriate. Prerendering every link on a page would waste bandwidth and could create unexpected behavior with analytics tracking or server-side logic.
The Core Web Vitals picture in 2026
Core Web Vitals have become a real consideration for site owners, not just a technical checkbox. Google’s use of page experience signals in search rankings means that poor LCP, INP, or CLS scores have visible consequences. WordPress has made steady progress on this front over multiple releases, and 6.8 continues that trajectory.
The most practical takeaway is that keeping WordPress updated is now a more meaningful performance strategy than it used to be. Each release since the performance team formalized their work has shipped measurable improvements. Staying on an older version isn’t just a security risk anymore. It’s leaving performance gains on the table.
At Sweet Mint Studio, we’ve seen this play out with client sites that were overdue for updates. After bringing them current, Core Web Vitals scores improved even before touching anything else. The core updates were doing quiet, useful work that older versions simply didn’t have.
What site owners should actually do
The practical steps here aren’t complicated.
First, update to the latest version of WordPress if you haven’t already. The performance improvements in 6.8 require nothing beyond the update itself to begin working.
Second, test Core Web Vitals scores before and after. Google’s PageSpeed Insights and the Core Web Vitals report in Google Search Console both give a clear picture of where a site stands. Speculative loading improvements show up most clearly in navigation speed, while INP changes are visible in the interaction metrics.
Third, don’t treat a WordPress update as a substitute for good theme and plugin hygiene. A bloated theme or an outdated plugin loading unnecessary JavaScript will still drag scores down regardless of what core does well.
Fourth, keep an eye on browser support data for the Speculation Rules API. As Firefox and Safari add support, the reach of speculative loading will grow without any action required on the site owner’s side.
A platform that’s genuinely improving
There’s sometimes a cynicism in the WordPress community about whether core development is moving in the right direction. The block editor rollout was bumpy, and there are still legitimate debates about complexity and bloat. But the performance work that has shipped over the past several releases represents something genuinely good: a platform that is measurably faster for real users, and getting more so with each update.
Speculative loading and INP improvements aren’t flashy features. They don’t show up in screenshots or demos. But they are the kind of work that makes a real difference to the person reading an article on a phone with a middling data connection, waiting for a page to respond to their tap. That person is who all of this is ultimately for, and it’s worth acknowledging when progress is real.
