How To Speed Up WordPress & WooCommerce For Logged-In Users

By default, anyone logged in to WordPress skips the page cache. That covers admins and editors, but also your customers and members. Their pages are built fresh on every click, so they can load 2 to 5 times slower than a cached page, with a very high time to first byte.

On WooCommerce and membership sites that’s a real problem, because logged-in users are usually your most valuable visitors. Their experience also counts towards your Core Web Vitals, so fixing it helps customers, conversions and SEO.

How to Fix Slow Logged-In Sessions

1. Turn on logged-in caching in your caching plugin

Popular caching plugins such as WP Rocket and FlyingPress, the two we use and recommend, have a setting to cache pages for logged-in users. It’s normally off by default. If your caching is handled at the server level, ask your host’s support team whether it can be enabled. Our guide to WooCommerce caching plugins covers the settings to avoid.

2. Use preloading and speculative loading

Enabling logged-in caching still leaves a gap: the page may not be in the cache yet when a user asks for it. Just in time preloading and the speculative loading feature in WordPress 6.8 close that gap by loading pages in the background before the user clicks, which pushes the server to cache them in advance.

You can read more about speculative loading. We usually recommend the Prefetch plus Eager settings. For just in time preloading, use the Flying Pages plugin.

3. Optimise your database

Uncached pages lean hard on the database, so a slow one becomes the bottleneck. The key steps are:

• Use object caching so the results of common queries are kept in memory. On WP Alpha, set up Redis object caching.
• Convert tables to InnoDB, the more efficient database storage engine.
• Enable High-Performance Order Storage (HPOS) on WooCommerce stores to speed up order handling.

There’s more detail in our WooCommerce database guide.

4. Tune PHP for performance

WordPress runs on PHP, so a well tuned PHP setup gets more out of your hosting and makes uncached pages load faster.

• Run the newest PHP version your site supports. Here’s how to change PHP versions on WP Alpha.
• Fix PHP errors. Use the Query Monitor plugin to find them.
• Adjust your opcode cache settings. See optimising PHP performance with opcode caching.

These are the opcode cache settings we recommend:

opcache.huge_code_pages=1
opcache.interned_strings_buffer=64
opcache.max_accelerated_files=10000
opcache.max_wasted_percentage=5
opcache.memory_consumption=1024
opcache.revalidate_path=0
opcache.validate_timestamps=1
opcache.revalidate_freq=10
opcache.enable_cli=1
opcache.use_cwd=1

5. Put Cloudflare in front of your site

A CDN moves work off your hosting. We use and recommend Cloudflare. Its APO service, available for $5 a month or included on the $25 a month plan, can shift more than 80% of the workload off your server and speeds the site up for every type of visitor.

6. Switch to a server cron job

WordPress runs its scheduled background tasks through wp-cron, which normally fires every 5 or 10 page loads and makes those page loads crawl. A server cron job runs wp-cron.php on a fixed schedule instead, usually every 30 minutes, so it never runs while a user is waiting for a page. Here’s how to set up a server based cron job and configure the WordPress cron.

7. Cover the basics

Standard optimisation still applies: keep pages small, optimise images and keep JavaScript under control. If you aren’t passing Core Web Vitals yet, working towards them helps logged-in and logged-out users alike.

8. Audit your plugins and scripts

Switch off plugins you no longer use and remove third party scripts that are no longer needed. We regularly find sites carrying half a dozen idle plugins and old marketing scripts that slow every page down.

9. Check your menu links

Make sure menus and internal links point to the exact final URL: https, the right choice of www or no www, and a trailing slash. Links that are slightly off send users through a redirect every time, which can add seconds to their session.

10. Fix 404 errors

404s hurt speed and SEO, especially sitewide ones caused by a typo in your template, footer or sidebar. A basic SEO audit tool will find them.

11. Use HTTP/2 or HTTP/3, and enable HSTS

HTTP/2 is 50 to 100% faster than the older HTTP/1.1, and HTTP/3 adds roughly another 10%. At a minimum you want HTTP/2, and you can check HTTP/2 support with this free tool.

HSTS is a security header that tells browsers to always use HTTPS. That cuts redirects, reduces canonical issues for SEO and lowers latency, since browsers only use HTTP/2 and HTTP/3 over HTTPS. Here’s how to enable HSTS.

12. Watch query strings on paid and email traffic

Custom query strings on ad and email links often skip caching and optimisation entirely. The usual fix is to set your caching plugin to ignore the query strings you use.

What Doesn’t Work

You’ll find plenty of advice online for speeding up logged-in users that does nothing. Skip these:

• Raising the PHP memory limit. It only matters if PHP is running out of memory and throwing errors.
• Minifying CSS or JS. It can actually slow the site by hurting how those files are cached. Gzip and Brotli compression on the server shrink files far more effectively.
• Changing the WordPress heartbeat.

Switch Off Query Monitor When You’re Done

Query Monitor is excellent for debugging, but disable it once you’ve finished. Left active, it can switch off caching for logged-in users and undo the work above.