FlyingPress can cache pages even for logged-in users by generating separate cache versions based on their WordPress roles.
How it works
When enabled:
Logged-in users are served from cache just like guests.
A unique cache file is created per user role.
Users with multiple roles get a combined cache key.
Examples:
/sample-page/index-logged-in-subscriber.html.gz
/sample-page/index-logged-in-editor-author.html.gz
Note: These versions are cached without frontend optimizations (minification, lazy load, etc.).
When to use it
Enable this if:
Logged-in users see similar content based on their role (e.g. WooCommerce customers, membership areas).
You want to boost performance without disabling access-based features.
Avoid this if content is highly personalized per user, such as user-specific dashboards.
Want to skip caching for certain roles?