Question: As soon as customers log into my WooCommerce shop or access their account ('My Account'), the page becomes extremely slow. My caching plugin understandably deactivates itself for logged-in users. How do I optimize performance specifically for these sessions when normal caching isn't possible?

Answer:

Your caching plugin is behaving correctly - and that is exactly the problem.

Logged-in users receive personalized content: their order history, their saved addresses, their account status, their active session. Serving a cached page to a logged-in user would mean serving someone else's data, which is why every serious caching solution excludes authenticated sessions by default. That exclusion is not a configuration error. It is a necessary architectural boundary.

But the consequence is significant: every logged-in customer accessing My Account triggers a full WordPress bootstrap on every single request. No cache intercepts it. No CDN absorbs it. The request lands directly on your server, and WordPress executes in full - including every active plugin in your installation, regardless of whether those plugins have any relevance to account management whatsoever.

Your slider plugin loads. Your SEO plugin loads. Your contact form loads. Your cookie banner logic runs. Your homepage widgets initialize. None of this serves the logged-in customer viewing their order history. All of it consumes server resources on every authenticated request.

This is the structural reality that caching cannot address - not because caching is insufficient, but because caching was never designed to solve execution overhead. It was designed to avoid repeated execution for identical requests. Logged-in sessions, by definition, are never identical enough to cache safely.

The only meaningful lever available here is reducing what executes per request - ensuring that authenticated sessions in My Account load only the plugins that account functionality genuinely requires, and nothing beyond that.

This is precisely the scenario LiteCache Rush was built to handle. Rush operates before the WordPress bootstrap and constructs a minimal, context-specific plugin set for each incoming request. For a logged-in customer accessing My Account, Rush loads WooCommerce, the session handler, and the plugins that account pages actually depend on. Everything else is prevented from executing entirely - not dequeued from the output, but never handed to WordPress in the first place.

The result is that authenticated sessions, which caching cannot help, become structurally lighter at the execution level. The server does less work per request not because anything was cached, but because unnecessary work was prevented before it started.

Where caching ends, prevention begins. For logged-in WooCommerce customers, that boundary is exactly where your performance problem lives.