Title: LS Cache Most Basic Setup for Use w/ QUIC.cloud Last modified: May 20, 2025 --- # LS Cache Most Basic Setup for Use w/ QUIC.cloud * Resolved [Nassim Sultan](https://wordpress.org/support/users/nassimsultan/) * (@nassimsultan) * [1 year ago](https://wordpress.org/support/topic/ls-cache-most-basic-setup-for-use-w-quic-cloud/) * Hello! I would like to add QUIC.cloud’s CDN to my site. In order to do that, I need to install LightSpeed Cache. I’m fine with doing that, but I already have two optimization plugins running and I’m concerned about overlap or interference. * With that in mind I’d like to know if there’s a way to disable all aspects of LS Cache. I assume that I can just go through and set everything to “off” but before I do that I wanted to check in to see if anyone has suggestions for how to approach this. * Alternatively, is there a very, very basic setup that I can use? I see that LS Cache has an “essentials” preset but even this has some level of redundancy with my other plugins. * Thanks! Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Support [litetim](https://wordpress.org/support/users/litetim/) * (@litetim) * [1 year ago](https://wordpress.org/support/topic/ls-cache-most-basic-setup-for-use-w-quic-cloud/#post-18475414) * [@nassimsultan](https://wordpress.org/support/users/nassimsultan/) or setup a stage site and test LSC for all optimizations. Is your server LTS?I would use just 1 plugin for optimizations. It’s not ok for your site to have multiple 🙂 - This reply was modified 1 year ago by [litetim](https://wordpress.org/support/users/litetim/). * Thread Starter [Nassim Sultan](https://wordpress.org/support/users/nassimsultan/) * (@nassimsultan) * [1 year ago](https://wordpress.org/support/topic/ls-cache-most-basic-setup-for-use-w-quic-cloud/#post-18475456) * [@litetim](https://wordpress.org/support/users/litetim/) Thanks for your reply! My server is not LTS. I hear you on using just 1 plugin for optimization. Ideally that’s what I would do. What I have found is that, although there is a lot of overlap between optimization plugins, they don’t all cover the same tasks. And so, to cover my bases, I am using two. I can assure that I have set them up such that there is no overlap–i.e., only one is handling caching, only one of them is handling heartbeat, only one of them minifying java and CSS, only one of them is handling fonts, etc. * I appreciate your suggestion to set up a staging site to test out the optimizations. Considering my current optimization setup (and that it is working well for me) I don’t need the optimizations offered by LSC, and so I would rather not go through that process–especially since my goal is simply to access QUIC.cloud’s CDN. * Considering all of this, do you have any recommendations for settings such that all optimization settings are disabled in LSC? I’d like to avoid conflicts between my plugins! Again, I assume that I simply need to set everything to “off”, but I want to be careful considering that I already have other optimization plugins doing their thing. * Thanks! * Plugin Support [litetim](https://wordpress.org/support/users/litetim/) * (@litetim) * [1 year ago](https://wordpress.org/support/topic/ls-cache-most-basic-setup-for-use-w-quic-cloud/#post-18475534) * [@nassimsultan](https://wordpress.org/support/users/nassimsultan/) If it works for you, ok 🙂Enabling CDN will allow to use LTS cache, that means all cache options will be available for non LTS servers.To use just CDN, I would turn off all LTS features and make the required changes for CDN on this page: [https://docs.litespeedtech.com/lscache/lscwp/cdn/](https://docs.litespeedtech.com/lscache/lscwp/cdn/) This is what I would do myself if I want to make this setup.I am here to help you, just shout for me :)) * Thread Starter [Nassim Sultan](https://wordpress.org/support/users/nassimsultan/) * (@nassimsultan) * [1 year ago](https://wordpress.org/support/topic/ls-cache-most-basic-setup-for-use-w-quic-cloud/#post-18477095) * Thanks, [@litetim](https://wordpress.org/support/users/litetim/)! I do have one follow up question for you regarding caching. Let me give a little context first, though. My goal in using a CDN is to speed up load times. My understanding is that caching is an important component to a CDN’s ability to serve content quickly. My host is SiteGround and so I am using their caching plugin. My understanding is that a caching plugin like this is different from a CDN’s caching abilities in that SG’s plugin caches info on SG’s servers whereas a CDN’s will cache info on their own servers. * With all of that in mind, how would I best go about using QUIC.cloud’s caching? Is it fully intertwined with LS Cache? * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [1 year ago](https://wordpress.org/support/topic/ls-cache-most-basic-setup-for-use-w-quic-cloud/#post-18477282) * in order to properly utilize the QC CDN , LiteSpeed Caceh plugin is required * LiteSpeed plugin will send out the instruction to purge CDN as well , when it purges cache locally on LiteSpeed Webserver Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘LS Cache Most Basic Setup for Use w/ QUIC.cloud’ is closed to new replies. * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181) * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/) * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq) * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/) * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/) * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/) ## Tags * [optimization](https://wordpress.org/support/topic-tag/optimization/) * [quic.cloud](https://wordpress.org/support/topic-tag/quic-cloud/) * 6 replies * 3 participants * Last reply from: [qtwrk](https://wordpress.org/support/users/qtwrk/) * Last activity: [1 year ago](https://wordpress.org/support/topic/ls-cache-most-basic-setup-for-use-w-quic-cloud/#post-18477282) * Status: resolved