What is a CDN?
A group of servers in many locations that hold copies of your content and answer requests from the copy nearest the visitor. MDN’s glossary puts it as a group of servers spread out over many locations that store duplicate copies of data so that servers can fulfill data requests based on which servers are closest to the respective end-users, and notes that geographical distance affects latency proportionally. A visitor in Sydney asking for an image on a server in Frankfurt waits for the round trip across the planet; with a CDN, the image comes from Sydney, and only the first request for it ever crossed the planet.
What does it cache?
Static files first: images, stylesheets, scripts, fonts. These make up most of the bytes on a page and never change between visitors, so they cache well. Many CDNs also cache whole HTML pages for anonymous visitors, which is where the big gains are for a blog or a brochure site, and most can be told not to cache pages that differ per visitor, such as a cart or a logged-in dashboard.
What it cannot cache is anything the server has to compute fresh for each visitor. Those requests still travel to the origin, and the CDN adds one hop on the way.
When does it help?
When your visitors are far from your server. A site hosted in a US data center with readers in Europe and Asia will see first-byte and load times fall for those readers once pages and assets are served from edge locations near them. When your visitors are in the same region as your server, the gain is smaller: the origin is already close, and a well-cached shared plan responds in a few hundred milliseconds on its own. Our TTFB article explains why distance is such a large part of that number.
The second benefit is absorbing traffic. A spike from a newsletter or a social post hits the cache, not your shared plan’s CPU allocation, and the CDN serves the same page thousands of times without the origin noticing. For a shared plan with published limits, that is often the more valuable effect.
When do you not need one?
When your audience is local and your site is already cached at the origin. A small business site in Toronto on a Toronto server, with LiteSpeed caching in front of WordPress, gains little from a CDN and adds a layer to debug. Likewise a store where most requests are carts and checkouts, which bypass the cache anyway. And a CDN is not a fix for a slow site: if the origin takes two seconds to build a page, the first visitor at each edge location still waits two seconds, and so does everyone on uncached pages.
Which hosts include one?
From the plan pages we read on 13 October 2026: SiteGround includes its own CDN on Google Cloud on every plan; Bluehost, HostPapa, and Flashcloud (Cloudflare) include a CDN; Hostinger includes it on Unlimited and Cloud Startup and lists it as available on Premium; ScalaHosting lists CDN integration. FastComet, Hosting.com and InMotion do not list one on their shared plan cards. Cloudflare’s free tier sits in front of any host by changing your nameservers, which is how many sites on the last three use one.