A CDN for a Business in One City

What a content network is for

The original purpose is distance. Copies of your files are held on machines around the world, and a visitor is served from a nearby one rather than from your server.

For a site whose visitors are spread across continents, that removes a real delay on every request.

For a plumber whose customers are all within a thirty-minute drive, the visitor and the server are already close, and the distance benefit is close to zero.

Which is where the usual sales pitch stops making sense, and where the more interesting question starts.

What still applies locally

Several things, and they are not the ones the marketing leads with.

• Caching, so your server handles far fewer requests.
• Compression, often better configured than on your host.
• Modern connection handling, which many cheap hosts lack.
• Image conversion to lighter formats, on some plans.
• Protection against floods of malicious traffic.
• Staying up when your server does not, for cached pages.

The first is the substantial one for a small business, because it changes how much work your hosting has to do rather than how far the data travels.

Caching is the real benefit

Worth separating from the distance argument entirely.

A network sitting in front of your site can serve cached copies of your pages and images without touching your server at all.

For a small site on modest hosting, that removes most of the load, which matters on a shared plan where you are competing with neighbours for the machine.

It also means a burst of traffic, from a local news mention or a busy day, is absorbed rather than taking the site down.

That is a genuine benefit for a business in one city, and it has nothing to do with geography.

The protection argument

Frequently the strongest reason for a small business, and the one least discussed.

Every site receives automated traffic looking for weaknesses, regardless of size or obscurity, and a small site on shared hosting can be knocked over by a fairly modest flood.

A network in front absorbs that before it reaches your server.

It also blocks a proportion of nuisance traffic, which reduces load and cleans up your analytics as a side effect.

For a business whose site is its phone book entry, staying reachable is worth more than a fraction of a second on load time.

The free tier changes the calculation

Several providers offer a level that covers caching, compression, and basic protection at no cost.

At that price the question is not whether the benefit exceeds the cost, since there is no cost.

The question is whether the added complexity is worth it, and that is a real consideration rather than a formality.

Adding a network means another system between your visitors and your site, another account somebody has to control, and another place to look when something breaks.

For a business with nobody technical, that is a genuine cost even when the invoice is zero.

A worked example

A local trades business was told a content network would make their site substantially faster.

Their customers were entirely within one region and their server was in the same province, so the distance benefit was negligible.

They enabled a free tier anyway, mainly for the caching.

Load time improved by a small amount, well under a second, which was not what anybody had been promised.

What did change was that a busy week following local radio coverage, which had taken the site down the previous year, passed without any interruption at all.

Their assessment was that they had bought insurance rather than speed, and that the insurance was the part they needed.

What it will not fix

Important, because it is sold as a general remedy and is not one.

It does not make oversized images smaller in any meaningful sense on a basic plan, and a four megabyte photograph delivered from a nearby machine is still four megabytes.

It does not fix a slow database, since anything not cacheable still goes to your server.

It does not fix a page that shows nothing for six seconds because of blocking scripts.

And it will not rescue a site whose real problem is that nobody can tell what the business does.

If your homepage is heavy and badly ordered, fix that first, because a network in front of a bad page delivers a bad page efficiently.

The things that go wrong

Worth knowing before enabling anything, since these produce most of the bad experiences.

Caching applied to pages that should not be cached, such as a basket or a logged-in area, which shows one customer another customer's page.

Changes to the site not appearing, because the old version is still cached and nobody knows how to clear it.

Certificate confusion during setup, producing browser warnings for a period.

And aggressive optimisation options that combine or rewrite files, which break sites in the same way overzealous performance plugins do.

Enable the basic level, confirm the site works properly, and leave the optimisation switches alone unless somebody is testing after each one.

The counter-case

Plenty of local businesses should not bother.

A small site on decent hosting, already fast, with modest traffic and no history of outages, gains very little and adds a system to its stack.

There is also a real risk in adding infrastructure nobody in the business understands, since the person who set it up may not be around when a problem appears, and diagnosing a site through a layer you did not know existed is genuinely difficult.

The clearest cases for enabling one are a site that has gone down under traffic, a site on struggling shared hosting, or a business with any national or seasonal audience at all.

Absent those, it is optional, and saying so is more honest than the usual recommendation.

Deciding

1. Check where your visitors are in your analytics.
2. Check where your server is relative to them.
3. Fix heavy pages first, since a network will not fix them.
4. Consider it for caching and protection, not distance.
5. Start with a free tier and basic settings.
6. Exclude baskets and logins from caching.
7. Write down who controls the account.

Step seven matters more than it appears, since a network nobody can log into is a problem waiting for a bad week.

What caching actually does is covered in caching explained without the jargon.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.