Full-page cache makes anonymous WordPress pages feel instant. The same cache, aimed at a cart, checkout, or account URL, can freeze the wrong person into someone else’s basket, hide a coupon state, or show a logged-out shell to a logged-in customer. Commerce pages are dynamic on purpose. They should not be treated like a brochure homepage snapshot.
Lightify’s full-page cache ships with gzip, background warming, purges on publish and edit, mobile-aware separate variants, and automatic exclusions for cart, checkout, and account pages. You get speed where HTML can be shared safely, and dynamic rendering where personalization matters. This post stays on those commerce and account exclusions inside the full-page cache story.
Lightify is the DaftPlug performance plugin. This post is only about keeping cart, checkout, and account out of the page cache while still using Lightify’s full-page cache path. Not unused CSS removal, not delay JavaScript, not lazy load as a deep dive, not WebP conversion, not YouTube placeholders, not speculative loading, not a Core Web Vitals dashboard essay, not database cleanup, not self-hosting third-party assets, not font preload, not a minify essay. Those live elsewhere. For the device-aware cache variant that pairs with this foundation, keep WordPress mobile-aware page cache device variant nearby.
What Lightify actually ships here
Stay inside the real feature set:
- Full-page cache with gzip so cached HTML is stored and served compressed where that path applies
- Cache warmed in the background so popular anonymous URLs can be ready before the next cold visitor
- Purges on publish and edit so new content does not sit behind yesterday’s HTML forever
- Cart, checkout, and account pages excluded so personalized commerce and account views are not frozen for the wrong person
- Mobile-aware behavior with a separate variant per device so phone and desktop do not steal each other’s cached HTML on the URLs that are eligible to cache
This post does not invent undocumented per-plugin exclusion UIs for every membership endpoint, custom reverse-proxy essays Lightify does not publish as a networking whitepaper, or promises that a host-level page cache will automatically mirror Lightify’s cart, checkout, and account exclusions. The product promise is Lightify full-page cache with gzip, background warm, publish/edit purges, cart/checkout/account exclusions, and mobile-aware variants. Stay there. Unused CSS, delay JS, lazy load, WebP, YouTube placeholders, speculative loading, CWV dashboards, database cleanup, self-host assets, font preload, and minify projects are parallel tools, not this article’s job.
Why excluding cart, checkout, and account matters
Cart HTML is personal. Item counts, line prices, and notices belong to a session. Serving a cached cart page to the next shopper is a trust failure, not a performance win.
Checkout must stay dynamic. Payment fragments, address fields, and conditional shipping change with the shopper. A full-page cache hit that freezes checkout is how stores earn angry tickets and abandoned orders.
Account pages are identity-bound. Order history, downloads, and profile fields are never brochure content. Caching them as anonymous HTML is unsafe even when it “looks fine” in a quick desktop glance.
Anonymous catalog and content pages still deserve cache. Exclusions are not an argument against full-page cache. They are how full-page cache stays honest. Lightify speeds the shareable URLs and leaves the dynamic commerce paths alone.
Gzip, warm, and purge still matter on the URLs you do cache. Excluding cart does not replace background warming for the homepage, or publish purges for the blog, or mobile-aware variants for the shop archive. The stack works together. This article focuses on the exclusion slice.
Host caches can reintroduce the footgun. If a server-level cache sits in front of WordPress and ignores commerce cookies, you can still serve wrong HTML even when Lightify excludes correctly on the WordPress side. Treat that as an ops checklist item, not as a reason to skip Lightify’s exclusions.
How to enable and verify safe cache exclusions in wp-admin
Assume Lightify is installed and you can test as a shopper on a staging or low-risk catalog. Start with anonymous pages, then prove cart, checkout, and account stay dynamic.
1. Map which URLs must never be brochure-cached
At minimum: cart, checkout, and account (WooCommerce defaults and your real permalinks). Mentally add any custom “my account” style endpoints you rely on for membership. You are planning verification, not inventing undocumented Lightify exclusion rows for every plugin.
2. Enable Lightify full-page cache with the shipped exclusions
In wp-admin, open Lightify. Enable the full-page cache path. Confirm cart, checkout, and account exclusions are active as Lightify ships them. Confirm gzip and background warming match what you intend. Confirm mobile-aware separate variants are on if you care about device-specific HTML (see the related post). Keep the first pass boring: page cache on, exclusions respected, leave unused CSS, delay JS, lazy-load projects, WebP migrations, YouTube placeholders, speculative loading, CWV dashboard tinkering, database cleanup, self-host asset projects, font preload experiments, and minify sweeps for later.
3. Confirm anonymous pages still cache
Load a public homepage or category URL twice as a logged-out visitor. You should feel the cache-fast second hit relative to a forced cold path, without claiming lab numbers Lightify does not publish for your host. Publish a small edit on a test page and confirm the front end updates after Lightify’s publish/edit purge path runs. Exclusions are useless if you never proved the cache works on safe URLs.
4. Smoke-test cart, checkout, and account as dynamic
- As shopper A, add a distinctive product to the cart. Note the cart contents.
- In a separate clean browser (or private window) as shopper B, open the cart URL. You must not see shopper A’s distinctive cart.
- Proceed toward checkout as shopper A. Confirm fields and totals match that session, not a frozen snapshot from another user.
- Log into an account view. Confirm order history or profile data matches the logged-in user.
- Repeat once on a phone-sized viewport if you use mobile-aware variants, still expecting cart, checkout, and account to stay personal.
- If a host or CDN page cache sits in front, repeat the two-shopper cart test through that edge. Wrong HTML at the edge is an ops conflict, not a reason to disable Lightify’s WordPress-side exclusions without investigation.
5. Keep media and script work as separate wins
Cached HTML that still downloads a huge hero is only half a win. Lazy-load, delay JS, and image format work still matter on catalog pages. Do them as later passes so you can tell which change moved LCP versus which change protected checkout correctness.
6. Document the enablement for the next teammate
Write one line in your internal runbook: “Lightify full-page cache on [date]. Cart, checkout, and account excluded. Mobile-aware variants [on/off]. Re-test two-shopper cart after CDN changes and after WooCommerce template updates.” Cache bugs show up as “my cart is empty” and “I see someone else’s items” long before they show up as a TTFB chart.
Who this is for
WooCommerce stores that want anonymous catalog speed without gambling on cart HTML.
Membership shops that combine products with account dashboards and cannot cache identity pages.
Agencies who have inherited sites where a blunt “cache everything” plugin once leaked cart state.
Performance-minded site owners who already know full-page cache is the big TTFB lever and want the safe defaults spelled out.
Anyone who has purged the entire cache during a flash sale because checkout “felt stuck.”
This is less urgent for pure brochure sites with no cart, checkout, or account. Even then, if you later add WooCommerce, the exclusion story becomes mandatory on day one of commerce.
What good looks like
- Full-page cache is enabled with gzip where that path applies.
- Popular anonymous URLs can be warmed in the background.
- Publish and edit purge stale HTML on content you care about.
- Cart, checkout, and account stay excluded and behave as personal, dynamic views.
- Mobile-aware separate variants remain available for eligible cached URLs.
- Two shoppers never see each other’s cart through a cache hit.
- Unused CSS, delay JS, lazy load, WebP, YouTube placeholders, speculative loading, CWV dashboards, database cleanup, self-host assets, font preload, and minify essays were not required for this win.
- You did not invent host CDN rules as if they were Lightify settings, and you did not claim every membership plugin URL is auto-listed beyond cart, checkout, and account.
If cart ever looks shared across users, stop selling the cache win and debug exclusions plus any host-level cache immediately. Correctness beats a green TTFB screenshot.
Pitfalls (the ones that bite)
Caching cart “just for guests.” Guest carts are still personal sessions. Excluding cart is the safe default Lightify ships.
Testing only while logged into wp-admin. Admin bars and bypass rules hide the shopper reality. Use clean shopper browsers.
Assuming the CDN matches WordPress exclusions. Edge caches that ignore cookies recreate the footgun. Verify through the public hostname.
Turning off all page cache because checkout felt weird once. Fix exclusions and edge rules. Do not throw away anonymous catalog speed.
Skipping publish purge checks. Editors will blame WooCommerce for stale product copy when the cache never cleared.
Bundling every Lightify performance toggle into the same change window. If exclusions, speculative loading, and unused CSS all land together, attribution dies. Ship cache plus exclusions first.
Forgetting mobile-aware variants on catalog pages. Excluding cart does not fix phone HTML served to desktops on the shop archive. See the related mobile-aware post.
Custom account URLs never verified. Lightify excludes account for you on the WooCommerce account path. If you invented a different members URL, verify it with the same two-user caution.
Practical checklist before you call it done
- Enable Lightify full-page cache with gzip as you intend.
- Confirm cart, checkout, and account exclusions are active as shipped.
- Confirm background warm and publish/edit purge behavior on a safe test URL.
- Confirm mobile-aware variants if device-specific HTML matters on catalog pages.
- Prove an anonymous marketing or archive URL benefits from cache.
- Run the two-shopper cart test in clean browsers.
- Walk checkout far enough to trust totals and fields are session-correct.
- Open account as a real user and confirm identity-bound data.
- If a CDN or host cache exists, repeat the cart test through that edge.
- Leave unused CSS, delay JS, lazy load, WebP, YouTube placeholders, speculative loading, CWV dashboard, database cleanup, self-host assets, font preload, and minify deep dives for separate passes.
- Write the exclusion and re-test notes in the team runbook.
- Re-test after WooCommerce major updates and after CDN rule changes.
Takeaway
Full-page cache is how anonymous WordPress pages get fast. Cart, checkout, and account are how stores stay correct. Lightify’s full-page cache gives you gzip, background warming, publish and edit purges, and mobile-aware variants, while excluding cart, checkout, and account so dynamic commerce is not frozen for the wrong person.
Lightify puts that balance in wp-admin so you are not maintaining a fragile hand-written exclusion list as your only safety net. Enable the cache. Prove anonymous URLs are fast. Prove cart and checkout stay personal. Keep sibling performance features as separate enablement work.
One Pro membership unlocks Lightify plus Progressify, Generatify, Rankify, and Snapshotify. New Pro plugins join existing memberships. Plans differ by site count only (Pro $37.99 for 1 site, Pro Plus $74.99 for 5, Pro Max $138.99 for 100), with a 14-day money-back guarantee. See pricing when page cache should accelerate catalogs without gambling on checkout HTML.
Turn on full-page cache. Keep cart, checkout, and account out of it. When two shoppers never share a basket through a cache hit, performance finally respects commerce.