Security and hosting
Do I need a CDN for a small website?
Not usually, if your visitors are near your server and the site is light. A CDN earns its place when your audience is geographically spread, when you serve many images, or when you need DDoS protection and edge rules your host does not offer.
When a CDN genuinely helps
- Customers on another continent from your hosting
- Image-heavy pages, where edge caching removes most of the transfer distance
- Traffic spikes that would otherwise exhaust a shared hosting plan
- A need for security headers, redirects or bot rules your host will not let you set
When it adds complexity for nothing
A local business whose customers are all within one country, on a site of a few hundred kilobytes. The time to first byte improvement is measured in milliseconds nobody notices, and you have added a cache layer to debug when something looks stale.
The prerequisite people miss
You need control of your DNS to put a CDN in front of a site. On a free subdomain where the provider controls the zone, it is simply not available — which is one of the concrete costs of not owning your domain.
The longer version
This answer is deliberately short. If you want the full treatment, Core Web Vitals, and the order that actually reduces them covers it in about 3 minutes — free, ungated, written from client work.
Who answered this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan — fifteen live client sites, six of them stores taking real payments. These answers come from those projects rather than from a content brief. More about how I work, or ask me something directly.