Cloudflare/Litespeed & Cloudinary

  • I don’t need help with anything specific, just asking general advice:

    I recently installed Cloudinary as a CDN to serve images. I noticed that I also have Cloudflare/Litespeed installed and it looks as if they do similar things.

    Are there likely to be any conflicts between the two? Is it a good idea to have both or is Cloudinary unnecessary if I already have CLoudflare/Litespeed ?

    Appreciate any advice, thanks.

    • This topic was modified 2 years, 8 months ago by Jan Dembowski.
Viewing 2 replies - 1 through 2 (of 2 total)

  • Generally, you should not use two different tools to perform the same function… as the time it takes for the second tool to wait for the first tool to finish can be far more than the potential gain from using the two tools together. And when there’s a problem, it can be a nightmare trying to pinpoint where the problem is.

    Beyond that general recommendation, when it comes to website optimization, there’s just one piece of advice that’s useful all the time: TEST to determine what gives YOU the best performance.

    Any advice people give you here or elsewhere to use this solution vs that solution is coming from their own experiences (and often untested assumptions)… which may not necessarily apply to your specific situation and performance bottleneck.

    Good luck!

    Hi @dsb01
    I’d like to suggest you use Cloudflare for DNS and Cloudinary for CDN.

    Because I found Cloudflare DNS is way faster and it also gives me protection from DDOS attacks in the FREE plan.

    On the other hand, Cloudinary is a very good solution for FREE CDN. It serves images in .webp format, optimize images via the FLY ON THE GO method so your original image won’t be touched.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Cloudflare/Litespeed & Cloudinary’ is closed to new replies.