Wordpress LScache Plugin: Crawler not pre warming
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, Im unable to get the wordpress crawler to pre warm the cache The crawl shows its crawling, everything is enabled and setup per guide lines but if I visit a page the notes at the bottom of the page shows its a freshly cached Server is in Atlanta and Im in UK so that would explain the time difference between the two So I can purge everything and leave the crawler for ie 6 hours and when I visit any pages it seems to generate it at that time and not pre cached Any help Keith Here is the info from the crawler Current sitemap crawl started at: 11/18/2020 19:20:02 The next complete sitemap crawl will start at: 11/22/2020 07:30:25 Last complete run time for all crawlers: 623 seconds Run time for previous crawler: 23 seconds Current crawler started at: 11/18/2020 19:30:02 Last interval: 11/18/2020 19:30:02 Ended reason: end Last crawled: 567 item(s) I visited another page and get this Same time I clicked it Keith Hi, the timestamp issue is false alert , its more like bug in server timezone and your wordpress timezone setting. from your crawler information , that is probably means , at 18th , the crawler crawled page, but at certain moment alone the way until 22th , there was a purge happened and purge cache, so it has to re-generate Best regards, but every time I visit my sites that use the crawler it caches then there and then Ideally shouldnt it pre cache the full site and serve pre cached pages not create them on the fly Example Current sitemap crawl started at: 58m 56s ago The next complete sitemap crawl will start at: 11/23/2020 13:05:27 Last complete run time for all crawlers: 625 seconds Run time for previous crawler: 25 seconds Current crawler started at: 48m 56s ago Last interval: 48m 56s ago Ended reason: end Last crawled: 567 item(s) but when i visit any pages on the site at 17:49 here and if i do this in 30 mins i will get the new current time again ? so this would mean its generating it again and not pre done Cheers Keith Forgot to mention the crawl interval is set to 3600 seconds for testing purpose, this to ensure pages are cached If I use WP supercache this works perfectly Maybe im missing the actual point of the crawler Cheers Keith Here is the debug log, as you can see it is creating new cache each visit Just this line mean its stale cache > [Ctrl] X Cache_control -> stale 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] ?? ??GET HTTP/1.1 (HTTPS) /orlando-property-management/ 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] Query String: 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] HTTP_REFERER: https://www.xxxxx.com/ 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] User Agent: Mozilla/5.0 (Windows NT 10.0 Win64 x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.66 Safari/537.36 Edg/87.0.664.41 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] Accept: text/html,application/xhtml+xml,application/xml q=0.9,image/webp,image/apng, / q=0.8,application/signed-exchange v=b3 q=0.9 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] Accept Encoding: gzip, deflate, br 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] X-LSCACHE: true 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] LSCACHE_VARY_COOKIE: cookie_notice_accepted 11/23/20 13:45:25.468 [x.x.x.x:37730 1 Slr] LSCACHE_VARY_VALUE: +webp 11/23/20 13:45:25.475 [x.x.x.x:37730 1 Slr] [Ctrl] X Cache_control -> stale 11/23/20 13:45:25.482 [x.x.x.x:37730 1 Slr] [Router] get_role: 11/23/20 13:45:25.482 [x.x.x.x:37730 1 Slr] [Media] init 11/23/20 13:45:25.482 [x.x.x.x:37730 1 Slr] [LQIP] init 11/23/20 13:45:25.482 [x.x.x.x:37730 1 Slr] [CDN] init 11/23/20 13:45:25.482 [x.x.x.x:37730 1 Slr] ? Task init 11/23/20 13:45:25.483 [x.x.x.x:37730 1 Slr] [Router] LSCWP_CTRL bypassed empty 11/23/20 13:45:25.483 [x.x.x.x:37730 1 Slr] [GUI] init 11/23/20 13:45:25.486 [x.x.x.x:37730 1 Slr] [Ctrl] X Cache_control init on 11/23/20 13:45:25.516 [x.x.x.x:37730 1 Slr] [Core] Footer hook called 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Core] Footer check passed 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Router] get_role: 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Router] get_role: 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Vary] role id: failed, guest 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Router] get_role: 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Router] get_role: 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Vary] no custimzed vary 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] ??? X-LiteSpeed-Cache-Control: public,max-age=5184000 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] ??? X-LiteSpeed-Tag: 3a0_HTTP.200,3a0_page,3a0_URL.867f2104520863e8d88b1297a9eaf788,3a0_Po.149,3a0_PGS,3a0_ 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Core] Footer check passed 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Media] finalize 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Media] buffer_webp attribute img.src 11/23/20 13:45:25.517 [x.x.x.x:37730 1 Slr] [Media] webp replacing: /images/USA-flag-20a.png => LiteSpeed Media->replace_webp(/images/USA-flag-20a.png)@851 => LiteSpeed Media->_replace_buffer_img_webp()@740 => LiteSpeed Media->_finalize()@465 => LiteSpeed Media::finalize( Hi, Please check this wiki Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference