New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction. | You have to log in to add a translation. | Details |
Original untranslated
Enables browsers to speculatively prerender or prefetch pages to achieve near-instant loads based on user interaction.
You have to log in to edit this translation. |
|||
| ↑ | Speculative Loading | Speculative Loading | Details |
Original current |
|||
| Use the controls in the <strong>Speculative Loading</strong> section to configure speculative loading. | You have to log in to add a translation. | Details | |
Original untranslated
Use the controls in the <strong>Speculative Loading</strong> section to configure speculative loading.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Visit the <strong>Settings > Reading</strong> admin screen. | You have to log in to add a translation. | Details | |
Original untranslated
Visit the <strong>Settings > Reading</strong> admin screen.
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| After activation | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| By default, speculative loading is only enabled for logged-out users, since unauthenticated pages are typically only eligible for caching and so more efficient to prefetch/prerender. This means that sites with frequent logged-in users on the frontend—such as e-commerce, forums, or membership sites—will not benefit from the feature. If your server can handle the additional load (for example, with persistent object caching), you can opt in to enable speculative loading for all logged-in users or for administrators only. This setting exclusively affects frontend pages; admin screens are always excluded. | You have to log in to add a translation. | Details | |
Original untranslated
By default, speculative loading is only enabled for logged-out users, since unauthenticated pages are typically only eligible for caching and so more efficient to prefetch/prerender. This means that sites with frequent logged-in users on the frontend—such as e-commerce, forums, or membership sites—will not benefit from the feature. If your server can handle the additional load (for example, with persistent object caching), you can opt in to enable speculative loading for all logged-in users or for administrators only. This setting exclusively affects frontend pages; admin screens are always excluded.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| This plugin adds support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API">Speculation Rules API</a>, which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/">merged into WordPress 6.8</a>, 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 <em>Settings > Reading</em> admin screen. | You have to log in to add a translation. | Details | |
Original untranslated
This plugin adds support for the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Speculation_Rules_API">Speculation Rules API</a>, which allows defining rules by which certain URLs are dynamically prefetched or prerendered. This core Speculative Loading functionality was <a href="https://make.wordpress.org/core/2025/03/06/speculative-loading-in-6-8/">merged into WordPress 6.8</a>, 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 <em>Settings > Reading</em> admin screen.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| A prerendered page is linked to the page that prerenders it, so personalisation may already be known by this point and changes (e.g. browsing other products, or logging in/out) often require a new page load, and hence a new prerender, which will then take these into account. But it definitely is something to be aware of and test! Prerendered pages can be canceled by removing the speculation rules <code><script></code> element from the page using standard JavaScript DOM APIs should this be needed when state changes without a new page load. | You have to log in to add a translation. | Details | |
Original untranslated
A prerendered page is linked to the page that prerenders it, so personalisation may already be known by this point and changes (e.g. browsing other products, or logging in/out) often require a new page load, and hence a new prerender, which will then take these into account. But it definitely is something to be aware of and test! Prerendered pages can be canceled by removing the speculation rules <code><script></code> element from the page using standard JavaScript DOM APIs should this be needed when state changes without a new page load.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Speculating with the default <code>moderate</code> eagerness decreases the risk that the prerendered page will not be visited by the user and therefore will avoid any side effects of loading such a link in advance. In contrast, <code>eager</code> speculation increases the risk that prerendered pages may not be loaded. Alternatively, the plugin offers to only speculate on mouse/pointer down (conservative) which reduces the risk even further and is an option for sites which are concerned about this, at the cost of having less of a lead time and so less of a performance gain. | You have to log in to add a translation. | Details | |
Original untranslated
Speculating with the default <code>moderate</code> eagerness decreases the risk that the prerendered page will not be visited by the user and therefore will avoid any side effects of loading such a link in advance. In contrast, <code>eager</code> speculation increases the risk that prerendered pages may not be loaded. Alternatively, the plugin offers to only speculate on mouse/pointer down (conservative) which reduces the risk even further and is an option for sites which are concerned about this, at the cost of having less of a lead time and so less of a performance gain.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you are running this plugin on a site without pretty permalinks and are confident that there are no custom query parameters in use that can cause state changes, you can opt in to enabling speculative loading via the <code>plsr_enabled_without_pretty_permalinks</code> filter: | You have to log in to add a translation. | Details | |
Original untranslated
If you are running this plugin on a site without pretty permalinks and are confident that there are no custom query parameters in use that can cause state changes, you can opt in to enabling speculative loading via the <code>plsr_enabled_without_pretty_permalinks</code> filter:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For safety reasons, the entire speculative loading feature is disabled by default for logged-in users and for sites that do not use pretty permalinks. The latter is the case because plugins often use URLs with custom query parameters to let users perform actions, and such URLs should not be speculatively loaded. For sites without pretty permalinks, it is impossible or at least extremely complex to differentiate between which query parameters are Core defaults and which query parameters are custom. | You have to log in to add a translation. | Details | |
Original untranslated
For safety reasons, the entire speculative loading feature is disabled by default for logged-in users and for sites that do not use pretty permalinks. The latter is the case because plugins often use URLs with custom query parameters to let users perform actions, and such URLs should not be speculatively loaded. For sites without pretty permalinks, it is impossible or at least extremely complex to differentiate between which query parameters are Core defaults and which query parameters are custom.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Are there any special considerations for speculative loading behavior? | You have to log in to add a translation. | Details | |
Original untranslated
Are there any special considerations for speculative loading behavior?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| <a href="https://developer.chrome.com/docs/web-platform/prerender-pages">Information on document rules syntax support used by the plugin</a> | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://developer.chrome.com/docs/web-platform/prerender-pages">Information on document rules syntax support used by the plugin</a>
CommentFound in description list item. You have to log in to edit this translation. |
|||
| For client-side JavaScript, is recommended to delay these until the prerender is activated (for example by clicking on the link). Some solutions (like Google Analytics) already do this automatically, see <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">Impact on Analytics</a>. Additionally, cross-origin iframes are not loaded until activation which can further avoid issues here. | You have to log in to add a translation. | Details | |
Original untranslated
For client-side JavaScript, is recommended to delay these until the prerender is activated (for example by clicking on the link). Some solutions (like Google Analytics) already do this automatically, see <a href="https://developer.chrome.com/docs/web-platform/prerender-pages#impact-on-analytics">Impact on Analytics</a>. Additionally, cross-origin iframes are not loaded until activation which can further avoid issues here.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Prerendering can affect analytics and personalization. | You have to log in to add a translation. | Details | |
Original untranslated
Prerendering can affect analytics and personalization.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.