mukoka

Is the affected image a background image or set by Javascript?

If a browser doesn’t support webp image type then the original image is used. This is mostly the case if iPhone Safari version < 13 is used, so use a browser that supports webp image if you check functionality of webp replacement.

Cache plugin shows webp image only if its size is smaller as the original image.

WooCommerce geolocation is cache compatible, but not cache warmup compatible, because the detection of user’s location is IP based. This makes it impossible to warmup the cache. You can only solve this without geolocation detection by asking the visitor where he comes from if the page is loaded first and set a cookie with a value based of the user selection. This cookie can be used to warmup the cache. If you offer different content (prices) based on the location there is no other way for cache warmup, so yes, the crawler is useless in this situation.

In the past there were regular problems when the Adsense script was loaded deferred or delayed. Therefore, the Adsense script was excluded from the ability to deferred/delayed loading. This exclusion is therefore not arbitrary, but is based on many years of experience. If you want to ensure that you do not suffer any disadvantages due to delayed loading, you should accept this general exclusion.

slow == page is not cached
fast == page is cached

To keep all pages fast use the built-in cache crawler frequently and check settings for Cache -> Purge -> Auto Purge Rules For Publish/Update

If the crawler is disabled at your host you can’t warmup the cache with built-in crawler, but there are 3rd crawlers that are especially made for the LScache Plugin and these crawlers can warmup the cache even when the built-in crawler is disabled.

One of the most important function of LScache (not the LScache plugin) is to provide cache varies (different cache copies) depending on specific parameters. If such parameters (HTTP parameters) can’t be provided by whatever CMS or plugin there is no way to bypass cache varies, but AJAX can do it. If you don’t want to use cache varies you need to use AJAX to provide prices depending on user roles. Sorry, this is the way how a HTTP page cache works.

The “whole sale plugin” must be able to set the price by user role AND by AJAX. Otherwise it is not possible to get what you try to get. Using AJAX is the best and the fastest way to prevent using of any cache vary and it is the best way to keep public cache and to warmup public cache.

Gravity can’t be switched off.

• This reply was modified 7 months, 1 week ago by mukoka.

@halfmack

It is essential that you do not use the -I parameter. WordPress and the LiteSpeed LScache plugin expect the response body query. Otherwise, a URL will not be cached, but the query for the response body is unique, so that it is not necessary for any other CMS to query the response body for a URL to be respected. The consequence of requiring the -I parameter is an exorbitant increase in traffic for the cache because much more data has to be transferred for the response bods. That’s why crawling and cache warmup take much longer.

You should also add the term “lscache_runner” to the UA agent. This UA Agent updates the cache and the TTL for the cache.

FYI: The built-in crawler’s block can easily be bybassed. Just ask Google how to do it. “How to enable LiteSpeed Cache Plugin Crawler for WordPress if it is disabled in LiteSpeed Server”

Use quotation marks to get the right search result.

• This reply was modified 7 months, 1 week ago by mukoka.
• This reply was modified 7 months, 1 week ago by mukoka.
• This reply was modified 7 months, 1 week ago by mukoka.
• This reply was modified 7 months, 1 week ago by mukoka.

I still don’t see any argument here.

The answer from a user who tries to compensate for insufficient knowledge through ignorance. Anyway, stop bothering this forum with unqualified comments that are of no use to anyone. This forum is for support and not pointless discussion by users who don’t know what they’re doing.

Why do you think I’m wrong?

Because you are not a developer and you don’t know how the Internet and a page cache like LiteSpeed LScache works.

Apparently you have more knowledge than any other PHP devloper and you also seem to know more about how the Internet and a page cache works. You should develop your own cache crawler based on your mysterious knowledge.

Just because the built-in crawler uses the sitemap to warm up the cache, the principle of cache warmup is always the same principle that exists in an HTTP request. If you have better knowledge about it that no one else seems to have, then you should file a patent for it.

You can’t turn off gravity, not even you.

Again, a page cache needs a HTTP request to make a URL cached and only the crawler makes a HTTP request and nothing else, but if the crawler is disabled you can’t run a HTTP request.

Sorry, you are wrong. To warmup the cache for whatever posts or page and for whatever reasons you need the crawler for it. Webhooks doesn’t have anything to do with it. URLs must be requested to warmup the cache again.

• This reply was modified 7 months, 2 weeks ago by mukoka.