WooCommerce breaks standard WordPress caching. The cart, checkout, and My Account pages contain user-specific data that standard page caching cannot serve correctly — cache those pages and every visitor sees the same cart, which is obviously wrong. The typical solution on standard hosts is to exclude those pages from caching entirely, leaving them to run through PHP and the database on every load.
WP Engine’s EverCache system handles WooCommerce differently. It includes a WooCommerce-specific caching layer that understands what can be cached, what cannot, and how to serve cached content correctly to anonymous visitors while preserving dynamic behaviour for logged-in shoppers and active cart sessions.
What EverCache Caches on a WooCommerce Store
| Page type | EverCache behaviour | Why |
| Product pages | Cached for anonymous visitors | Content is the same for all visitors |
| Category pages | Cached for anonymous visitors | Static product listings |
| Homepage and blog | Cached for anonymous visitors | No dynamic user content |
| Cart page | Bypasses cache | Cart contents are user-specific |
| Checkout page | Bypasses cache | Must process live order data |
| My Account pages | Bypasses cache | Contains user-specific account data |
| Logged-in customers | Bypasses cache | Personalised experience required |
How EverCache Handles the Cart Fragment Problem
WooCommerce uses AJAX cart fragments to update the cart icon in the header dynamically when a visitor adds a product. On standard hosts, the cart fragment request fires on every page load for every visitor, even those who have never added anything to their cart. This generates significant uncached server load.
EverCache manages cart fragment requests intelligently, serving cached responses where cart state is empty and only triggering live requests when the visitor has an active cart session. For stores with high anonymous traffic, this alone can reduce server load substantially compared to a standard WooCommerce caching setup.
EverCache and WooCommerce Sessions
WooCommerce creates a session for every visitor who lands on your store, even anonymous ones who never add anything to their cart. On a busy store, abandoned sessions accumulate in the database over time. Standard hosting handles this poorly because each session represents a database record that adds to query load.
WP Engine’s infrastructure manages session storage and cleanup as part of the platform, keeping the session table from becoming a performance bottleneck. Combined with Redis object caching (available as an add-on), the database load from active WooCommerce sessions is significantly reduced compared to a standard hosting environment. For more on WooCommerce database management, see WordPress Database Optimization.
Do You Need a Separate Caching Plugin with EverCache?
No. WP Engine explicitly advises against installing a third-party caching plugin alongside EverCache. Plugins like WP Rocket, W3 Total Cache, and LiteSpeed Cache conflict with EverCache and can cause incorrect caching behaviour, including serving cached cart or checkout pages to visitors with active sessions.
EverCache handles page caching, browser cache headers, and CDN integration through Cloudflare automatically. The only caching add-on that works correctly alongside EverCache on WP Engine is Redis object caching, which operates at a different layer and does not conflict. For a full explanation of how caching layers interact, see WordPress Caching Explained.
Performance Impact: What EverCache Means in Practice
For a WooCommerce store, the practical performance difference between EverCache and a standard caching plugin on shared hosting shows up most clearly in three situations. Product page load times for anonymous visitors are fast because EverCache serves cached HTML without touching PHP or the database. Checkout reliability under traffic spikes is maintained because WP Engine’s infrastructure handles increased server load without degrading uncached request handling. And cart fragment requests are managed at the server level rather than generating unnecessary database calls per visitor.
For a WooCommerce store doing any meaningful volume, these differences translate to better conversion rates and fewer support tickets about slow or broken checkout experiences. See also: How to Speed Up a WooCommerce Store and WooCommerce Checkout Optimization.
Frequently Asked Questions
Why does my WooCommerce cart show the wrong contents on WP Engine?
If cart contents appear incorrect, the most common cause is a conflicting caching plugin running alongside EverCache. Remove any third-party caching plugins and flush the EverCache cache from the WP Engine dashboard. If the problem persists, check that your cart and checkout page URLs are set correctly in WooCommerce settings so EverCache can identify and exclude them from caching.
Does EverCache work with custom WooCommerce page setups?
EverCache identifies WooCommerce cart and checkout pages based on WooCommerce’s page settings. If you have set up custom checkout pages at non-standard URLs, you may need to contact WP Engine support to ensure those URLs are correctly excluded from caching.
Is EverCache the same as WP Engine's standard page cache?
EverCache is WP Engine’s server-level page caching system that applies to all sites on the platform. The WooCommerce-specific layer within EverCache adds the logic to handle cart pages, checkout pages, and session detection correctly. Standard page caching applies to all other WordPress sites on WP Engine; the WooCommerce layer activates automatically when WooCommerce is detected.
