Wordpress LScache Plugin: Initial Server Response Time with Litespeed Cache is 2+ seconds?
Last Updated on: Wed, 15 Apr 2026 00:00:02 I dont understand? how is a simple WordPress installation on Apache returning 200ms initial server response time, but when I flip it to Litespeed and turn on Litespeed Cache, that goes up to 2 seconds and up? What am I missing? How is Litespeed / Cache helping in this case? Ive even used the crawler and everything, and still, there is a 2 second backend or server delay showing in GTMetrix and Page Insights over and over and over. What am I missing? UPDATE: What solved it for me is turning off all Guest mode options and optimizations and Caching Mobile option as well. Those options somehow added all this extra padding, and the performance has gone back to amazing now. Ignore the above request. Well, spoke too soon? As soon as I enabled the Image WebP Replacement in Image Optimization (after enabling the QUIC.cloud integration), it created another cron / crawler for WebP images, and now, again, with multiple crons/crawlers it is causing the 2 second initial response time from the server? Why is this happening? How do we fix this? Hi, when you run it on Apache , the page will not be cached , which means every time it has to go through all the optimization process , that could take some times example like this no cache plugin WP site : TTFB 500 ms cache plugin + cache miss : TTFB 1000 ms (additional TTFB created by optimization process on first access) cache hit: TTFB 100 ms but when you are not using LiteSpeed webserver, as the page wont be cached , so you will literally hit the cache miss case all the time Best regards, @CacheCrawler see my post above? I guess you literally typed yours out while I was typing mine. Let me repeat: As soon as I enabled the Image WebP Replacement in Image Optimization (after enabling the QUIC.cloud integration), it created another cron / crawler for WebP images, and now, again, with multiple crons/crawlers it is causing the 2 second initial response time from the server? Why is this happening? How do we fix this? Hi, please provide me the report number , you can get it in toolbox -> report -> click send to LiteSpeed because once you enable webp replacement , it will need to create 2 separated cache , one for browser that supports webp , one for browser that doesnt support it Best regards, Report # is SHSZKPMU Thank you! you need to go to Cache -> Cache -> Enable Cache , set it to ON Sorry, had that turned off for a few minutes. I am getting mostly misses now on the crawlers. https://prnt.sc/1wb7ubf Should I worry about that? Hi, thats normal since you just re-enable the cache Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference