LiteSpeed Cache or WP Rocket
Why LSCache is the better fit on WebGee's LiteSpeed servers, what WP Rocket still does well, and why you must not run both.
Both are page-cache plugins for WordPress. On WebGee hosting, LiteSpeed Cache is the better choice for most sites. Applies to all shared and reseller hosting, which runs LiteSpeed.
The difference that decides it
LSCache caches at the server. LiteSpeed Web Server holds the cached page and serves it before PHP starts. No WordPress code runs, no database is queried.
WP Rocket caches at the PHP layer. A request still starts PHP, loads WordPress far enough to reach the plugin, and is then served a cached file.
That gap is small on a quiet site and significant under load, because server-level caching also means fewer PHP processes in use — which matters on shared hosting, where PHP processes are the resource you run out of first.
What else LSCache gives you here
- ESI (Edge Side Includes) — cache a page while leaving parts of it dynamic, such as a cart total or a "logged in as" greeting. Without it, any page containing personalised content cannot be cached at all.
- Tag-based purging — when you edit a post, only the pages affected are purged rather than the whole cache.
- cPanel integration — enable, disable and flag installations from LiteSpeed Web Cache Manager without logging into WordPress.
- QUIC.cloud integration — see QUIC.cloud or Cloudflare.
- No licence cost. LSCache is free and open source; WP Rocket is a paid annual subscription.
Where WP Rocket still makes sense
It is a well-built plugin with a deliberately smaller set of options, and some people prefer that — LSCache exposes a great deal of configuration, which is useful when you need it and confusing when you do not.
It is also server-agnostic. If you manage sites across several hosts and want one plugin configured the same way everywhere, that consistency has real value, and you would be trading some performance on LiteSpeed for it.
Do not run both
Two page caches will conflict. The usual result is not "twice as fast" but
stale pages, a cache that will not clear, and hours lost working out which
layer is serving the old content. Uninstall one before installing the other —
deactivating is not enough, because both write configuration into
.htaccess and wp-config.php.
If you are switching, remove WP Rocket first, confirm the site still loads, then install LSCache.
Related
Use SVG images in WordPress
WordPress blocks SVG uploads by default for good reason. How to enable them safely with Safe SVG, and why not to use a plugin that simply allows the type.
Fix "Unable to create directory"
WordPress cannot write to the uploads folder. How to correct file permissions, check the upload path, and rule out a full disk.