A CDN (Content Delivery Network) is, in plain terms, a way of copying your website's images and pages ahead of time onto many local branch shops dotted around the world, so that when a visitor opens your site they collect everything from the branch nearest them instead of making the long round trip back to your one main server every time. That is why it feels faster. Those scattered branches are, in technical terms, the edge nodes. For a Vancouver small business, a CDN earns its keep in three concrete ways: even your local visitors get a faster site, your site gains a buffer when traffic suddenly spikes (whether from a malicious attack or from going viral on the local news overnight), and if you have overseas or Asian customers, their access to your site improves noticeably. This article will not teach you to set one up yourself. It explains what a CDN actually is, how it relates to your website server and your domain, and whether your particular business needs one at all.
Who should read this? ❓
If your business has a website and you have run into any of these, this is worth a few minutes: someone has suggested you "put a CDN in front of your site" and you have no idea what that is or whether it would help; customers tell you your site is slow to load, especially ones who are out of town or overseas; your business gets a wave of traffic every so often (holiday sales, a news mention, an event); or you worry about your site being attacked. If your website serves only the local area, its traffic has always been steady, and it has never felt slow, you can simply skim the decision checklist near the end.
The one-sentence version of what a CDN is
Start with an analogy. Say you run a popular bakery, and your main shop is in downtown Vancouver. Your customers are spread right across Metro Vancouver, but everyone who wants bread has to drive into downtown to your one shop. The ones farther out find it a hassle, and at peak times they queue. So you hit on an idea: open a local branch shop in Burnaby, in Richmond, on the North Shore, and stock each branch with the same bread in advance. From then on, the Burnaby customer collects from the Burnaby branch, the Richmond customer from the Richmond one. Faster, and no crush.
A CDN does exactly this, except the "bread" is the part of your website that can be copied in advance: images, video, page styling, pages that do not change often. A CDN provider keeps data centres in many cities around the world, and those scattered servers are the edge nodes mentioned above. When a visitor opens your site, the system works out roughly where they are and serves the content from the nearest edge node, rather than going back to your one main server every time. Shorter distance, shorter wait. You can also picture it like the pumping stations on a water network: there is only one source (your main server), but with pumping stations placed along the way, the pressure is strongest, and the water arrives fastest, closest to the user.
One distinction to clear up first: a CDN does not replace your website server. The real thing, your software, your database, your admin, always lives on that main server (the industry calls it the "origin"). The CDN simply keeps many extra copies of the parts that can be duplicated, closer to your customers. To understand the main server itself first, see our companion article on what a web server is.
What a CDN actually does for a local small business
Many people hear "global delivery" and assume a CDN only matters to companies selling worldwide. Not so. Of the three benefits below, the first two apply even to a purely local small business; only the third is for some of you and not others.
1. Even local visitors get a faster site
Even if every one of your customers is here in Metro Vancouver, speed is still worth money. Without a CDN, a Richmond customer opening your site sends a request all the way to wherever your main server sits (perhaps Toronto, perhaps the United States), which then sends everything back the same way. That round trip takes time. With a CDN, the images and pages are served from a nearby edge node, the long trip is skipped, and the page snaps into view.
How fast a site loads is not only about experience; it also touches search ranking. Page speed is one of the factors Google considers when it ranks (just one factor, not the deciding one). More to the point, visitors are impatient. If your site is half a beat slow, a customer may leave before they have even seen your content, which means you have quietly turned away someone who was ready to walk in.
2. A buffer when traffic suddenly spikes
This is the use a small business most often underrates, and the one that can matter most. In our companion article on websites under attack we used an analogy: a DDoS attack is like a busy Robson Street suddenly flooded with thousands of people who are not real customers, packing your shop so tightly that the genuine customers who want to buy something cannot get in.
Carry that picture one step further. If you have only one door (one main server), the crowd rushes it, the door jams, and nobody gets in. A CDN is the equivalent of having hundreds or thousands of branch shops all over the place. When the fake crowd arrives, it is dispersed across the edge nodes, each branch taking only a small fraction, and no single one gets jammed shut. That broad front of nodes absorbs and filters the messy traffic first, so only the genuinely clean requests are passed back to your main server, and your real customers can still get into the shop. The principle is simple: there is no single door to jam, so a single surge is far less likely to bring the whole thing down.
One point has to be stated plainly, so the expectation is right: a CDN is not the same as being attack-proof. It is a genuinely useful buffer, not a shield. The sound approach is to run a CDN together with rate limiting (capping how many requests a single source can make in a short window) and a WAF (a web application firewall, which screens out requests that carry an attack intent). It is the layers stacked together that let you talk about "holding up". For a small business, "a useful cushion, not a suit of armour" is exactly the right way to think of it.
That same buffer helps when something good happens suddenly, too: your restaurant gets a local-media write-up, say, or a post unexpectedly takes off, and visitors surge overnight. Without a CDN, the sudden crowd can flatten your main server at the precise moment you most want to catch the business; with one, most people are served from the edge nodes, and the site is far more likely to ride out the wave intact.
3. Only really relevant if you have overseas, China, or Asia customers
This one matters to some of you and not others. If a fair number of your customers are overseas, particularly in China or Asia, then slow cross-border access is a real problem: the data has to travel halfway around the world, so slow loads, and the occasional failure to load at all, are no surprise. In that case, choosing a CDN with edge nodes in the regions you care about makes a marked difference: local customers collect content from a local node, and the experience is much like visiting a local site. Conversely, if your customers are uniformly here in Metro Vancouver, this point means much less for you, which is exactly the "a CDN is only for global businesses" misconception worth correcting.
CDN, website server, name server: how the three divide the work
These three terms get lumped together, but each looks after a different stretch, and once you separate them it is clear:
- The website server (origin): where the real thing lives, software and database and all. It is the "main shop".
- The CDN: copies the duplicable parts of the main shop to branches (edge nodes) around the world, so customers collect locally. It is the "chain of branches".
- The name server: decides where someone is directed to fetch your content once they type in your address. It is the "signpost" at the junction.
How do the three connect? It comes down to that signpost. Putting a site behind a CDN usually involves one specific step: going back to the registrar you bought the domain from and changing the name servers to the set the CDN provides. That way, the first place every visitor in the world is directed to becomes the CDN, which serves them locally and goes back to the origin for the latest parts when it needs to. This step happens at the DNS level, where one small change affects everything, and a misconfiguration can take down the whole site along with the company email, so it is better left to someone who does it regularly. To understand that "signpost", see what a name server is.
When to seriously consider putting a CDN in front of your site
Not every website needs one. Our recommendation: if any of the following is true, it is worth serious consideration.
- Customers report the site is slow to load, especially ones who are out of town or overseas.
- Your business has predictable traffic peaks: holiday sales, a seasonal rush, events, or ad-driven landing pages.
- You worry about attacks, or you have been knocked offline by abnormal traffic before.
- You have a meaningful share of customers overseas, in China, or in Asia.
On the other hand, if you have a purely local, steady-traffic brochure site that has never felt slow, a CDN may not be your most pressing need, and your money and effort might be better spent elsewhere first. This is a judgment to make against your actual situation; there is no one-size-fits-all answer that "every site should have one" or that "having one means you are sorted".
How 5U Website handles this for clients
Whether to use a CDN, which one, and how to fit it to your existing server and DNS, is the kind of call we make day to day. In our years designing, building and hosting websites for Vancouver businesses, our advice has never been "use whatever is fashionable", but rather: who does your site actually serve, does it have traffic peaks, and where are your customers. Where a CDN is warranted, we choose a suitable one for you, set up the edge node caching strategy, and carry out that name server switch carefully, keeping any service interruption to a minimum. Where it is not warranted, we will say so plainly rather than have you pay for something you do not need. Where it makes sense, we also plan the CDN alongside rate limiting and a WAF, so each does its own job.
Let us handle it
A CDN is never a set-and-forget switch. Choosing one, configuring it, fitting it to your DNS, and maintaining it afterwards all take judgment, and getting it wrong can do more harm than good. Our website design, development and hosting service includes assessing, configuring and maintaining a CDN. If you are wrestling with a slow-loading site, worried about attacks, or struggling with poor access for overseas customers, send us an email describing your situation and we usually reply within one to two business days.
Last updated:
