Troubleshooting

Symptom-first checks for cache, assets, CSS, images, Redis, LiteSpeed, and monitoring.

2 min readPart of Performance Optimisation

Use this page as a symptom-first checklist. Capture the URL, the exact setting or action, the response headers, and the relevant System Info output before changing several controls at once.

Pages are not cached

Check cache_settings.enableCache, the owned advanced-cache.php drop-in, WP_CACHE, cache-directory permissions, and request gates. Logged-in requests, query strings, REST/admin/feed routes, WooCommerce dynamic routes, and private cookies can intentionally bypass the cache.

wp wppo cache status
curl -sI https://example.com/ | grep -iE \'etag|last-modified|vary|x-litespeed-cache\'

Stale content after publishing

Publishing normally purges affected pages, archives, and configured edge/server layers. If an older layer remains, purge it explicitly:

wp wppo cache clear
wp wppo object-cache flush

Minification or JavaScript breaks a page

Disable the narrowest failing option, add the exact script or stylesheet handle to the relevant exclusion list, save, and clear the page cache. For delay-JS, exclude navigation, consent, payment, and builder-critical scripts before changing the idle timeout.

CSS disappears or critical CSS is stale

Use the Used CSS/Critical CSS safelist or user exclusion UI, then regenerate the affected URL. The staged preview, health check, promotion, and rollback controls are designed for this workflow. Re-test after a builder update.

WebP or AVIF is not served

wp wppo image status
wp wppo image convert

Check conversion status, format, generated files, and server rewrite/vary rules. On OpenLiteSpeed, restart LiteSpeed after changing .htaccess. Original uploads remain available when conversion is pending.

Redis is disconnected

wp wppo object-cache status
wp wppo object-cache ping

Check PhpRedis, reachability, drop-in ownership, and circuit state. Do not paste a Redis password into a ticket or screenshot.

LiteSpeed headers are absent

Check litespeed_integration.mode, active LiteSpeed Cache, and the selected rule layer. On nginx, .htaccess is not executed; use generated nginx rules. On OpenLiteSpeed, restart after rule edits.

PageSpeed or RUM data is missing

PageSpeed requires a configured key and an explicit scan. RUM requires the setting to be enabled and an unobstructed browser beacon; ad blockers and rate limits can prevent collection. Check dashboard status and wp wppo system-info.