Walkthrough · Intermediate · an hour
How to Connect a CDN
Serve assets from close to your visitors, in the cases where that genuinely pays — a hands-on walkthrough in plain words that names the classic mistake before you reach it.
The short answer
One line covers it: serve assets from close to your visitors, in the cases where that genuinely pays — a intermediate-level job of roughly an hour.
Below is the full run of steps, the error most people trip over, and the short cut worth remembering. On Hosting & Domains plans several steps are already automated away — the guide marks each one.
By the Hosting & Domains team · Reviewed 18 August 2026
Intermediate
Experience required
5
Stages, start to finish
Free
Support included
Proven
On the platform itself
No technical background needed. This walkthrough was written for first-timers, proven on our own hardware, and honest about which parts are genuinely tricky rather than merely unfamiliar.
First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.
The route, mapped end to end
Set out end to end, the route is: check whether you need one, choose the integration style, plug it in, refuse flexible ssl and change your purge habits.
No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.
One caution before you click anything
Flexible SSL on a proxy CDN. The padlock shows while the leg between CDN and origin travels in plaintext, which is a manufactured sense of safety that strict mode exists to replace.
It earns a section of its own because it is no obscure edge case — it is the single commonest reason this task reaches a support queue. Knowing it in advance turns the whole job from risky into routine.
The habit that keeps this easy for good
LiteSpeed and a CDN divide the work neatly: static files off the edge, HTML off the origin cache. Before you keep the CDN, time real visits from where your audience actually is, because a new moving part has to pay rent in milliseconds.
Habits this small are what separate the people who find hosting effortless from the people who find it draining. The same tools on both sides — a different way of working.
What a Hosting & Domains plan spares you
Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.
Should a step still misfire, support answers at any hour with an actual fix rather than a knowledge-base link and a shrug. Half the guides on this site began as repeat patterns in our ticket queue.
The hosting these steps were tested on
Tutorials written against imaginary hosting go stale fast. Ours are written against the real thing: the same panel, installer and defaults waiting in your account.
A free SSL certificate comes with every plan and reissues itself before the old one lapses — the padlock is never yours to diarise.
- Every step checked exactly as published
- The snag named before it arrives
- The dull steps taken out of your way
- People reachable at any hour you stall
Why Hosting & Domains
Standard on every plan
The dull parts automated
SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.
5 steps, nothing padded
Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.
Jargon never charges you
Every term is defined on the spot or linked to the jargon buster — nothing assumes prior knowledge.
Help that keeps your hours, not ours
Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.
Honest about how big it is
Serve assets from close to your visitors, in the cases where that genuinely pays is a intermediate-level job — set aside an hour, with the platform-absorbed steps marked.
Every undo written out
Any step that could bite is marked, together with the exact way to wind it back.
Quick Start
Order placed to site online
- 1
Check whether you need one
Where the audience is local and the hosting is quick, there is almost nothing to gain. An audience spread around the world gains real latency reductions. The CDN decision is geography first and technology second.
- 2
Choose the integration style
Proxy CDNs of the Cloudflare kind take over DNS and filter all traffic. Pull-zone CDNs only rewrite asset URLs. One brings security layers, the other brings simplicity.
- 3
Plug it in
For the proxy route, point your nameservers at the CDN and pick full or strict SSL. For a pull zone, the cache plugin simply swaps asset URLs over to the CDN hostname and there is nothing else to do.
- 4
Refuse flexible SSL
With a proxy CDN, 'flexible' SSL leaves the second half of the journey unencrypted. Only full or strict, encrypted the whole way, belongs on a production site.
- 5
Change your purge habits
CDN hits appear in the response headers, and the purge paths matter now as well. A CDN adds one more cache layer to clear with every published change.
Built In
Fitted to every plan
- Softaculous included for one-click application installs
- Upgrades applied in place, with no migration when you change plan
- Webmail in the browser plus IMAP, POP and SMTP for any client
- PHP versions set per site from the control panel
- Spam and virus screening on every mailbox by default
- NVMe SSD storage on every tier, not only the dear ones
- Mailboxes that answer at the name you hold
- Money back within 30 days on hosting plans, 7 on reseller
- A renewal figure identical to the one you registered at
- People on the support desk every hour of every day
Frequently Asked
The questions that come up most
Is there anything in a CDN for a small site?
Often not. A UK audience on good European hosting sees only a marginal improvement. CDNs prove themselves with geographically scattered visitors, heavy static payloads, or the bundled security layers. Measure first and let the numbers decide.
Ever since the CDN went in, my updates never show up.
The chain has one more cache in it now. After each update, purge the CDN as well as the origin cache. Most integrations can link the two purges, and until then the CDN loyally serves whatever it captured before your edit.
Will you move my existing site free of charge?
Yes. Open a ticket with the login for your current host and we bring the lot across — files, databases, mailboxes, configuration. You check the copy before DNS moves, and the old site keeps taking traffic right up to the moment the new one serves it, so nobody meets a gap.
What does round-the-clock support actually cover?
A reply from a person at any hour, covering the practical jobs: setting up a mailbox, a DNS record, a WordPress fault, a restore. Not 'server is up, closing ticket'. Put a hard question to us before you buy — the answer is a fair sample of what follows.
Keep reading
How to Secure Your Hosting Account
Harden the single account that carries every site you operate — beginner level, about 30 minutes.
How to Set Up an Email Autoresponder
Run out-of-office and acknowledgement replies that stay on their best behaviour — beginner level, about 5 minutes.
CDN (Content Delivery Network) (Glossary)
The plain-English definition this page rests on, with a worked example.
VPS Hosting
KVM virtual servers — root access, DDoS filtering, one flat monthly figure.
WordPress Hosting
WordPress looked after for you — LiteSpeed caching, staging copies and a daily backup.
Changing hosts? Run through our checklist first.
A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.
Your site has earned better hosting.
Every plan carries the essentials other hosts bill as extras — and support that answers.
View VPS Hosting plans