How to reduce cache warmup crawl time by up to 70%

[LiteCache]

It's primarily about Wordpress or the LScache Plugin (LSCWP) for Wordpress, but the problem affects every LiteSpeed Cache Plugin for which a Cache Warmup Crawler is available.

In order to benefit from LScache, it is imperative that the cache is warmed up. If you don't do that or maybe don't even know that you can warm up the LScache, you only have a very limited use of it. The fact is that the loading time can be improved by several 100% by warming up. LScache turns e.g. 4 seconds loading time into a few milliseconds. The loading time is not everything, but the loading time already decides with the first request of a page whether the user jumps off immediately or stays on the page if the loading time is too long. Therefore it is essential that you warm up your pages or the cache for it.

The problem is that the warm-up process not only consumes a lot of resources and impairs performance, but can usually last longer. Online shops are particularly affected by this. If the stock level or any other product information changes, then this change inevitably affects the whole shop. This means that not only the URL or the cache of the URL for 1 article has to be purged, but basically the entire cache. After all, products and their product information can appear anywhere in the shop.

If, as a result, you have to purge the entire cache with every order or even the smallest changes to a product, you can only get very little use from a cache.

Now what could be a solution for this?

According to our research, a maximum of 30% of all available URLs on a page are actually and regularly accessed. Now, if the sitemap.xml serves as the basis for the cache warmup, it means that up to 70% of unnecessary resources are used for something for which no one has any benefit. The logical conclusion would therefore be that you only warm up the cache of URLs that are actually requested regularly. This dramatically reduces the effort, time and resources required for the cache warmup process.

None of the plugins offered by LiteSpeed provide a function that fulfills this requirement. All LiteSpeed plugins only use the Sitemap.xml.

But the Kitt CacheCrawler can solve the problem. It has exactly this function, but we are already working on making this function available at least for the LiteSpeed LScache Plugin (LSCWP) for Wordpress.

Benefit from it now and use the Kitt CacheCrawler, which was specially programmed for LiteSpeed LScache. The Kitt CacheCrawler is available for many applications and is not limited to Wordpress and the LScache Plugin for WP.

https://www.cachecrawler.com

​

 

[atrix]

If, as a result, you have to purge the entire cache with every order or even the smallest changes to a product, you can only get very little use from a cache.

You should not be purging the entire cache hardly ever. Plugin updates for example can cause it but if you change a product it should only affect pages that product appears on and the module for wordpress handles this already. A new order should have zero affect on caching. Your cache will take a long time to warm up on big sites but it should stay warm most of the time.

 

[LiteCache]

You should not be purging the entire cache hardly ever. Plugin updates for example can cause it but if you change a product it should only affect pages that product appears on and the module for wordpress handles this already. A new order should have zero affect on caching. Your cache will take a long time to warm up on big sites but it should stay warm most of the time.

It would be nice if you could do it the way you suggest. However, you seem to lack the relevant knowledge. The problem that the cache has to be purged affects WooCommerce users in particular, but not only. Products in a shop, their information about them and their status are not limited to the product page. Products can be displayed anywhere in the shop. Therefore it makes little sense to only purge the cache of the product page. If you didn't do that, it would mean that item prices or availability, for example, would no longer be the same on all pages. The cache plugin for WP therefore has to clear the cache for all relevant pages and this often means that the entire cache has to be purged. Maybe you should do a little more research on the subject.

 

[atrix]

I run several woo sites on litespeed with cache. I've never had an entire purge just because I updated a single product. I think you're just doing something wrong.

You're right that it's all relevant pages, but that being "the entire cache" as you suggested is wrong. Sorry for trying to help you won't make that mistake again Maybe don't disguise your ads as a help question either.

 

[LiteCache]

If you run not just one, but several WooCommerce sites, then you are inevitably bound to the purge behavior of the cache plugin. This inevitably means that in the event of a product update, not only the cache of the product page, but also the cache of the categories will be purged. This is still not the purging of the "entire cache", but it is almost the same.

But I'm not disguising anything here. It is primarily about relativizing the consequences of purging the cache, or only warming up the cache of the pages with the crawl, which is ultimately relevant.

As already mentioned, you should deal with the caching, the purging and the cache plugin for WP and their functions a little better, because only then you will be able to understand the problem.