Skip to content

Black Friday 50% off your first year on all premium plugins and the Suite.

See the deals

Logged-in users and admins

Why logged-in users and administrators never see cached pages in TurboCache, and when to cache for members with per-user cache.

1 min read · Updated 5 November 2026

Admins do not get cached pages

By default anyone with the WordPress login cookie bypasses the cache (BYPASS; reason=logged-in). So you will not see the speed-up while logged in — test speed in a private window or with PageSpeed Insights.

In Test mode the opposite applies to optimisation: only administrators see optimised pages, and visitors get untouched, uncached ones.

Caching for members

  • Logged-in users on Cache and revalidation — one shared copy for everyone logged in. Only safe if members see exactly the same markup as guests (no name in the header, no account menu).
  • Per-user cache on Exclusions and views — a private copy per user (or per session), sent with Cache-Control: private. Use this for membership sites, courses and dashboards.

Never use shared logged-in caching on a shop or membership site: one member could see another member’s details.

Builders

The Divi Visual Builder (and Elementor, Beaver Builder, Bricks, Oxygen, Brizy and WPBakery front-end editors) is never cached or optimised, so editing always shows live content. Previews and the Customizer preview are never cached either.

Did this answer the question? No — open a support request