by
FlexaTech
0 (0 reviews)
Flexa Cache
Page cache, Redis object cache, and front-end optimization: static HTML before WordPress boots plus a persistent object cache, zero configuration.
Flexa Cache ranks #61,904 among WordPress.org plugins with 0+ active installations, is #1,311 of 1,658 in the Performance category, and was last updated Sep 28, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1.4
v1.3.2
Current Version v1.3.2
Updated 1 month ago
Last Update on 28 Sep, 2026
Refreshed 1 week ago
Last Refreshed on
#1,311 of 1,658 in Performance
Rank
#61,904
—
No change
Active Installs
0+
-100%
KW Avg Position
151
1 worse
Downloads
637
+2 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
34,336
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 8 more installs to reach 10+
Rank Changes
Current
#61,904
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
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.3.2
- Last Updated
- Sep 28, 2026
- Requires WP
- 5.9+
- Tested Up To
- 7.1.4
- PHP Version
- 8.2 or higher
- Author
- FlexaTech
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- 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,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
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
#36
Speed Optimizer – The All-In-One Performance-Boosting Plugin
1M+ installs
#44
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
#59
Frequently Asked Questions
Common questions about Flexa Cache
On activation, Flexa Cache installs an advanced-cache.php drop-in into wp-content/ and adds define('WP_CACHE', true) to wp-config.php. On the next uncached request, the plugin generates a static HTML file. Every subsequent request for that URL is served directly from the file — no PHP execution, no database query.
Yes. Cart, checkout and account pages are never cached, and once a visitor has something in the cart (or a WooCommerce session) they get live pages for the rest of their visit. Shop pages with filter or sort parameters in the URL are not cached either. A product's cached page is cleared when the product is saved or its stock changes. The JS optimizers also skip cart, checkout and account pages.
The static file cache works on any server (the drop-in uses PHP readfile()). The Gzip and Browser Caching toggles write Apache .htaccess rules; the plugin's class docblocks include the nginx equivalent snippets for hosts that need them.
Click Clear all cached files on the Cache screen, use wp flexa-cache clear from the command line, or call POST /wp-json/flexa-cache/v1/cache/purge. To clear a single URL, use the per-URL input in the Cache Stats panel or wp flexa-cache clear --url=https://example.com/page/.
The Minify JS toggle is a documented safe no-op when used alone. JavaScript is only ever concatenated (via Combine JS), never minified in isolation — the plugin ships no JS parser. If you want JS minification, enable Combine JS together with Minify JS.
Flexa Cache never overwrites an advanced-cache.php that another plugin installed. If one is present, Flexa Cache does not install its own drop-in, and the Cache screen and Site Health warn that another plugin's advanced-cache.php is in place. Deactivate the other plugin (it should remove its own drop-in), then save the Flexa Cache settings again. Flexa Cache also warns you when it finds another caching plugin, a host-level cache or a CDN that caches HTML; see the next question.
Yes, but Flexa Cache cannot clear those caches. When it clears a page, a CDN or server cache in front of your site can keep serving the old copy until its own expiry. Either let only one layer cache HTML, or clear the CDN or host cache after you publish changes. Static files (images, CSS, JS) on a CDN are not affected. If you use "Separate mobile cache" or "Exclude mobile", Flexa Cache sends Vary: User-Agent, but many CDNs ignore it for HTML, so a CDN that caches your pages must be set to tell phones and desktops apart. The Cache screen and Site Health list what was detected, based on the plugins you run, your hosting environment and the response headers of your home page.
Logged-in users, WooCommerce cart/checkout/account pages and shoppers with a cart, URLs with a query string, non-GET requests, wp-admin, admin-ajax.php, the REST API, WP-Cron, feeds, search, previews, 404 pages, password-protected posts, pages that define DONOTCACHEPAGE, and whatever you add to the URL, cookie and user agent exclusion lists. Developers can add their own rule with the flexa_cache/engine/is_cacheable filter.
Open the page in a private window twice and look at the response headers: a page served from the cache has the X-Flexa-Cache: HIT header. You can also watch the cached file count on the Cache screen. To test an exclusion, visit the page, check for the header, then add the exclusion and reload: saving an exclusion change clears the cache, so the page should no longer be a HIT.
Turn off Enable Flexa Cache at the top of General Settings and save. The page cache, every optimization, the widget cache, the Gzip and browser caching rules and the Redis object cache all stop, but each of their switches keeps its saved value. Turn the master switch back on and everything comes back as it was. "Enable page cache" on its own only turns off the page cache. Deactivating the plugin also stops everything, and also keeps your settings.
