LumenCache
RAM-first full-page caching that serves pages before WordPress loads, with automatic WooCommerce and LMS integration.
Solid choice
LumenCache is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites and was last updated 4 days ago, and scores 66/100 on our health check.
- Actively developed — last update 4 days ago
- Tested with the latest WordPress (7.1)
- Small user base (10+ active installs)
- Very few reviews so far
- Needs PHP 8.1 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where LumenCache stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| cache | >100 |
| full page cache | >100 |
| Page Speed | >100 |
| performance | >100 |
| woocommerce | >100 |
Version adoption
Share of active sites per release.
About LumenCache
From the official readme · v1.7.5Description
LumenCache implements a RAM-first full-page cache with a WordPress
advanced-cache.php drop-in. On a cache HIT, the drop-in serves complete HTML
before the normal WordPress bootstrap and database queries. This early-response
path reduces application-layer work and keeps repeat page requests fast across
Nginx, Apache, and LiteSpeed.
The cache is designed to fail open when its storage layer is unavailable, so a
cache connection problem does not take the WordPress site offline.
Research Foundation
Academic Reference:
“Dynamic Resource Mapping in Zero-Reload Server Architectures: Eliminating
Application-Layer Latency and Extension Dependency in High-Concurrency CMS
personalised requests continue through the full WordPress stack.
This architecture is intended to reduce repeated bootstrap work, database
queries, and extension overhead while preserving WordPress compatibility. It
also provides a practical bridge between academic performance research and
everyday publishing workloads, including content-heavy sites, WooCommerce
catalogues, and membership-driven pages.
Research author: Professor Nasrul Eam — Dean, Light & Composition University.
Ten-Subsystem Architecture
- RAM-First Full-Page Cache Engine — PHP stores complete HTML at
shutdown and resolves repeat requests from the in-memory cache layer. - Nginx / Apache Proxy Bridge — Static or dynamic server config bypasses
PHP entirely for cache hits. - Selective Bypass Cookie Router —
sys_active_statecookie routes
logged-in users and cart-active visitors to live PHP. - Application Driver Profile Engine — Auto-detects WooCommerce,
LearnDash, LifterLMS, MemberPress, BuddyBoss and registers tailored bypass
rules and invalidation hooks. - Surgical Cache Invalidation — Post save / nav menu / widget / theme
switch events trigger precise per-URL or full purges. - REST API State Endpoint —
/wp-json/lumencache/v1/user-stateserves
personalised fragments for skeleton-hydration clients. - Skeleton Hydration DOM Worker —
skeleton-hydration.jsreplaces cached
placeholders with live content on load. - WP-CLI Management Interface —
flush,flush-url,statuscommands.
Configuration (optional)
All settings are configurable from LumenCache → Settings in the WordPress
admin. Optionally override any setting via wp-config.php — constants always win:
define( 'LUMENCACHE_REDIS_HOST', '127.0.0.1' );
define( 'LUMENCACHE_REDIS_PORT', 6379 );
define( 'LUMENCACHE_REDIS_SOCKET', '' );
define( 'LUMENCACHE_REDIS_PASSWORD', '' );
define( 'LUMENCACHE_REDIS_DATABASE', 0 );
define( 'LUMENCACHE_REDIS_TIMEOUT', 1.0 );
define( 'LUMENCACHE_REDIS_PREFIX', 'cache:' );
define( 'LUMENCACHE_CACHE_TTL', 86400 );
define( 'LUMENCACHE_CACHE_SALT', '' );
define( 'LUMENCACHE_CACHE_QUERY_STRINGS', false );
define( 'LUMENCACHE_PROXY_PASSWORD', '' );
WP-CLI
wp lumencache flush
wp lumencache flush-url https://example.com/page/
wp lumencache status<h3>Privacy</h3>
LumenCache stores rendered page HTML and cache metadata in the in-memory cache
service configured by the site administrator. It does not send cache contents,
visitor data, or analytics data to a third-party LumenCache service. The
optional user-state endpoint returns only the requested dynamic values to the
requesting browser; sites should review those values and their own privacy
policy before enabling personalized hydration.
Frequently asked questions
Getting a 502 Bad Gateway on Nginx after activating or during WooCommerce use?
Nginx has a default fastcgi_buffer_size of only 4KB–8KB. When combining rich caching headers with WooCommerce session cookies, the upstream response header exceeds this limit. Nginx immediately terminates the connection with: upstream sent too big header while reading response header from upstream, resulting in an instant 502 Bad Gateway error. To resolve this, add the following FastCGI and proxy buffer directives to your Nginx configuration (within the http {}, server {}, or PHP location block): fastcgi_buffer_size 32k; fastcgi_buffers 16 16k; fastcgi_busy_buffers_size 32k; proxy_buffer_size…
Why are 0 pages cached?
Two common causes: 1. Nginx config not applied — visit Server Setup and paste the config blocks. 2. WooCommerce session cookie — fixed in v1.1.0. Previous versions bypassed the cache for all visitors on WooCommerce sites due to the always-present wp_woocommerce_session_* cookie.
Why can key salting affect server-level caching?
When LUMENCACHE_CACHE_SALT is set, PHP stores keys as SHA-256 hashes. A server-level configuration must use the same key strategy or it will produce cache misses. Disable the salt for a plain-key configuration, or use the compatible hashed-key server template.
Does LumenCache work with LiteSpeed?
Yes. LiteSpeed supports Apache-compatible .htaccess rewrites. LumenCache uses the Apache proxy mode on LiteSpeed. For better performance, ask your host which in-memory cache acceleration options are available.
Can I still use wp-config.php constants?
Yes — constants always take precedence over admin settings. If you define a constant, the corresponding field in the Settings tab is shown locked (read-only).
Changelog
High-performance bypass routing and Speculation Rules update featuring immediate intra-request cookie state mirroring, cart item removal recovery, reverse proxy HTTPS hardening, and expanded prefetch/prerender safety guards.
1.7.5 (October 6, 2026)
- REST API GUEST HYDRATION RESILIENCY: Hardened
/wp-json/lumencache/v1/user-stateto gracefully isolate guest-safe keys (cart-count,cart-total) when unauthenticated requests contain mixed-key requests (such as headers rendering both cart widgets and member greetings), preventing 403 authorization rejections from breaking guest cart hydration. - LCU LMS & SENSEI COURSE PROGRESSION: Added native student course progress resolution for Light & Composition University’s LMS (
Educational_Products_LMS_Progress) and Sensei LMS, alongside existing LearnDash and LifterLMS integrations; addedlumencache_resolve_course_progressandlumencache_enqueue_hydration_scriptfilters. - SKELETON HYDRATION PROGRESS BARS & REHYDRATION API: Enhanced
skeleton-hydration.jsto dynamically update progress bar widths (role="progressbar",.lms-progress-bar,.progress-bar) and supportdata-lumencache-suffixattributes; exposedwindow.lumenCacheHydrateAPI and registeredlumencache:rehydrateevent listener for AJAX catalog pagination and mini-cart drawers. - WP-CLI STACK COMMAND ENHANCEMENTS: Added
wp lumencache flush-allsubcommand alias,--url=<url>flag support forflush-url, and enrichedwp lumencache statuswith HTTP 304 ETag status, Speculation Rules API state, storage driver, SWR grace periods, browser cache TTL, Apache/LiteSpeed RAM Proxy status, and Pro status. - WP-CLI AUTOMATION PROVISIONING: Added
wp lumencache deploy-dropin,wp lumencache remove-dropin,wp lumencache write-htaccess, andwp lumencache remove-htaccesssubcommands for automated headless server provisioning and CI/CD pipelines. - PRO COMPATIBILITY BRIDGE & DUAL HOOK DISPATCH: Restored
lc_is_pro_active()andlc_has_pro_feature()legacy function aliases; added dual hook dispatching for all five Pro administrative sections (lc_render_pro_*andlumencache_render_pro_*); added legacylumencache_render_pro_panel()andlc_render_pro_panel()compatibility bridges.
1.7.4 (October 6, 2026)
- TAB CONTINUITY & FORM REDIRECTION: Injected explicit
from_tabhidden inputs across Settings, Cache Controls (Flush All, Purge URL), and Server Setup action forms, guaranteeing that all form submissions and admin-post actions reliably redirect administrators back to their active working tab. - HTACCESS ERROR RESILIENCY: Hardened
handle_htaccess_write()to validateWP_Errorreturn states fromHtaccess::write_rules(), passing distinct error notices with diagnostic messages instead of reporting false positive success on filesystem permission failures; added distincthtaccess=removedhandling for rule deletions. - APACHE & LITESPEED SERVER SETUP CARD: Introduced dedicated “Apache / LiteSpeed Direct RAM Proxy (.htaccess)” management card on the Server Setup tab for Apache and LiteSpeed environments, providing real-time deployment status, one-click rule write/remove controls, and a copyable rewrite rules block.
- TEN SUBSYSTEMS OVERVIEW MATRIX: Expanded “Core Engine Systems” on the administrative overview to feature all ten subsystems, providing live status and operational descriptions for the new HTTP 304 & ETag Validation Engine and Next-Gen Speculation Rules API Engine.
- MULTI-DEVICE RESPONSIVENESS (<620px, <480px): Overhauled admin layout styles with responsive column-wrapping for all settings labels and input controls on viewports <=620px, single-column metrics card grid on screens <=480px, column layout for URL purges, and >=40px touch targets for mobile usability.
1.7.3 (October 6, 2026)
- INTRA-REQUEST STATE SYNCHRONIZATION: Enhanced
Cookie_Router::set_active_cookie()to immediately mirror active state into superglobal$_COOKIE['sys_active_state'] = 'true', ensuring all downstream checks and speculation suppression evaluate correctly within the identical PHP lifecycle. - RECOVERY ON CART ITEM REMOVAL: Added
woocommerce_cart_item_removedlistener toCookie_Router, automatically clearingsys_active_stateand restoring high-speed RAM caching when a guest shopper removes the final item from their cart. - REVERSE PROXY SSL RESILIENCY: Hardened cookie dispatch in
Cookie_Router::send_cookie()with full reverse proxy and Cloudflare SSL awareness (HTTP_X_FORWARDED_SSL,HTTP_CF_VISITOR), guaranteeing correctSecureattribute propagation. - SPECULATION RULES BYPASS HARDENING: Expanded
Speculation_Rules::should_render()with comprehensive suppression checks forDONOTCACHEPAGE,woocommerce_cart_hash, native WooCommerce checkout/account templates (is_cart(),is_checkout(),is_account_page()), and password-protected posts. - SPECULATION URL PATTERNS & SELECTOR EXCLUSIONS: Enhanced speculation rules schema to explicitly exclude exact
/cart,/checkout,/my-accountpaths, archive mime types (.tar*,.gz*), and link downloads (a[download]). - SANITIZED AJAX FRAGMENTS HANDLING: Hardened
Woo_Guard::maybe_short_circuit_fragments()with query parameter sanitization (sanitize_text_field( wp_unslash( ... ) )).
1.7.2 (October 6, 2026)
- QUERY OPTIMIZATION: Eliminated redundant MySQL transient deletion on frontend cache writes (
Redis_Connector::set()), preventing database churn and maintaining 15-second key count caching exclusively for the administrative dashboard. - OUTPUT BUFFER COLLAPSE: Added nested output buffer level tracking (
$capture_buffer_level) inCache_Engine, safely collapsing unclosed third-party template and widget buffers prior to cache capture. - ERROR RECOVERY HARDENING: Extended fatal error detection in output buffer shutdown hook to intercept
E_RECOVERABLE_ERROR, guaranteeing incomplete or faulted pages are never committed to cache. - DEDICATED BLOG & AUTHOR INVALIDATION: Added surgical cache purging for static front page blog listings (
page_for_posts) and post author archives (get_author_posts_url), ensuring archives immediately reflect newly published and updated articles. - SLASHED & UNSLASHED KEY PURGE PARITY: Expanded
purge_post()andpurge_url()to invalidate both trailing-slashed and unslashed canonical Redis keys in a single atomic batchedDELcommand. - REVERSE PROXY SSL EXPANSION: Extended HTTPS scheme detection to support
HTTP_X_FORWARDED_SSLand CloudflareHTTP_CF_VISITORpayloads across write paths and URL purges. - DEACTIVATION & UNINSTALL HYGIENE: Enhanced
Lifecycle::deactivate()andLifecycle::uninstall()to automatically flush Redis cache keys and clean up all transient caches (lumencache_key_count,lumencache_nginx_confirmed,lumencache_qs_bridge_check). - REDIS SCAN BOUNDS: Added iteration bounds to
Redis_Connector::key_count()anddelete_pattern()to defend against runaway driver loops during full-keyspace cursor traversal.
1.7.1 (October 6, 2026)
- HTTP HEAD METHOD SUPPORT: Enabled early RAM cache HIT handling for HTTP HEAD requests across both advanced-cache.php drop-in and server/lumen-cache-proxy.php, serving accurate response headers in <1ms without body transfer and eliminating unnecessary WordPress bootstrap on crawler/probe checks.
- RFC 7232 CONDITIONAL GET HARDENING: Expanded If-None-Match evaluation to seamlessly support unquoted ETags, wildcard asterisk (*), and multi-tag header values, preventing accidental cache re-downloads.
- PREDIS AUTOLOADER RESOLUTION: Hardened early autoloader path resolution to respect custom WP_PLUGIN_DIR definitions before falling back to WP_CONTENT_DIR/plugins.
- HEADERS_SENT DEFENSE: Wrapped proxy header emission in defensive headers_sent() check to prevent PHP runtime notices.
1.7.0 (October 6, 2026)
- SPECULATION RULES API ENGINE: Introduced next-generation browser speculation rules (
<script type="speculationrules">) delivering sub-50ms instant page navigation via Chromium background prefetching and prerendering, fully accelerated by sub-millisecond RAM cache delivery. - CONDITIONAL GET & HTTP 304 NOT MODIFIED: Added native ETag generation and
If-None-Matchvalidation directly into early drop-in and proxy readers, terminating repeat requests withHTTP 304 Not Modifiedand 0 bytes transfer. - RFC 5861 STALE-WHILE-REVALIDATE & EDGE HEADERS: Emitted modern
Cache-Control: public, max-age=..., stale-while-revalidate=...headers for browser caches and edge CDN proxies. - WORDPRESS.ORG PLUGIN CHECK COMPLIANCE: Hardened input attribute rendering, added translator comments across all internationalized placeholders, namespaced pro compatibility surfaces, and cleared 100% of repository linter errors.
- EARLY DROP-IN PREDIS BOOTSTRAP: Resolved silent drop-in bail-out in environments without
ext-redisPHP extension. Bothadvanced-cache.phpandserver/lumen-cache-proxy.phpnow detect and load LumenCache’s bundled Predis autoloader (wp-content/plugins/lumen-cache/vendor/autoload.php) before early bail-out checks. - RAM HIT RATIO AUDIT & CERTIFICATION: Verified RAM cache hit-rate scaling from 0% past the 98% target (certified at 98.1% across 150+ requests with 0 DB queries on hits).
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best LumenCache alternatives
All cache plugins →
FAQ
LumenCache: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 10, 2026
Is LumenCache free?
Yes. LumenCache is free to download and use from the official WordPress.org plugin directory.
Is LumenCache safe to use in 2026?
LumenCache is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites and was last updated 4 days ago, and scores 66/100 on our health check.
How many websites use LumenCache?
LumenCache is active on 10+ WordPress websites and has been downloaded 472 times since it launched in August 2026. It was downloaded 274 times in the last 30 days.
Does LumenCache work with WordPress 7.1?
Yes. The developer has tested LumenCache up to WordPress 7.1.3, the latest release. It requires WordPress 6.0 or newer.
What PHP version does LumenCache need?
LumenCache requires PHP 8.1 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was LumenCache last updated?
The latest version, 1.7.5, was released on October 6, 2026 (4 days ago).
Who makes LumenCache?
LumenCache is developed and maintained by Celsius Anderson.
What are the best alternatives to LumenCache?
The most popular alternatives to LumenCache are WP Super Cache (1M+ installs), WP Fastest Cache (1M+ installs) and WP-Optimize (1M+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
