There's a WordPress speed feature most site owners haven't switched on yet, and it makes navigation feel almost instant. It's called speculative loading, it ships in WordPress core now, and it's quietly one of the biggest perceived-speed wins of 2026. The catch is that almost nobody explains it clearly, and plenty of guides confuse the two modes it uses. This is a plain-English walkthrough: what speculative loading actually is, how prefetch and prerender differ, how to turn it on safely, and the one nuance about Core Web Vitals you need to know before you expect miracles.
What is speculative loading in WordPress?
Speculative loading is a WordPress core feature, built on the browser Speculation Rules API, that quietly prefetches or prerenders the next page a visitor is likely to open. When they click, that page appears almost instantly because the browser already started, or finished, loading it.
The idea is simple once you picture it. As a visitor hovers, scrolls toward, or moves their pointer near a link, the browser makes an educated guess that they're about to click it. Instead of waiting for the click, it gets a head start on that destination page in the background. By the time the click actually happens, much of the work is already done, so the new page snaps into view. You don't write any code for this. WordPress generates the speculation rules for your links automatically.
Why does this matter so much in 2026? Because the loading fundamentals, caching, compressed images and a decent server, are now table stakes. Most serious WordPress sites have them. Speculative loading is one of the few levers left that meaningfully changes how fast a site feels once those basics are in place, and it does it for the part of the experience visitors notice most: moving from page to page. It's the difference between a site that's merely fast and one that feels effortless.
How does speculative loading work?
It works through the Speculation Rules API, which tells the browser which links to load early and how aggressively. There are two modes: prefetch downloads the next page's resources, while prerender fully builds the page in the background. An eagerness setting controls how soon the browser acts.
Is prefetching the same as prerendering?
No, and the difference is the whole story. Prefetch downloads the HTML and key resources for the next page but stops short of rendering it, so the click is faster but there's still a small build step. Prerender goes all the way and constructs the page in the background, so when the visitor clicks it's already painted and appears instantly. Prerender feels faster, but it uses more memory and bandwidth, and it can run page scripts early, which matters for the WooCommerce caution below.
| Mode | What the browser does | Feels like | Resource cost |
|---|---|---|---|
| Prefetch | Downloads the next page's resources, doesn't render | Faster click, small build step | Lower |
| Prerender | Fully builds the next page in the background | Near-instant, page already painted | Higher |
The eagerness setting is the other lever. A conservative eagerness only acts when the visitor clearly commits, like on pointer-down, while a moderate or eager setting acts earlier, on hover. Earlier means faster, but it also means more wasted loads for links people never click. WordPress defaults to a sensible, conservative blend so it's safe out of the box.
Our WordPress speed optimization service configures speculative loading, caching and the rest properly, with a guaranteed 90+ PageSpeed result or your money back.
How do you enable speculative loading in WordPress?
On a current WordPress version it's already on by default through core, so there's nothing to install for the basics. For control over prefetch versus prerender and the eagerness level, add the official Speculative Loading plugin, set your exclusions, then test that navigation feels near-instant.
- Confirm you're on a current WordPress. Speculative loading ships in core and is enabled by default, so an up-to-date install already benefits.
- Install the Speculative Loading plugin for control. If you want to choose the mode and eagerness, the official plugin exposes those settings without any code.
- Set eagerness and exclusions. Pick conservative or moderate eagerness, and exclude cart, checkout, account and any logout or action URLs so nothing fires early.
- Test it. Click around your own pages and confirm navigations feel instant, then double-check your excluded pages still behave exactly as before.
If you haven't covered the fundamentals yet, speculative loading works best on a site that's already fast. Our speed up WordPress guide walks through caching, images and the core fixes that this feature then sits on top of.
Does speculative loading improve Core Web Vitals?
Mostly it improves perceived and navigation speed rather than your initial Core Web Vitals scores. Because it speeds up the next page, not the first one a visitor lands on, it doesn't directly lower the entry page's LCP. It can help INP and repeat-navigation feel, though.
This is the nuance other guides skip, so it's worth being precise. Core Web Vitals like LCP are measured on the page a visitor first loads. Speculative loading helps the page they go to next, which the browser preloaded, so the headline LCP of your landing page is unchanged. What it does improve is how the whole site feels as people move through it, and that perceived speed is exactly what keeps visitors clicking deeper and converting. For the full picture of how the three vitals are actually scored, see our Core Web Vitals guide. Treat speculative loading as a perceived-speed bonus on top of solid vitals, not a replacement for fixing LCP, INP and CLS at the source.
When does speculative loading help most?
It helps most on content-heavy sites where visitors move through several pages in a session, like blogs, news sites, documentation and multi-page brochure sites. The more likely a visitor is to click an internal link next, the more often the browser's guess pays off with an instant load.
Think about how people actually browse. On a blog, someone reads one article, then clicks a related post, then another. Each of those clicks is a chance for speculative loading to have already done the work. On a single-page landing site, there's nowhere to go next, so there's not much to preload and the benefit shrinks. That's the simple rule of thumb: the more internal navigation your site encourages, the more speculative loading earns its keep.
There's a sensible way to think about the resource cost too. Yes, prerendering a page the visitor never opens is wasted work. But on a well-cached site, the cost of fetching a page is tiny, and you only pay it for links the browser thinks are likely. WordPress keeps the default eagerness conservative precisely so you get most of the speed benefit without prefetching half your site for no reason. For a typical content site, that trade is well worth it, and visitors feel the difference the moment they click. If you're running a store, lean toward prefetch over prerender and keep your exclusions tight, and you'll get the navigation boost without the early-action risk.
Key takeaways
- Speculative loading preloads the likely next page, so clicks feel near-instant.
- Prefetch downloads, prerender fully builds the page, so they're not the same thing.
- On WooCommerce, exclude cart and checkout so prerender doesn't fire actions early.
- It boosts perceived navigation speed, not your landing page's initial LCP.
- It pays off most on content-heavy sites with lots of internal navigation.