If you’ve seen “BerqWP CDN” mentioned in your dashboard and weren’t sure what it actually does, this article explains what it is, what it delivers, and why it’s turned on by default for most sites.
TL;DR: BerqWP CDN delivers your site’s images, CSS, JavaScript, and font files from a fast global network instead of your own server, so visitors everywhere get those files quickly. It’s enabled by default on BerqWP Premium, and several other BerqWP features, including Fluid Images, depend on it being on.
What BerqWP CDN Actually Does
Every WordPress page loads a set of static files behind the scenes: images, stylesheets, JavaScript files, and web fonts. Normally, your own server has to deliver every one of those files to every visitor, no matter where in the world that visitor is. If your server is in one location and a visitor is on the other side of the world, that distance adds real delay before anything on the page can finish loading.
BerqWP CDN solves this by delivering those static files from a global network instead of your own server. A visitor gets the files from a location close to them rather than from wherever your hosting happens to be, which is what makes the page ready to use in a fraction of the time.
What’s Actually Powering It
BerqWP CDN is powered by Cloudflare’s global network, with files served from BerqWP’s own CDN infrastructure. You don’t need a Cloudflare account, an API key, or any setup of your own, it works automatically once enabled. This is different from BerqWP’s separate Cloudflare Edge Cache integration, which is an optional feature where you connect your own Cloudflare account specifically for page caching, BerqWP CDN doesn’t require that at all.
Why It’s On by Default
BerqWP CDN ships enabled by default because there’s rarely a reason to turn it off. It delivers your images, CSS, JavaScript, and font files faster for every visitor regardless of where they’re located, with no configuration needed. It’s also a dependency for other BerqWP features. Fluid Images, which serves correctly sized, retina-ready images in AVIF or WebP based on a visitor’s device, specifically requires BerqWP CDN to be turned on to work.
If You Need to Keep Something Off the CDN
Not every file necessarily needs to go through the CDN. If you have a specific file that should always load directly from your own server instead, BerqWP includes a CDN Exclusions setting for exactly that. See “How to Exclude Files From BerqWP’s CDN Delivery” for the details on how that works.
