A CDN (content delivery network) is a set of servers spread across different regions that keep cached copies of your site's files. When someone visits your site, they get served from the server closest to them instead of always hitting your origin server. That means faster load times for visitors far from your host's datacenter, less load on your origin during traffic spikes, and some protection against attacks that try to overwhelm a single server.
If you're on Flashcloud, this isn't something you need to set up from scratch. Hosted domains get Cloudflare-backed DNS by default, and proxy mode (the actual CDN layer) can be switched on per domain from the Cloudflare CDN tool in the portal sidebar.
How a CDN actually speeds things up
Without a CDN, every visitor's request travels all the way to your origin server, wherever it physically is. A visitor in Singapore hitting a server in New Jersey pays for that round trip on every request, every asset, every page load.
A CDN sits in front of your origin. Its edge servers, positioned in many regions, cache static content: images, CSS, JavaScript, and sometimes full HTML pages. When a request comes in, it's answered from the nearest edge location if a cached copy exists. Only cache misses, or requests for content that can't be cached, go back to your origin.
The other benefit is capacity. If a page suddenly gets a lot of traffic, cached content gets served from the edge network instead of hammering your origin server directly. The origin sees a fraction of the actual request volume.
What a CDN does and doesn't cache
Static assets, images, fonts, CSS, JS, are the easy case: they don't change per visitor, so they're cheap to cache for long periods. Full HTML pages can be cached too, but only if the page is the same for every visitor. Pages that show a logged-in user's name, a cart total, or any per-visitor data need careful cache rules, or they shouldn't be cached at all.
This is where caching rules and purge tools matter. When you update a page and the cached version is stale, you need a way to clear it immediately rather than waiting for it to expire on its own. On Flashcloud, the Cloudflare CDN page in the portal has a Purge cache action for exactly this, alongside a Caching toggle per domain.
Worth knowing: a CDN's cache is separate from other caching layers your site might have. If you're running WordPress, your site likely also has page and object caching happening closer to the origin. Flashcloud's WordPress installs come with LiteSpeed Cache pre-configured plus Redis object cache, which speeds up dynamic requests before they even reach the CDN layer.
CDN vs. proxy: what "proxying" means
People sometimes talk about a CDN and a "proxy" as separate things, but for services like Cloudflare, they're the same switch. When a domain is proxied, traffic to it routes through the CDN's network instead of connecting directly to your origin's IP address. That's what makes caching, and features like SSL and bot mitigation, possible in the first place.
On Flashcloud, this is a per-domain toggle (Proxy) in the Cloudflare CDN tool, on by default for hosted domains. Turning it off sends traffic straight to your origin server with no caching or edge protection in front of it.
If a proxied domain starts redirecting in a loop, check this setting first.
When a CDN isn't enough on its own
A CDN reduces load and latency, but it isn't a substitute for a fast origin. If your database queries are slow or your WordPress install is bloated with unused plugins, caching only hides the problem for cached requests, uncached ones, and any dynamic page, still hit the slow path underneath.
It also isn't primarily a content strategy tool. If you're trying to improve site speed as part of a broader SEO or content push, a CDN is one piece; the other is making sure what you publish is worth the traffic it gets. If that's the goal, a simple weekly content routine is a good next read for keeping a blog consistently healthy alongside a fast site.
If something looks wrong
If you toggle proxy or caching settings and something breaks, like a redirect loop, mixed content warnings, or a page that won't update after a purge, open a ticket from Support in the portal. It's real people, not a bot, and they can help troubleshoot the Cloudflare configuration on your domain.