Wordpress LScache Plugin: Serving stale pages for WP
Last Updated on: Wed, 15 Apr 2026 00:00:02 First I tried to achieve this for OpenCart. No success according to response time. But even if I enable the setting in the WP plugin, it doesnt make a difference either. Is there any confirmation that should be visible in the header? Something like: x-litespeed-cache: stale Maybe the problem is at the server level, not the plugin. This topic was modified 1 year, 5 months ago by Germont. Hi, Please be more specific about your issue and provide more information for verification and troubleshooting. Thank you. I purge an article and there is no stale page served at first visit, header has a x-litespeed-cache: miss value. The stale setting is ON. Next visits have obvious lower TTFB, and value is changed to hit. Is there a specific method to confirm that stale pages are served? This is the domain I am working on now. https://tinyurl.com/2afpa574 Ah, you need technical details. Here it is. -- WordPress Configuration -- Multisite: No Version: 5.7.2 Language: ro_RO WP_DEBUG: Disabled WP Memory Limit: 270M Permalink: /%year%/%monthnum%/%postname%/ Show On Front: posts Current Theme: Weaver Xtreme (4.4.7) Operating System: Linux PHP Version: 8.0.7 MySQL Version: 5.7.34 jQuery Version: 3.5.1 Server Software: LiteSpeed -- PHP Configuration -- Local Memory Limit: 400M Server Memory Limit: 32M Post Max Size: 32M Upload Max Filesize: 16M Time Limit: 900 Max Input Vars: 1800 Display Errors: N/AExpand Hi, the stale doesnt work the way you expected in this case, with LiteSpeed, the stale works as follow : assuming you have a page that cache has or about to be expired , then lets say , there is 10 people requested this same page at same time and then , the first user will trigger cache regeneration , and rest of 9 people will get the staled cache for this page , after this time , all newer visitor will get the cached generated by visitor 1 in which , stale cache is only lived like 1 or 2 seconds and then be flushed/replaced by newly regenerated cache on a heavy concurrent connection situation. Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference