by
Weston Ruter
5 (1 reviews)
Instant Back/Forward
Enables back/forward cache (bfcache) for instant history navigations even when “nocache” headers are sent, such as when a user is logged in.
Instant Back/Forward ranks #1,678 among WordPress.org plugins with 10,000+ active installations, is #73 of 1,518 in the Performance category, a 5/5 rating from 1 reviews, and was last updated Sep 12, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.3.3
Current Version v1.3.3
Updated 3 days ago
Last Update on 12 Sep, 2026
Refreshed 6 hours ago
Last Refreshed on
#73 of 1,518 in Performance
Top 5% by installs
Downloads -22.6% this week
Actively maintained
Rank
#1,678
+3 this week
Active Installs
10K+
-40%
KW Avg Position
50.5
0.5 better
Downloads
28.6K
+100 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(1 reviews)
Next Milestone 20K
10K+
20K+
258
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 3,217 more installs to reach 20K+
Rank Changes
Current
#1,678
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
1 reviews
Overall
100%
5
1
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Support Threads Overview
Resolved
Unresolved
1
Total Threads
0
Resolved
1
Unresolved
0%
Resolution Rate
Security History
Source: WPVulnerabilityNo known vulnerabilities on record for Instant Back/Forward. Checked 1 day ago.
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3.3
- Last Updated
- Sep 12, 2026
- Requires WP
- 6.8+
- Tested Up To
- 7.1
- PHP Version
- 7.2 or higher
- Author
- Weston Ruter
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 1
- Support Threads
- 1
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,752
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,007
LiteSpeed Cache
7M+ installs
#5
Wordfence Security - Firewall, Malware Scan, and Login Security
5M+ installs
#11
Hostinger Tools
3M+ installs
#20
WP Super Cache
1M+ installs
#38
Speed Optimizer - The All-In-One Performance-Boosting Plugin
1M+ installs
#43
WP Fastest Cache - WordPress Cache Plugin
1M+ installs
#47
WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance
1M+ installs
#52
Maintenance
1M+ installs
#57
TL;DR
AI summary of the plugin's readmeThis plugin is for WordPress site owners who want faster back/forward navigation for logged-in users or on pages that send no-cache headers. It removes the no-store directive from the Cache-Control header so browsers can use bfcache for instant history navigation while adding safeguards to protect logged-out privacy.
- Enables browser bfcache navigation
- Removes no-store Cache-Control directive
- Bfcache session token cookie safeguard
- Clears cached page after logout
- Requires Remember Me opt-in
- nocache_bfcache_use_remember_me_as_opt_in filter
- Adds private, no-cache, must-revalidate directives
- Removes public directive
Frequently Asked Questions
Common questions about Instant Back/Forward
Please see the Stale Content in Page Caches section of the above blog post.
The functionality in this plugin is proposed for WordPress core in Trac ticket #63636: Enable instant page navigations from browser history via bfcache when sending “nocache” headers. Other relevant core tickets that this revisits: #21938: Add “no-store” to Cache-Control header to prevent history caching of admin resources #55491: Replace unload event handlers from core #57627: The Cache-Control header for logged-in pages should include private #61942: Add “no-store” to Cache-Control header to prevent unexpected cache behavior
Instead of using the pageshow event handler, an alternative method to evict pages from bfcache is to send the Clear-Site-Data: "cache" at logout. Per MDN, this header “sends a signal to the client that it should remove all browsing data of certain types (cookies, storage, cache) associated with the requesting website.” This header is supposedly supported by 91%+ of users according to Can I Use… and it is "Baseline 2023 Newly available" but with an asterisk. In testing, only Chromium-based browsers (e.g. Chrome and Edge) seem to evict pages from bfcache when this header is sent, but there is currently a bug (40233601) where responses with this header can take 10-30 seconds to load. Furthermore, Firefox does not currently evict pages from bfcache with this header, but like Chromium browsers, it does evict pages from HTTP cache, meaning authenticated pages will not be accessible when reopening closed browser tabs. Safari, however, does not seem to evict pages from either bfcache or the HTTP cache. Lastly, Clear-Site-Data only works in a secure context (i.e. over HTTPS), meaning insecure sites still on HTTP would have yet another concern. For all these reasons, Clear-Site-Data is not yet a reliable method to invalidate pages from bfcache. Hopefully the Chromium bug will be fixed in the near future. The Clear-Site-Data header was also mentioned in Trac tickets #49258 and #57627.
Chrome may even now store pages served with no-store in bfcache, although there are still failure scenarios in which bfcache will still be blocked. These can be observed in the “Back/forward cache” panel in the Application tab of Chrome DevTools, for example: JsNetworkRequestReceivedCacheControlNoStoreResource: JavaScript on a page makes a request to a resource served with the no-store directive (e.g. REST API or admin-ajax). CacheControlNoStoreCookieModified: JavaScript on a page modifies cookies. These scenarios happen frequently when browsing the WP Admin, and they occur frequently on the frontend when using plugins like WooCommerce or BuddyPress. Such bfcache failures can also occur when not being logged in to WordPress, as it can happen whenever a site calls nocache_headers(). For example, WooCommerce currently calls nocache_headers() when an unauthenticated user is on the Cart, Checkout, or My Account pages (but see woocommerce#58445 which has been merged to remove this as of v10.1). These failure scenarios do not occur when the no-store directive is omitted from the Cache-Control header.
See the Back/forward cache article on web.dev for reasons why bfcache may be blocked. See also the list of blocking reasons on MDN. See also the YouTube video on Debugging bfcache, make your page load instantly. If you can identify the plugin or theme which is setting Cache-Control: no-store or doing something else that blocks bfcache (like adding an unload event handler), please report the issue to the respective plugin/theme support forum. The Performance Lab plugin also includes a Site Health test for whether the server is sending the Cache-Control: no-store header.
Pantheon sites have a must-use plugin which includes some Page Cache functionality. When a user is logged in, it is currently sending a Cache-Control: no-cache, no-store, must-revalidate response header. This prevents bfcache from working. A pull request has been opened to fix this, but in the meantime you may work around the issue by preventing this header from being sent with the following plugin code: // Workaround for Pantheon MU plugin sending Cache-Control: no-store which prevents bfcache. // See https://github.com/pantheon-systems/pantheon-mu-plugin/pull/94 add_filter( 'pantheon_skip_cache_control', static function (): bool { return is_admin() || is_user_logged_in(); } );
