Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is Speculative Loading in WordPress?

Short answer

Speculative loading in WordPress lets a supporting browser start loading a page you are likely to visit next, before you click its link. WordPress 6.8 added it to core with a cautious default: prefetch with conservative eagerness, for logged-out visitors on sites with pretty permalinks. Unsupported browsers ignore the rules and load pages in the normal way.

Key takeaways

  • WordPress 6.8 added speculative loading to core on April 15, 2025, with prefetch and conservative eagerness as the default.
  • Prefetch downloads the next page HTML early, while prerender builds the full page in a hidden tab before you click.
  • Speculative loading is off by default for logged-in users and for sites without pretty permalinks.
  • Chrome, Edge, and Opera version 121 or above support the Speculation Rules API features WordPress uses.
  • Sites using the earlier feature plugin improved their LCP passing rate by about 1.9% at the median, based on HTTP Archive and CrUX data.
  • You can change the mode and eagerness with the wp_speculation_rules_configuration filter or the Speculative Loading plugin.

What is speculative loading in WordPress?

Speculative loading in WordPress is a way for the browser to start loading a likely next page before you click its link.

WordPress adds JSON rules to a page, and a supporting browser reads those rules to decide which links to prepare early. The Speculation Rules API is the web API behind this, and WordPress calls the result speculative loading.

The idea is simple: a click often follows a hover, a pause, or the start of a press. If the browser uses that short gap to fetch the next page, the wait after the click shrinks. WordPress.org says speculative loading in WordPress 6.8 speeds up navigation by preloading links before users navigate to them.

It does not change what a page contains. It changes when the browser starts work on the next page.

How does speculative loading work?

Speculative loading works through JSON rules that name links to prepare and say when to start.

WordPress outputs a speculationrules script on front-end pages when the feature is active. Chrome's guide on improving next page load performance explains that rules can list exact URLs or use document rules that match links on the page.

A list rule names specific URLs, such as /pricing/ and /contact/. A document rule matches links by pattern, such as all same-origin links on the page.

The browser treats the rules as hints, not orders. Chrome's prerender guide says Chrome will not speculate when Save-Data is on, when Energy Saver is on with low battery, when memory is limited, or when the page is in a background tab.

What happens after the browser starts?

  • Prefetch: the browser downloads the target page HTML in advance.
  • Prerender: the browser loads and renders the full page in a hidden tab.
  • Activation: when you click, the browser shows the prepared page instead of starting from zero.

If you click before preparation finishes, the browser still has a head start. Chrome says a prerendered page that is activated early moves to the main frame and keeps loading.

What is the difference between prefetch and prerender?

Prefetch downloads only the next page HTML, while prerender loads the full page, including its images, styles, and scripts.

Prefetch is the lighter choice. It skips much of the server wait, because the HTML is already on hand when you click, but the browser still needs to load the page assets after that.

Prerender is the stronger choice. Chrome describes a prerender as a page opened in an invisible background tab, then activated by replacing the foreground tab. That is why a click can feel instant when prerender worked.

The trade-off is cost. Prerender uses more memory, bandwidth, and server work, and it can run page scripts before you visit. Chrome warns not to over-prerender, and to prerender only when the page is likely to be visited.

ModeWhat the browser loadsSpeed gainCost
PrefetchHTML onlyFaster start, less wait for the serverLow
PrerenderHTML, images, styles, scripts, full renderNear-instant click when readyHigher

WordPress core uses prefetch by default. The Speculative Loading plugin uses prerender by default, which is one reason its settings feel stronger.

What are the eagerness settings in WordPress?

Eagerness settings control when the browser starts speculative loading, from at once to only when you press a link.

Chrome lists four levels: immediate, eager, moderate, and conservative. WordPress core exposes three of them through its filter, plus auto, which lets core decide.

The WordPress hook reference says the mode can be prefetch or prerender, and eagerness can be eager, moderate, or conservative. The default for both keys is auto.

EagernessWhen it starts on desktopBest for
ImmediateAs soon as the rules are seenOne or two pages almost certain to be visited
EagerAfter a 10 ms hover, from Chrome 143Likely next pages on a light site
ModerateAfter a 200 ms hover, or on pointer down if soonerA middle choice for most content sites
ConservativeOn pointer or touch downMany links, or a site that wants low waste

Chrome says the default eagerness for list rules is immediate, while the default for document rules is conservative. That split matters, because a document rule can match many links at once.

Chrome also caps how much it speculates. For eager, moderate, and conservative, the limit is 2 at a time on desktop, in first-in, first-out order. For immediate, the limit is 50 prefetches and 10 prerenders.

Is speculative loading turned on by default in WordPress?

Yes, speculative loading is on by default in WordPress 6.8 and later, but only for logged-out visitors on sites with pretty permalinks.

WordPress 6.8, code-named Cecil, was released on April 15, 2025, and WordPress.org lists speculative loading among its headline changes. The release note says older browsers will simply ignore the feature without any impact.

The core default is prefetch with conservative eagerness. That means loading starts when a visitor begins to click a link, not when the page first loads.

Two cases turn it off. The WordPress hook reference says the default value is null for logged-in users and for sites that are not configured to use pretty permalinks, which means speculative loading is entirely disabled there.

Admin screens are also excluded. The feature is for front-end pages only.

Which browsers support speculative loading?

Chrome, Edge, and Opera support the Speculation Rules API features WordPress uses, starting with version 121.

The Speculative Loading plugin page states that support covers Chromium-based browsers such as Chrome, Edge, or Opera using version 121 or above. Other browsers ignore the rules and load pages in the normal way.

That makes speculative loading a progressive enhancement. A visitor on an unsupported browser still gets the same content, just without the early load.

You should not plan a site around it. Use it as a speed bonus for visitors whose browsers support it, and keep normal caching and image work as the base.

Why does speculative loading matter for speed?

Speculative loading matters because it can cut the wait on the next click, which is the part of speed visitors notice most.

A normal click waits for the server, then for HTML, then for assets. Prefetch removes part of the server wait. Prerender can remove most of the wait, because the page is already built when you click.

Chrome says prerendering can give near zero LCP, reduced CLS, and improved INP for the activated navigation. LCP is Largest Contentful Paint, CLS is Cumulative Layout Shift, and INP is Interaction to Next Paint.

Real results depend on the site. Make WordPress Core reports that sites using the earlier feature plugin improved their LCP passing rate by about 1.9% at the median, based on HTTP Archive and CrUX data. That is a median, not a promise for one site.

Before core, the feature ran on over 50,000 WordPress sites through the Speculative Loading feature plugin, according to Make WordPress Core. That history gave the core team field data before the feature shipped in 6.8.

If you want a wider speed plan, start with our guide on how to speed up WordPress. Speculative loading helps the next click, but it does not fix a slow first page.

A CDN can cut first-page load time too, so check how much a CDN costs for WordPress before you add one.

How can you check speculative loading on your site?

You can check speculative loading by viewing the page source in a logged-out browser and looking for a speculation rules script.

Open a front-end page in a private window, so you are logged out. View the page source and search for speculationrules. If the feature is active, you should see a script block with that type.

If you see no such script, check the two common causes first. Are you logged in, or does the site use plain permalinks? Both cases disable the core default.

Next, test a click in Chrome. Open Chrome DevTools, load the page, then press a link and watch whether the next page appears faster than a normal load. Chrome's prerender guide notes that a prerendered page is activated by swapping the hidden page into view, so a ready prerender should feel close to instant.

For a fuller check, look at field data over time rather than one click. A single fast click can come from cache, a fast host, or a light page. Compare navigation speed before and after a change, and watch server load too.

How do you change or turn off speculative loading?

You can change speculative loading with the Speculative Loading plugin, or with a small code change using the core filter.

The plugin adds a Speculative Loading section to Settings > Reading. It defaults to prerender with moderate eagerness, which is stronger than the core default of prefetch with conservative eagerness.

Use the plugin when you want a settings screen and do not want to edit code. Use code when you want a precise setting that stays with your theme or a small custom plugin.

The core filter is wp_speculation_rules_configuration. The WordPress hook reference says it was introduced in WordPress 6.8.0, and that setting the config to null disables speculative loading entirely.

To exclude a link, add the no-prerender class to that link. To exclude a path, use the plugin filter plsr_speculation_rules_href_exclude_paths. Exclude any URL that changes state when visited, such as logout or add-to-cart links.

Chrome's guide also warns not to speculate URLs that trigger state changes, and not to use speculation rules on single-page apps, where navigation does not load a new document.

What mistakes should you avoid?

Avoid treating speculative loading as a fix for a slow site, and avoid speculating every link at the most eager setting.

The first mistake is expecting a big gain on the first page load. Speculative loading helps the next navigation, not the page a visitor lands on from search. If that first page is slow, fix hosting, caching, and images first.

The second mistake is prerendering too much. Chrome caps most eagerness levels at 2 speculations at a time, but eager prerendering can still waste bandwidth and server work when visitors do not click. Start with the core default, then test a stronger setting.

The third mistake is speculating unsafe links. A link that logs a user out, adds a product to a cart, or changes account state should never be prefetched or prerendered. Exclude those paths and check the rule list before you raise eagerness.

The fourth mistake is judging it from one click while logged in. Core disables the feature for logged-in users, so a logged-in test can show no effect even when visitors get the benefit.

Test logged out, in a private window. Compare a caching setup before you blame speculative loading for a slow page.

Frequently asked questions

Does speculative loading slow down my site?

It can add server and bandwidth use, because the browser loads pages that some visitors never click. The core default is light, with prefetch and conservative eagerness, so the added load is small on most content sites. Prerender with eager settings costs more, so test it and watch server load before you keep it.

Does speculative loading work for logged-in users?

No, not by default. WordPress core disables speculative loading for logged-in users, because their pages are often not cached and may show personal content. The Speculative Loading plugin offers an opt-in for logged-in users, but only use it if your server can handle the extra load, for example with persistent object caching.

Does speculative loading help SEO?

It does not add content or links for search engines, and it does not replace caching, image work, or good hosting. It can improve the speed visitors feel when they move between pages, and Chrome links prerendering to better LCP, CLS, and INP for activated navigations. Treat it as a speed aid, not an SEO shortcut.

Should I use the Speculative Loading plugin on WordPress 6.8 or later?

You do not need it for the basic feature, because core already enables prefetch with conservative eagerness. Install it if you want a settings screen in Settings and Reading, or if you want prerender with moderate eagerness without writing code. If you only want the core default, leave the plugin out.

Why do I not see speculative loading in my browser?

Check three things: your WordPress version, your login state, and your browser. You need WordPress 6.8 or later, a logged-out visit, pretty permalinks, and a supporting browser such as Chrome, Edge, or Opera version 121 or above. Unsupported browsers ignore the rules, and logged-in visits get no rules by default.

Sources

  1. Speculative Loading in 6.8 Make WordPress Core
  2. WordPress 6.8 Cecil WordPress.org
  3. wp_speculation_rules_configuration WordPress Developer Resources
  4. Speculative Loading WordPress.org
  5. Prerender pages in Chrome for instant page navigations Chrome for Developers
  6. Improve next page load performance Chrome for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test