What is a CDN?

A CDN delivers your website content from servers close to each visitor reducing load times globally. CloudSonic includes Cloudflare Enterprise CDN on every hosting plan at no extra cost.

CloudSonic
CloudSonic
Last Updated September 10, 2026

TL;DR CDN

A CDN, or content delivery network, is a geographically distributed network of servers that work together to deliver web content to users from the location closest to them. Instead of every visitor's request travelling all the way to your origin server no matter where they are in the world, a CDN stores cached copies of your content on servers positioned strategically around the globe. The result is faster load times, lower server load, and a more consistent experience for visitors regardless of their location. CloudSonic includes Cloudflare's global CDN on every hosting plan as part of the Cloudflare Enterprise stack, covering 310 plus edge locations worldwide. CDN delivery works closely with edge caching and anycast routing to make the whole system as fast as possible.

How a CDN Works

When a visitor requests a page from your website, that request travels from their device across the internet to your origin server, which processes it and sends the response back. Without a CDN, every visitor makes this full round trip regardless of where they are in the world. A visitor in Tokyo requesting a site hosted in Sydney experiences significantly more latency than a visitor in Melbourne making the same request. A CDN solves this by placing servers called edge nodes in locations around the world and storing cached copies of your content on them. When a visitor in Tokyo makes a request, it goes to the nearest edge node which serves the cached content immediately without involving your origin server at all.

The first time a piece of content is requested after the cache is empty, the edge node fetches it from the origin server, serves it to the visitor, and stores a copy. Every subsequent request for the same content from visitors near that edge node is served from cache. This is called a cache hit. The CDN also handles DDoS protection, SSL termination, and security filtering at the edge, meaning threats are neutralised before they ever reach your origin server. Anycast routing ensures each visitor is automatically directed to the nearest edge node without any manual configuration.

Why a CDN Matters for Your Website

The speed at which your website loads for visitors around the world is directly determined by how far their requests have to travel. Without a CDN, all requests go to your origin server regardless of the visitor's location. A visitor in Tokyo, London, or New York all experience the full network latency of the distance to your server. With a CDN, those visitors are served from an edge node close to them and the difference in load time can be several seconds. Beyond performance, a CDN also absorbs traffic spikes and DDoS attacks at the network edge before they reach your origin server. A viral post or a sudden traffic surge that would overwhelm a single server is distributed across the CDN's global network and handled without your origin server even noticing. For any website with visitors outside its immediate geographic region, a CDN is not optional infrastructure, it is fundamental.

Frequently Asked Questions on CDN

Does my website need a CDN if it only has visitors in one country?

The performance benefit is smaller for single-country traffic but a CDN still provides value through reduced origin server load, DDoS protection, SSL termination at the edge, and edge caching. If your visitors are geographically concentrated, the security and reliability benefits alone justify using a CDN even without the global distribution advantage.

What is the difference between a CDN and web hosting?

Web hosting is where your website lives and runs. A CDN is a delivery layer that sits in front of your hosting and distributes your content closer to visitors. They serve different purposes and work together rather than replacing each other. Your managed WordPress hosting on CloudSonic is your origin. The CDN is what delivers it globally.

Does a CDN store my entire website?

A CDN caches content rather than storing your website permanently. It keeps copies of frequently requested content on edge nodes for a defined period, serving them to nearby visitors. Dynamic or personalised content that changes per visitor, like logged-in pages or cart contents, bypasses the CDN cache and is served fresh from your origin server each time.

Can a CDN break my website?

A misconfigured CDN can cause issues like serving stale cached content after you update your site, or caching pages that should not be cached like checkout or account pages. CloudSonic's CDN configuration handles these rules correctly by default for WordPress and WooCommerce, and you can purge the cache manually from your dashboard at any time.

How does a CDN handle my SSL certificate?

The CDN terminates the SSL connection at the edge node closest to the visitor, which is why visitors see a padlock even when connecting to an edge node rather than your origin server. The connection between the edge node and your origin server is also encrypted. CloudSonic manages all SSL configuration through Cloudflare Enterprise so you do not need to handle certificates separately for the CDN layer.