Knowledge
Breakdance on LiteSpeed hosting: LiteSpeed Cache or a plugin cache?
On a LiteSpeed host, LiteSpeed Cache is often enough for a Breakdance site, because the server cache already delivers pages very quickly. A plugin cache mainly adds something if you want the optimizations around it, such as used CSS and lazy loading. What matters is that only one place caches the pages. Below is how Spark Speed handles that and when to pick which.
In short
- Cache pages in one place: the LiteSpeed server cache or a plugin cache, not both.
- By default Spark Speed leaves the page cache to LiteSpeed Cache as soon as that plugin is active, and forwards its purges.
- The optional native mode drives the LiteSpeed server cache directly with headers and tags. It is off by default.
- For Breakdance-specific behaviour we found no documentation from LiteSpeed Cache itself. So clear manually after global changes.
Is LiteSpeed Cache enough for a Breakdance site?
Often yes. The LiteSpeed server cache is fast and the plugin has general purge rules: you can have the whole cache cleared on updates, and add extra hooks that wipe everything. The setting that keeps serving stale pages is better turned off for a Breakdance site, otherwise visitors briefly still see the old page. We found no documentation in which LiteSpeed Cache recognises Breakdance templates. If you use Breakdance, clear the cache by hand after saving a template or global style.
What does Spark Speed do next to LiteSpeed Cache?
Spark Speed detects LiteSpeed automatically. If LiteSpeed Cache is active, Spark Speed gives up its own page cache so nothing is cached twice, and forwards its purges. The optimizations of Spark Speed, such as used CSS, remain possible. Without LiteSpeed Cache the plugin writes .htaccess rules so LiteSpeed never serves the shared page to visitors with login or cart cookies.
What is the native LiteSpeed mode?
An optional mode (litespeed_native_cache, off by default) in which Spark Speed drives the LiteSpeed server cache itself with X-LiteSpeed-Cache-Control and tag headers. The same exclusions as for its own disk cache apply: cart, 404, bypass URLs and cookies. It also purges per URL with tags, adds a vary for mobile, caps filter variants and refreshes copies at 80 percent of the observed lifetime. You then have one cache, on the server, managed by Spark Speed.
How do other plugins do on LiteSpeed?
According to our review of version 3.23.3.3, WP Rocket keeps its own cache and only sends LiteSpeed purge headers on a purge. It does not drive the LiteSpeed cache itself. FlyingPress has no LiteSpeed integration and lists LiteSpeed Cache as an incompatible plugin. If you do not want a second cache next to the server one, that is a difference that matters.
When do you pick which?
Pick LiteSpeed Cache alone if you are happy with the basics and make few Breakdance changes. Pick Spark Speed next to LiteSpeed Cache if you also want used CSS and lazy loading without double caching. Pick native mode if you want one server cache managed by Spark Speed, and test it first with cart and filters. Without a LiteSpeed server, Spark Speed keeps its own page cache. If you run a Breakdance shop, keep the exclusions for cart and checkout in mind, which apply in both cases. Whichever route you choose, always check in a private window after a change to a Breakdance template.
After switching it on, check in the response headers of a visitor page that only one cache header is present, then test the cart and a filter.
Spark Speed detects LiteSpeed and chooses itself: no double cache, or native control of the server cache.
Frequently asked questions
Yes. Spark Speed then leaves the page cache to LiteSpeed Cache and forwards its purges.
No, it is off and you switch it on yourself.
It is not described in the sources we consulted. Clear the cache yourself after global changes.