Caching plugin · WordPress
Get more out of LiteSpeed Cache
LiteSpeed Cache is powerful but sprawling — Page Optimization alone has eight tabs. Maki detects LiteSpeed Cache and points you to the exact tab and field for each problem your PageSpeed scan finds.
What usually slows down LiteSpeed Cache sites
Page Optimization is mostly off
CSS Combine, UCSS and Load CSS Asynchronously are disabled by default. Enabling them carefully removes render-blocking CSS.
QUIC.cloud services aren't connected
Critical CSS and Unique CSS generation require QUIC.cloud. Without it, some optimizations silently do nothing.
Hero images are lazy-loaded
Add your LCP image to Media Excludes → Lazy Load Image Excludes so it loads immediately.
Step-by-step fixes
The fixes Maki most often recommends on LiteSpeed Cache sites.
Eliminate render-blocking CSS
Read the fix →TTFBReduce initial server response time (TTFB)
Read the fix →LCPYour main image is lazy-loaded (LCP penalty)
Read the fix →SpeedStatic files have a short browser cache
Read the fix →LCPCSS or JavaScript files aren't minified
Read the fix →SpeedGoogle Fonts load from Google's servers
Read the fix →LiteSpeed Cache speed FAQ
Does LiteSpeed Cache work on any host?
Page caching requires a LiteSpeed web server. The optimization features (CSS, JS, images) work on any host.
Also see: Elementor · WooCommerce · WP Rocket · Perfmatters · Divi
Scan your LiteSpeed Cache site free.
Free scan with real Google data. Exact fixes for your plugins.
