It doesn’t convert all images to webp and has an error displaying the original

Hi Eugenio,

Were you having problems with the assets CDN by any chance – especially with Premium plugins or themes?

Thank you.

Hi Eugenio,

WP Rocket doesn’t serve your CSS or JS through a CDN. It only minifies or combines them, but the files are still delivered from your own server. StaticDelivr actually serves assets from a CDN.

For example, your original theme file might be:

/wp-content/themes/twentytwentythree/1.0/style.css

StaticDelivr would turn that into something like:

https://cdn.staticdelivr.com/wp/themes/twentytwentythree/1.0/style.css

But if WP Rocket rewrites it into a combined local file, such as:

/wp-content/cache/min/style-abc123.css

then that file will always come from your server, not the CDN, because the original URL no longer exists for StaticDelivr to rewrite.

So the only real question is which is faster on your setup. Do you want to test whether your site loads quicker with StaticDelivr’s Assets CDN on and WP Rocket’s combining off, or with StaticDelivr off and WP Rocket’s combining on?

Best regards.

Hi Eugenio,

Thanks for letting me know. I agree, if WP Rocket is giving you the best results, it’s best to stick with that.

To be honest, making the assets CDN fully compatible with WP Rocket is basically impossible. StaticDelivr is a CDN for open-source assets, so it serves original files straight from the WordPress.org repository. WP Rocket works by changing and combining those files into unique versions on your server. Since the files aren’t originals anymore, the CDN can’t find them to serve them.

It would be cool to see if LiteSpeed actually feels faster for users in different cities globally though. Sometimes a global CDN setup performs better in the real world for distant users, even if local speed scores look similar.

Thanks again for all the help testing these things out! I’m glad the images are working well now.

Best regards.