supervisior

The crawler is a PHP script that cannot request itself, so it needs another script that requests the crawler and this can only be done with a cron job.

You don’t use LiteSpeed web server. This web server is necessary to use all features from cache plugin, so you can’t use main features of the cache plugin like cache function, Guestmode, Cache Mobile and webp replacement. To solve the current issue disable Guestmode and check https://quic.cloud. With quic.cloud you get all features and power from LiteSpeed cache plugin without changing your hosting.

There is no hook for this in LiteSpeed cache plugin. If you want to purge CF cache you have to do it in CF control panel.

FYI: If you use CF caching for dynamic pages this causes huge conflicts, because CF doesn’t respect LiteSpeed Cache Plugin cache header.

There is actually no reason why the webp replacement function shouldn’t work. However, if you state that you have apparently installed additional plugins for image optimization, then there is definitely a reason. Deactivate and uninstall all other optimization and image optimization plugins because this is the immediate cause of conflicts and very likely the reason for your problems.

Check the Javascript settings. If the load Javascript “delayed” option is selected, then change this setting to Javascript “deferred”. If that doesn’t solve the problem, then you have to exclude the JavaScript responsible for displaying the menu from the optimization.

The map is a snapshot showing the cache status after crawling. If the cache of a URL is changed by any actions, then this changed status will not be displayed in the map, which is technically not possible.

In principle, you can also use the CF plugin, but you will then have to deactivate the settings for webp replacement, guest mode and cache mobile, as CloudFlare neither recognizes nor supports these functions. Otherwise you will get significant glitches and malfunctions, which is also the reason why the LiteSpeed Cache Plugin indicates that the CF is not compatible with the LiteSpeed Cahe Plugin. The simple explanation for this is that both plugins do almost, but only almost, the same thing, but the CloudFlare plugin is not compatible with the special optimization functions. That’s why I recommend you use quic.cloud instead of CouldFlare, because this is the only way you can use the advantages of a CDN while using a page cache.