Title: Keeping cache warm Last modified: April 2, 2021 --- # Keeping cache warm * Resolved [kdfr](https://wordpress.org/support/users/kdfr/) * (@kdfr) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/) * A warm cache that works well and is well documented can be found here: * [sitemap-cache-warm](https://github.com/khromov/sitemap-cache-warmer) * Here is an excerpt from the log when calling the warm cache in the browser: * {“status”:”OK”, “message”:”Processed sitemap: [https://www.baerbels-naturfoto.de/sitemap.xml”](https://www.baerbels-naturfoto.de/sitemap.xml”);,“ count”:2324, “duration”:127.06444191932678,”log”:[], “visited_urls”:[ “[https://www.baerbels-naturfoto.de/”](https://www.baerbels-naturfoto.de/”);“ [https://www.baerbels-naturfoto.de/monatsfoto2018/”](https://www.baerbels-naturfoto.de/monatsfoto2018/”);,“ [https://www.baerbels-naturfoto.de/monatsfoto2019/”](https://www.baerbels-naturfoto.de/monatsfoto2019/”);,“ [https://www.baerbels-naturfoto.de/monatsfoto2020/”](https://www.baerbels-naturfoto.de/monatsfoto2020/”);,“ [https://www.baerbels-naturfoto.de/monatsfoto2021/”](https://www.baerbels-naturfoto.de/monatsfoto2021/”);,..] * But no matter which warm cache I use, the WP pages are not cached (allow_url_fopen in php.ini is active). If I call up the pages via the browser, the cache is only activated at this point (). Is there a setting in the LiteSpeed Cache plug-in to be observed? If I use preheating with the WP Fastest Cache plug-in, it works correctly. Viewing 8 replies - 1 through 8 (of 8 total) * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14270829) * Hi, * LiteSpeed Cache plugin has its own crawler for pre-cache the pages * Best regards, * Thread Starter [kdfr](https://wordpress.org/support/users/kdfr/) * (@kdfr) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14271757) * Hi [@qtwrk](https://wordpress.org/support/users/qtwrk/), * thank you very much, but my search for a working Warm Cache Cralwer resulted from this: * [LiteSpeed Crawler is disabled on most shared hosts.](https://wordpress.org/support/topic/keeping-cache-warm/) * Ok., can’t be changed. * Best regards * Thread Starter [kdfr](https://wordpress.org/support/users/kdfr/) * (@kdfr) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14272376) * I have now run Purge All-LSCache in the LiteSpeed ​​Cache Toolbox and then checked it with [LSCache Check](https://check.lscache.io/). * The display is: X-Litespeed-Cache: miss * Then I let the warm cache run and the LCCache check showed: X-LiteSpeed-Cache: hit * This measurement shows the correct result and the desired function of the cache. * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14272619) * I’m sorry ? * if it works as desired, then what is the issue? * Thread Starter [kdfr](https://wordpress.org/support/users/kdfr/) * (@kdfr) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14276542) * Hi [@qtwrk](https://wordpress.org/support/users/qtwrk/), * the problem is: Although the warmCache crawler is running, which is confirmed by the LSCache check, the TTFB is approx. 500 ms when it is first called and only approx. 50 ms when it is called afterwards. The last line in the page source text with the current time is only displayed when the website is called up in the browser: The time when the WarmCache Crawler first visited the site is not displayed. * Best regards, * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14279989) * Hi * Please try make your own crawler to mimic full Chrome header * Best regards, * Thread Starter [kdfr](https://wordpress.org/support/users/kdfr/) * (@kdfr) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14283277) * Hi [@qtwrk](https://wordpress.org/support/users/qtwrk/), * Thank you for your kind and persistent support. Unfortunately, my specialist knowledge is no longer sufficient to carry out further steps. Perhaps one day there will still be a crawler in the Litespeed cache that can run independently of the hoster. * Best regards! * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14285401) * Hi, * I am not sure how your crawler works , but a reasonable expectation is that it should be able to send out certain user agent * like chrome has UA like `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/ 537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36` * this needs to be send alone with crawler to the server to make it (pre)cache for Chrome browser * Best regards, Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘Keeping cache warm’ is closed to new replies. * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181) * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/) * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq) * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/) * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/) * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/) * 8 replies * 2 participants * Last reply from: [qtwrk](https://wordpress.org/support/users/qtwrk/) * Last activity: [5 years, 3 months ago](https://wordpress.org/support/topic/keeping-cache-warm-2/#post-14285401) * Status: resolved