Skip to content

Commit 347a3de

Browse files
swissspidywestonruterdesrosj
authored
Merge pull request #2120 from WordPress/update/speculative-loading-readme
Co-authored-by: westonruter <[email protected]> Co-authored-by: swissspidy <[email protected]> Co-authored-by: desrosj <[email protected]>
2 parents f1e5c20 + 1614ac1 commit 347a3de

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

plugins/speculation-rules/readme.txt

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,7 @@ Enables browsers to speculatively prerender or prefetch pages to achieve near-in
1111

1212
== Description ==
1313

14-
This plugin adds support for the [Speculation Rules API](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API), which allows defining rules by which certain URLs are dynamically prefetched or prerendered.
15-
16-
See the [Speculation Rules WICG specification draft](https://wicg.github.io/nav-speculation/speculation-rules.html).
17-
18-
By default, the plugin is configured to prerender WordPress frontend URLs when the user interacts with a relevant link. This can be customized via the "Speculative Loading" section in the _Settings > Reading_ admin screen.
14+
This plugin adds support for the [Speculation Rules API](https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API), which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was [merged into WordPress 6.8](https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/), but it only prefetches with conservative eagerness by default. In contrast, this plugin defaults to prerendering with moderate eagerness (i.e. when interacting with a link), and it provides a user interface to customize the mode and eagerness via the "Speculative Loading" section on the _Settings > Reading_ admin screen.
1915

2016
A filter can be used to exclude certain URL paths from being eligible for prefetching and prerendering (see FAQ section). Alternatively, you can add the `no-prerender` CSS class to any link (`<a>` tag) that should not be prerendered. See FAQ for more information.
2117

0 commit comments

Comments
 (0)