What Is a CDN, and Does a Small Business Website Need One?
Learn what a CDN does, which website content it can cache, and how to decide whether your small business needs one.
Part of our guide: The Complete Guide to Website Speed for Business Owners
A content delivery network, or CDN, serves eligible website content through a distributed network rather than making every visitor fetch everything from one hosting location. It can improve delivery, particularly for visitors far from the original server. It is not a substitute for a well-built page or dependable hosting.
Many website platforms already include a CDN. Before buying another service, ask what your current setup provides and which problem you are trying to solve.
What changes when a website uses a CDN?
Your main server is often called the origin. A CDN can keep reusable copies of files nearer visitors and deliver those copies when requested. Not every request is necessarily cached: eligibility, expiry and configuration determine what happens. Cloudflare’s CDN explanation describes this relationship between the origin and distributed delivery.
Think of a business supplying several branches. Keeping commonly needed materials at each branch can avoid repeated trips to the main store. But the branches still need a reliable way to receive updated materials.
When a price changes or a customer signs in, the CDN needs to return the correct information as well as deliver it quickly.
Which content could benefit?
Start with a content inventory rather than a provider comparison.
| Content | Question to ask |
|---|---|
| Public photographs and illustrations | Are these already delivered through an image service or CDN? |
| Stylesheets and scripts | Do filenames change when their contents change? |
| Public information pages | Can these be cached safely, and how are edits refreshed? |
| Account, basket or personalised pages | What prevents one visitor receiving another visitor’s content? |
| Form submissions | Are these handled correctly without inappropriate response caching? |
A developer should explain the rules for your actual platform. “The CDN is switched on” is not evidence that every page is faster or safe to cache.
Our guide to website caching explains the different layers that can hold a copy.
A small-business decision tree
Use these questions in order.
- Does the platform already provide a CDN? If yes, understand and test that configuration before adding another layer.
- Are visitors geographically distant from the hosting location? If yes, compare performance from representative places.
- Are large public assets repeatedly downloaded? If yes, check image sizing and caching as well as delivery distance.
- Is the main delay caused by server processing? Investigate time to first byte rather than assuming distribution alone will fix it.
- Is the page sluggish after it appears? Review scripts and interactions; a CDN cannot remove unnecessary work running in the browser.
- Can someone own configuration and troubleshooting? Include that responsibility in the decision.
For a local service website already served efficiently by its platform, another paid CDN may add little. For an image-heavy site with customers in several countries, a measured trial may be worthwhile.
Test the improvement you actually need
Choose a small set of representative pages: homepage, main service page and a page with substantial imagery. Record the location, device, network conditions and whether the cache was warm.
Compare repeated runs rather than selecting the best score. Check that forms, redirects, consent controls and edited content still work. A faster homepage does not compensate for an enquiry form that has stopped submitting.
Ask for a short before-and-after report with the same conditions and a clear explanation of what changed. The broader website speed guide helps separate delivery problems from page-design problems.
Agree who handles failures and updates
Record who controls the CDN account, billing, DNS connection and recovery settings. Keep this alongside your hosting ownership information.
Ask how to refresh a changed file, how to bypass caching during diagnosis and how to return to a known working configuration. Avoid making overlapping changes to hosting, DNS and delivery rules without a rollback plan.
A CDN can reduce repeated origin requests, but do not turn that into an unsupported environmental claim. Our sustainable website guide explains why performance improvements and carbon estimates need different evidence.
Check whether a CDN is worth adding
Check whether the CDN improves the delivery problem you measured and agree who will maintain it. If you cannot yet do either, establish the baseline before buying more infrastructure.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
