Wordpress LScache Plugin: Higher TTFB on Apache
Last Updated on: Wed, 15 Apr 2026 00:00:02 Good day support, I would like to use this plugin on an Apache server. But compared to other caching plugins the Time To First Byte (TTFB) is significantly higher. Causing a short lagg when browsing the website. Is that normal behavior as it is not on a LSWS? For comparison reasons Ive set up 2 exactly the same websites on 2 different domains BUT they are on the same server. Maybe you can point me in the right direction. Looking forward to your reply. Hi @alusion, our caching feature requires OpenLiteSpeed, commercial LiteSpeed products or LiteSpeed-powered hosting. So plain Apache server might not work. Hi Stanley. Thanks for the fast reply. Yes I know. But you have stated on the main page that the general features also work on an Apache server. And they do. Every seems to work fine. The TTFB is only significantly higher. I wonder why this is. I assume this should not me the case. Hi, by significantly higher , as how much higher ? Also could you please make multiple time (as network fluctuates ) comparison on full waterfall page loading ? Best regards, Ruikai. When browsing the websites with Network tab open (Chrome DevTools) the normal TTFB is between 20ms ? 60ms TTFB. While with LS Cache it is between 700ms ? 950ms. LS Cache: http://prntscr.com/nheesw Other: http://prntscr.com/nhef6f Have the feeling this should not be the case and stumbled upon serious LS Cache / Apache conflict as I am not a novice. Can provide you with admin logins if needed. I rather dont share it right here. Not for confirguring. But to see the webserver and the TTFB issue. Hi, LiteSpeed plugin , the general optimization feature works on non-LiteSpeed , but the caching feature will NOT work there. Therefore you are basically comparing dynamic-generated-page against statically-cached-page. Id like to ask you to try LSCWP on OpenLiteSpeed or set up Quic Cloud to try the caching feature. Best regards, Then it makes totally sense! Please add the information to the main page as it is not really clear. Solved.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference