Troubleshooting · Troubleshooting
How to Fix LiteSpeed Cache Breaking the Site
Short answer
To fix LiteSpeed Cache breaking your site, first purge all cache, then turn off the CSS and JS optimization settings and check the site again. If the site looks right, turn those settings back on one at a time, purge after each change, and exclude the single file that breaks the layout. If the site still looks wrong with optimization off, turn on Disable All Features to test whether LiteSpeed Cache is the cause at all.
Key takeaways
- Add ?LSCWP_CTRL=before_optm to a page URL to view it with no LiteSpeed optimization applied.
- Turning off all CSS and JS optimization and purging the cache is the fastest way to confirm an optimization clash.
- Purge All does not clear Critical CSS, Unique CSS, or Low-Quality Image Placeholders, so purge those separately when needed.
- LiteSpeed Cache needs WordPress 6.0 or higher and PHP 7.4 or higher, as of November 2026.
- Re-enable settings one at a time and exclude only the file that breaks the page, instead of leaving every optimization off.
What does LiteSpeed Cache breaking the site mean?
LiteSpeed Cache breaks a site when one of its optimization or cache settings changes how a page looks or works.
The page may lose its styling, show a plain layout, hide a menu, stop a slider, or fail at checkout. LiteSpeed Cache for WordPress is a free site acceleration plugin with a server-level cache and a set of optimization features, according to WordPress.org.
A cache problem shows old content, while an optimization problem changes the CSS or JavaScript the browser receives. Start by naming the symptom you see.
| Symptom | Likely cause | First fix |
|---|---|---|
| Plain, unstyled page | CSS minify, combine, or async load | Turn off CSS optimization, then purge |
| Menu, slider, or button does not work | JS combine, defer, or delay | Turn off JS optimization, then purge |
| Old content after an edit | Stale page cache | Purge All, then reload in a private window |
| Wrong cart, price, or account data | Cached dynamic page | Turn off Guest Mode and check cache rules |
| White screen or no page at all | A clash or a server error | Disable All Features, then check the debug log |
How do you tell if LiteSpeed Cache caused the break?
Open the broken page in a private window with ?LSCWP_CTRL=before_optm added to the URL to see it with no optimization applied.
LiteSpeed documents this exact check in its CSS/JS troubleshooting guide. If the page looks right with that address, the fault sits in the optimization settings. If it still looks wrong, the fault is not in those settings.
Try ?LSCWP_CTRL=NOCACHE too. That address makes the server build the page fresh instead of serving a cached copy, as shown in the Toolbox guide.
If the page looks right with no cache and no optimization, LiteSpeed Cache is involved. If it still looks wrong after you deactivate the plugin, look at the theme, another plugin, or the host instead.
What should you do first when the site breaks?
Purge all cache first, then turn off CSS and JS optimization and purge again.
Go to LiteSpeed Cache > Toolbox > Purge and press Purge All. That button clears the cache entries for the current WordPress install, according to the Toolbox guide. It does not clear Critical CSS, Unique CSS, or Low-Quality Image Placeholders, so use the separate buttons for those.
Next, go to LiteSpeed Cache > Page Optimization. The LiteSpeed Cache settings guide lists what each of these settings does. Set every CSS option to OFF on the CSS Settings tab, and every JS option to OFF on the JS Settings tab, as LiteSpeed shows in its CSS/JS troubleshooting guide.
Purge All again after you change the settings, then reload the broken page in a private window. If it looks right now, you have a CSS or JavaScript clash. If it still looks wrong, use Disable All Features next.
How do you use Disable All Features to test the site?
Turn on Disable All Features in LiteSpeed Cache > Toolbox > Debug Settings to switch off every LiteSpeed Cache feature at once.
LiteSpeed says to turn this option on when you need to debug a site without any caching or optimization getting in the way, in the Toolbox guide. Turn it back off when you finish, or the site will stay uncached and unoptimized.
The same screen offers Disable All Features for 24 Hours. That choice acts the same way, then returns the site to normal operation after 24 hours, according to the same Toolbox guide. Use it when you want a safe time limit on the test.
If you cannot reach the dashboard, set LITESPEED_DISABLE_ALL to true in wp-config.php to disable all plugin features, as listed in the LiteSpeed constants guide.
If the site works with all features off, LiteSpeed Cache is part of the problem. If it still fails, the cause sits elsewhere, and you should check the theme, the other plugins, and the host. LiteSpeed states this test plainly in its troubleshooting guide.
How do you fix a broken layout after turning on CSS or JS optimization?
Turn off all CSS and JS optimization, purge, confirm the page looks right, then turn the settings back on one at a time.
CSS Minify strips extra white space, line breaks, and comments from CSS files, while CSS Combine joins them into a single file, according to the Page Optimization guide. JS Minify and JS Combine do the same for JavaScript. Combine can break scripts that depend on file order.
Work in this order:
- Set CSS Minify to ON, purge, and check the page.
- Set JS Minify to ON, purge, and check the page.
- Set CSS Combine to ON, purge, and check the page.
- Set JS Combine to ON, purge, and check the page.
- Set Load JS Deferred to Deferred, purge, and check the page.
Load JS Deferred holds JavaScript until the HTML has finished loading, while Delayed waits for user activity such as a mouse move or key press, according to the same Page Optimization guide.
Try Deferred first, and try Delayed only after Deferred works. Purge All after every single change, because an old cached copy can hide the result.
How do you find the exact CSS or JS file that breaks the site?
List the page files in the browser Network tab, exclude them all, then remove them from the exclude list one at a time until the page breaks again.
First, decide whether the fault is CSS or JavaScript. Turn the JS options on and the CSS options off, purge, and view the page.
If it looks wrong, a JS file is at fault. If it looks right, swap the two groups and check again. LiteSpeed lays out this split in its CSS/JS troubleshooting guide.
Next, get the file list. Open the page with ?LSCWP_CTRL=before_optm added to the URL, open the browser developer tools, go to the Network tab, click CSS or JS, and reload. The Network Monitor shows the network requests made when a page loads, as Mozilla documents.
Then exclude the whole list. Go to LiteSpeed Cache > Page Optimization > Tuning - CSS and paste the CSS files one per line in the CSS Excludes box, or use the Tuning tab for JS files. Purge and check the site.
Remove one file from the exclude list, purge, and check the page. If the page still looks right, that file was not the fault.
If the page breaks, you found the bad file, so put it back in the exclude list and leave it there. Repeat the step for each file left on the list.
Why is the site still showing old content after a fix?
The site shows old content because a cached copy is still being served, so purge the cache and test in a private window.
A page cache stores a generated page as a static HTML snapshot, so the next visitor gets the snapshot instead of a fresh page, as LiteSpeed explains. A fix will not show until the old snapshot is cleared.
Purge All clears the cache for the current WordPress install, but it does not clear Critical CSS, Unique CSS, or LQIP, as the Toolbox guide states. If you changed CSS, purge the CSS/JS cache too. If you use a CDN, purge that cache as well, because the CDN can hold its own old copy.
The default public cache TTL is 604800 seconds, which is 7 days, according to HostArmada. A long TTL makes a missed purge last longer. For more on stale pages, read the guide on changes not showing on the live site.
Why do menus, sliders, carts, or forms stop working?
Menus, sliders, carts, and forms stop working when a JavaScript file is combined, deferred, or delayed in the wrong order.
A slider script may run before its library loads, a menu script may wait for a mouse move that never comes, or a cart script may read a cached page instead of fresh data.
Start with Load JS Deferred. Set it to OFF, purge, and check the page. If the feature works again, the defer or delay setting is the cause.
Next, check JS Combine. Turn it off, purge, and check again. If the feature works, one of the combined files conflicts with another.
Use the exclude method in the last section to find it. Leave JS Combine External and Inline off on the first pass, because it pulls inline and third-party scripts into the same bundle.
For a shop, check Guest Mode too. It serves a default cached page for a first visit, with no cache varies considered, according to the General settings guide.
That page can show the wrong price or language for a moment. Turn Guest Mode off, purge, and check again.
How do you fix a white screen or a site that will not load at all?
Turn on Disable All Features, update the plugin, and check the debug log before you change any other setting.
A white screen often means a fatal PHP error, not a layout clash. LiteSpeed Cache version 7.9.3 was released on 3 November 2026, as shown in the changelog on the WordPress.org plugin page. Update to the current release shown there first.
Check the requirements next. LiteSpeed Cache needs WordPress 6.0 or higher and PHP 7.4 or higher, according to the LiteSpeed overview. The page cache needs LiteSpeed Web Server Enterprise with the LSCache module (v5.0.10 or later), OpenLiteSpeed (v1.4.17 or later), LiteSpeed WebADC (v2.0 or later), or QUIC.cloud, as listed on the WordPress.org plugin page.
If the dashboard will not load, add define( 'LITESPEED_DISABLE_ALL', true ); to wp-config.php. That constant disables all plugin features, as listed in the LiteSpeed constants guide. Remove it after the site loads, or the plugin will stay off.
Turn on the WordPress debug log to find the error. Add WP_DEBUG and WP_DEBUG_LOG set to true in wp-config.php, and WordPress will log errors to wp-content/debug.log, as WordPress Developer Resources explains. The LiteSpeed debug log size limit runs from 3 MB to 3000 MB, according to the Toolbox guide.
How do you check that the fix worked?
Reload the fixed page in a private window, click every broken feature, and check the same page on a phone screen.
Reload the fixed page in a private window, then reload it once more after a minute. Click the menu, the slider, the form button, and the cart.
Check the browser Console tab for errors. Open the developer tools, click Console, and reload the page. A red error that names a file tells you which script still fails.
In the Network tab, click the main page request and look for the X-LiteSpeed-Cache header. A hit means the page came from cache, while a miss means it was built fresh, as LiteSpeed notes in its CSS/JS troubleshooting guide.
Repeat the check on a second page type, such as a post and the home page. If both work and the Console shows no errors, the fix holds. For CSS-only faults, the guide on CSS changes not showing covers the next checks.
When should you contact your host?
Contact your host when the site still fails with Disable All Features on, or when you cannot reach the dashboard at all.
Your host controls the server cache, the cache root, and the LiteSpeed server itself. LiteSpeed notes that a site owner without server admin access should ask the hosting provider to set up the cache root, in its overview guide.
Send the host the page URL, the exact symptom, and the results of the ?LSCWP_CTRL=before_optm check and the Disable All Features check. Ask whether the site runs on a LiteSpeed server, whether the LSCache module is on, and whether a second cache or CDN is caching the same pages.
If you need a QUIC.cloud setup check, read the guide on setting up LiteSpeed Cache with QUIC.cloud.
What mistakes should you avoid?
Do not turn on every optimization at once, do not skip the purge after each change, and do not leave Disable All Features on.
Turning on CSS Minify, CSS Combine, JS Minify, JS Combine, and Load JS Delayed in one go hides which setting broke the page. Turn them on one at a time and purge after each one, as the CSS/JS troubleshooting guide shows.
Do not forget the purge. LiteSpeed warns to purge all after changing Page Optimization settings, in the Page Optimization guide. A stale cached copy can make a good fix look broken, or a bad setting look fine.
Do not run two cache plugins, and do not run LiteSpeed Cache with another page cache such as Cloudflare APO. If you are unsure whether you need a cache plugin on your host at all, read the guide on whether a cache plugin helps on LiteSpeed hosting.
Do not leave Disable All Features on after the test, and do not leave the debug log on for days. The debug log can fill disk space fast, so turn it off when you finish, as the Toolbox guide warns. Export your settings before a reset, because a reset is permanent.
Frequently asked questions
Can LiteSpeed Cache break a WordPress site on its own?
Yes, it can change how a page looks or works when a CSS or JavaScript optimization clashes with a theme or plugin file. The page cache itself usually shows old content instead of breaking a layout. Use the before_optm check to tell the two apart, then turn off the optimization settings and purge to confirm the cause.
Should I deactivate LiteSpeed Cache to fix a broken site?
Deactivate it only as a test, not as the first fix. First purge all cache and turn off the CSS and JS optimization settings. If the site works then, you can keep the cache and exclude the one bad file. If it still fails with the plugin off, the cause is in the theme, another plugin, or the server.
Why does my site look fine when I am logged in but broken for visitors?
Logged-in users often see a fresh, uncached page, while visitors see a cached page or the Guest Mode default page. Guest Mode serves a default cached page for a first visit, so it can show the wrong content for a moment. Test in a private window, purge the cache, and check Guest Mode if the fault only affects visitors.
How long should I wait after purging LiteSpeed Cache?
Purge All takes effect at once for the pages it clears, so reload the page right away in a private window. If the page still looks old, purge the CSS and JS cache too, and purge any CDN cache in front of the site. A second reload after a minute confirms that the new cached copy is the one visitors see.
Is it safe to leave CSS and JS optimization off for good?
Yes, it is safe. LiteSpeed states that a site can still gain a lot from caching even without optimization turned on. You lose some file-size and load-time gains, but the page cache still works. Turn the settings back on one at a time later if you want the extra speed.
What do I do if the site breaks right after a LiteSpeed Cache update?
Purge all cache first, including the CSS and JS cache, then check the site in a private window. If it still breaks, turn off the CSS and JS optimization settings and purge again. Check that you run the current plugin release, and use Disable All Features to confirm whether the update caused the fault before you roll back or contact support.
Sources
- CSS/JS Issues | Troubleshooting | LSCache for WordPress LiteSpeed Documentation
- Toolbox | Screen-by-Screen | LSCache for WordPress LiteSpeed Documentation
- Troubleshooting Guide | LSCache for WordPress LiteSpeed Documentation
- Page Optimization | Screen-by-Screen | LSCache for WordPress LiteSpeed Documentation
- LiteSpeed Cache for WordPress LiteSpeed Documentation
- LiteSpeed Cache – WordPress plugin WordPress.org
- Debugging in WordPress WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
