web-platform-tests / web-platform-tests/interop
Speculation Rules API
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Description
Speculation rules offer a way to preemptively load pages for future navigations before the user has actually clicked a link.
Developers can opt to either prefetch, prerender or prerender_until_script.
Specification
https://html.spec.whatwg.org/multipage/speculative-loading.html#speculative-loading
web-feature
https://web-platform-dx.github.io/web-features-explorer/features/speculation-rules/
Test Links
https://wpt.fyi/results/speculation-rules?label=master&label=experimental&aligned&q=speculation
Additional Signals
The Speculation Rules API has been supported in Chrome and Edge since version 109.
The feature has 25 👍 in the developer signals repo.
Speculation Rules had 40 👍 In Interop 2026 and 30 👍 in Interop 2025.
Standards positions:
- Firefox initially expressed a neutral position but have a partial implementation in Firefox Nightly.
- Webkit have expressed support only for same-origin prefetch with an eagerness of conservative.
There are certain aspects of the spec that still seem to be in progress:
- Chromium has an in-progress bug for adding external file support. There is an open pull request for adding this to the specification. There are separate Mozilla and Webkit standards positions for using an external speculationrules file rather than inlining.
- Chrome has been running an origin trial for
prerender-until-script
The State of HTML 2025 survey revealed that a majority of developers have not yet heard of this feature, but it is already being used by some large companies such as Shopify, WordPress, Etsy and Google.
This tweet about the API has 558 likes and this other tweet has 1000 likes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Speculation Rules API specification and the linked WPT results for speculation-rules to determine what coverage the Interop project would need. The issue names no repository files or tests and does not define a requested change, so the expected coverage and completion criteria require clarification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100