Maurice

Thank you for your quick reply! And custom built xml sitemap seems to be the way then indeed. However most (or actually all) WP plugins I’ve found so far generate sitemaps automatically and don’t have the ability to easily create a custom sitemap with a couple of manually added links. If you have any tips or ideas I’d be happy to hear them.

I can easily create myself a custom sitemap however it would be difficult to explain to thousands of customers (I run a hosting company) how to create a custom sitemap themselves while they’ve never seen a line of code only using some default WP editor.

I’m trying to make it look as easy as possible so most customers would be able to create one themselves or, if LScache plugin would have the abililty to add a couple URL’s manually to crawl.

The crawler itself works perfectly as long as someone doesn’t have +10k (or even +100k) pages. Most of these pages hardly gets one visit per day so why cache them anyway. Ideally you’d only want to cache important pages.

The thing with caching is it all about performance for the enduser/visitor on the website and nothing else. The exact technique being used not that important.

So I do agree with you that when cached, LS Cache performs better. But WP Rocket keeps pages in cache while LS Cache depends on a crawler that comes by on a regular base. Even then, after the crawler has come by, some pages are still cache “missed” and end up slow loading the first time. This could be to a page update, plugin update etc. WP Rocket preloads the changed page immediately after saving which brings far more reliable performance.

It would be different when LS Cache is able to reliably keep pages in cache like WP Rocket does. Better performance, better conversion and more visitors due to a better ranking/CWV. Consistant performance is viable for sites like webshops, blogs with ads or affiliate based websites.

It seems like for the moment WP Rocket is your best bet here. Even when te crawler is enabled, WP Rocket is far better in maintaining pages in cache against LS Cache. For instance WP Rocket automatically preloads any changed (and purged) page whereas LS Cache is losing the cache until the crawler has crawled the whole site again.

That said: it probably has to do with the technical considerations too. WP Rocket seems far more reliable on serving cached content. Not sure why, but I’m seeing regular cache misses even when absolutely nothing on the site happens and TTL set at 1 week. WP Rocket serves content from cache until TTL expires when it will preload automatically again.

In theory, there is no need for a daily or hourly (or whatever interval) cron to crawl when all content is simply cached. There’s only need for a new crawl when specific pages get purged because of changes (and then only these pages need to be crawled) or expired TTL which can be a week or even more.

WP Rocket is far more superior on this prelod topic.

• This reply was modified 3 years ago by Maurice.

We have kinda the same problem with many clients lately, including our own website. The only way to fix this seems to go to WordPress LS Cache plugin > Toolbox > Choose “Empty all cache”, not “Purge all”. This seems to help the issue of randomly 404 errors of .css files breaking the website.

I don’t get the difference. I’m sure from a technical standpoint there is a reason for this, but from user perspective its confusing.

Same goes for the solution mentioned above, what is the difference between:

“Purge All and Purge All – CSS/JS Cache” or;
“Purge All”?

When I want to “Purge All Cache”, I guess I would like to purge all cache, not “Purge All Cache (except for the ultrasecret hidden for CIA CSS/JS)”.

Most WordPress users, I suspect +50%, are not very technical driven users and don’t see the difference. It it hard to explain all the different options in purging.

Ofcourse open to idea’s!

• This reply was modified 3 years, 5 months ago by Maurice.
• This reply was modified 3 years, 5 months ago by Maurice.
• This reply was modified 3 years, 5 months ago by Maurice.

Oops, sorry for my late reply ?? But ok… that was quite a quick fix. Works like a charm and thank you so much!