LucasRolff

Hi tores54,

Testing the images in the Google Drive zip file, the majority of the images does indeed not end up with a generated webp image:
– 7NDNMLIqak0.jpg
– Fk5xo6hxgIY.jpg
– FRSbHtCKINQ.jpg
– o-PpIxUWSMA.jpg
– SkRpLtCsJRk.jpg
– STci4WCoyfA.jpg
– ZkrxrclxCQ0.jpg

krWpoj_yMH0.jpg does get a webp image.

The way the decision is made whether there’s going to be a webp image, is based on a filesize comparison.

Whenever you send an image for optimization 3 things happens:

– We check the filesize of the original image fetched from your site, and record this (original_filesize).
– We optimize the image using a set of algorithms to generate the lowest possible size, with a slight quality loss (unless you have lossless optimization enabled). We then record the size (optimized_filesize).
– We generate a webp image based on the original image. The webp image will still have a slight quality loss. We then record this size as well (optimized_webp_filesize).

We then do a check whether the generated webp image’s filesize is smaller than the optimized jpeg/png filesize. If it’s smaller, you’ll get the webp image returned. If it’s bigger you’ll not get the webp image returned. Since you’re then increasing the size of the page, which is what you’re trying to prevent in the first place by using the image optimize function.

Since WordPress has different sizes (thumbnail + scaled/resized versions) for each image, the outcome may differ for each image as well. In some cases there can be optimizations, in other cases, there won’t be.

If we take 7NDNMLIqak0.jpg as an example:

– The size when uploaded to WP is 1299518 bytes.
– The optimized jpeg size is 447307 bytes.
– The webp imag size is 457024 bytes.

The webp image is thus 9717 bytes larger than the jpeg.

Since the webp image is larger, it won’t be returned.

It’s also worth noting that webp generally turns out larger for large images, it’s just how the webp compression works.

The swcfpc query string is a part of the “WP Cloudflare Super Page Cache” plugin, you might want to check their support page whether it’s possible to remove it.

Your website does not accept requests to /wp-json/litespeed/v1/notify_img, it simply gives a timeout.

You have to ensure the site (or server) will accept traffic from IPs listed on https://quic.cloud/ips

Currently if doing a request it results in the following:

* Hostname <DOMAIN> was found in DNS cache
*   Trying 82.79.xxx.xxx...
* TCP_NODELAY set
* connect to 82.79.xxx.xxx port 443 failed: Connection timed out
* Failed to connect to <DOMAIN> port 443: Connection timed out
* Closing connection 0
curl: (7) Failed to connect to <DOMAIN> port 443: Connection timed out

> Are new images automatically optimized on upload?

Yes, as long as you go to LiteSpeed Cache -> Image Optimization -> [2] Image Optimization Settings, and make sure “Auto Request Cron” is set to “On” (and ideally “Auto Pull Cron” is set to “On” as well).

Then the plugin will use the WP cron to request optimization for any image that has not yet been optimized (new or existing).

The 1000 images will go into a “fast” queue, the remaining images will go into a standard queue, which may be slower compared to the fast queue.

Standard queue is free, and will always be free – and you’re indeed limited to maximum 200 images per 5 minutes regardless of being in the fast or the standard queue. Except if you buy the “jumbo group” option, then you’re limited to 1000 images per 5 minutes.

The notify endpoint (/wp-json/litespeed/v1/notify_img) is giving a 404 not found page.

This usually happens if the backend IP changes or is configured incorrectly on my.quic.cloud.

Another reason can be that it’s being blocked/intercepted by some kind of application firewall either on the hosting providers systems or the site itself.

If you do not have a my.quic.cloud user, you can try doing a domain key refresh in WordPress -> LiteSpeed Cache -> General, and click on “Refresh Domain Key”.