CDN: when a website needs one

A CDN stores copies of a site's files on servers around the world and delivers them to each visitor from the nearest one. This speeds up loading of images, scripts and video and takes load off your server, but it does not make a slow CMS faster and does not replace choosing the right country for your server. Here is when a CDN is really needed and when a single VPS in the right place is enough.

Updated 06.11.2026 · Find a VPS for your needs →

A CDN (content delivery network) is a layer between the visitor and your server. The domain's DNS record points not to the server but to the CDN. The visitor connects to the nearest node of the network, the node serves whatever it has in its cache and fetches everything else from your server, which in this setup is called the origin.

What a CDN does

  • Serves static files close to the visitor. Images, CSS, JavaScript, fonts and video load from a node in the same or a neighbouring country rather than from another continent.
  • Shortens connection setup. The encrypted connection is established with the nearest node. Even in TLS 1.3 the handshake takes a separate round trip (RFC 8446), and with a 150 ms ping to a server on another continent, the connection alone takes about a third of a second.
  • Offloads the server and the network link. If the cache serves 90% of requests, the server gets a tenth of the traffic. This lets you get by with a smaller plan and stay within the traffic limit discussed in the article Bandwidth and traffic: what 1 Gbps and unlimited really mean.
  • Absorbs part of the attacks. There is a separate section on this below.

What a CDN does not do

  • It does not speed up what is not cached. The cart, the user account area, search, the API and pages for logged-in users are requested from the origin every time. If a page takes two seconds to build because of a slow database, it will take the same two seconds with a CDN. What helps here is a more powerful server or optimization; see the article How much RAM and how many cores a website needs.
  • It does not protect a server whose address is known. An attack aimed directly at the origin's IP bypasses the CDN.
  • It does not replace backups. The cache holds only some of the files and only for a while; you cannot restore a site from it.
  • It adds a dependency. A CDN outage or a mistake in its settings takes the site down just like a server failure.

When a server closer to your visitors is enough

If your visitors are in one country or one region, the simplest way to speed up the site is to put the server there too. Every 100 km in a straight line adds about a millisecond to the ping, and a server in the audience's country usually responds within 5–30 ms. Such a site will get only slightly faster with a CDN and is simpler to set up without one. How to choose a location and check the ping before paying is described in the articles How to choose a country for your server and How to test VPS ping and speed before you pay.

A CDN is needed when the audience is spread across continents, when the site has many heavy files (a catalogue with photos, video, downloads) or when traffic comes in peaks: a sale, a newsletter, a press mention. An alternative for an audience in two or three regions is a server in each. According to the accsly.io catalog as of November 2026, VPS plans are available in 96 countries, 400 hosts have servers in five or more countries and 155 in ten or more, so several locations can be rented from a single host. But several servers have to be kept in sync, whereas a CDN caches files from one.

Caching rules

A CDN decides what to store and for how long based on the response headers from your server, first of all Cache-Control (RFC 9111):

  • max-age is how many seconds the response may be stored, and s-maxage is the same but only for CDNs and proxies;
  • private means the response is for one user, so only the browser may store it, not the CDN;
  • no-store means do not store it anywhere.

A working scheme for most sites: files with a version in the name (app.3f2a.css) are served with a one-year max-age and the immutable flag (RFC 8246), and the name changes when the file changes. HTML is cached for minutes or not at all. Pages with a session, a cart or personal data are marked private or no-store.

CDNs also have their own defaults. For example, Cloudflare does not cache HTML and JSON, nor responses with a Set-Cookie header or Cache-Control: private. If you enable caching of all pages with a rule that overrides these headers, the CDN may serve one visitor a page generated for another, complete with that person's name and orders. Enable such a rule only for URLs that definitely contain no personal data.

You can check whether a response came from the cache with curl -I https://example.com/app.css: the Age header shows how many seconds the response has been stored, and the CDN reports the cache status in its own header, whose name you will find in its documentation.

CDN and DDoS protection

Large CDNs have network capacity and node counts orders of magnitude greater than a single data centre, so volumetric attacks are spread across the network and do not reach your server. Application-layer attacks are filtered by the CDN with rules: request rate limiting, browser checks, blocking by country or address. This complements the host's protection rather than replacing it: according to the accsly.io catalog as of November 2026, 1,123 of 2,243 hosts with VPS plans state that they offer DDoS protection, and it is usually network-layer filtering. What actually lies behind such a line in a plan is explained in the article DDoS protection: what hosting providers actually give you; plans that include it are collected in VPS with DDoS protection.

Protection through a CDN only works as long as the origin's address is unknown. On the server, allow incoming connections to ports 80 and 443 only from the CDN's address ranges, which every provider publishes. Do not keep mail and other services on the same IP as the site: MX records and email headers reveal the address. After connecting a CDN, change the server's IP if the old one was already in public DNS records, since their history is kept in open databases.

What it costs

The price of a CDN is made up of transferred traffic, the number of requests and additional features. There are three models:

Application protection (WAF), image optimization, log storage and dedicated addresses are paid for separately. Before connecting a CDN, compare its price with the cost of traffic at your host: if the server already includes several terabytes a month and the audience is nearby, you do not need a CDN to save on traffic.

How to connect a CDN without breaking the site

  1. Choose the setup. You can hand the CDN the domain's entire zone by changing the DNS servers at the registrar, or route only a subdomain for static files through the CDN with a CNAME record, for example static.example.com. The second option is easier to undo. How these records work is explained in the article Domains and DNS for a server owner.
  2. Set up encryption to the origin. The connection between the CDN and the server must also use HTTPS with certificate verification. A mode in which the CDN connects to the server over HTTP leaves traffic unencrypted on that leg. Certificates are covered in the article SSL certificates: free and paid.
  3. Pass the visitor's real IP to the server. Otherwise logs, rate limits and fail2ban will see only the CDN's addresses. The CDN passes the address in a header, and the web server has to be configured to trust it only from the CDN's addresses.
  4. Check the nodes for your audience. Look at the CDN's node map and measure latency from the regions where your visitors are, especially from the countries where most of your audience is. A CDN without nodes near your audience can turn out slower than direct access to the server.

FAQ

Does a small website need a CDN?

If the visitors are in one country and the server is there too, usually not: the speed gain will be small. A CDN is useful when the audience is spread across continents, when there are many images and videos or when there are traffic peaks.

Does a CDN speed up dynamic pages?

Hardly at all: the cart, the user account area and the API are requested from your server every time. A CDN only shortens connection setup, while page build time depends on the server and the CMS.

Does a CDN protect against DDoS attacks?

Yes, if the server's address is hidden: the CDN spreads volumetric attacks across its network and filters requests to the application. If the server's IP is known, the attack will go straight to it, so the server should accept web traffic only from the CDN's addresses.

How much does a CDN cost?

A free plan is often enough for small sites. With pay-per-traffic pricing, the price in Europe and North America starts at about one cent per gigabyte and is several times higher in other regions. WAF and image optimization cost extra.

Which is better: a CDN or a server closer to visitors?

If the audience is in one region, a server in that region is simpler and cheaper. If visitors are all over the world or the site serves many heavy files, you need a CDN, and the server is placed where most of the audience is.

Why does the site show an old version after connecting a CDN?

The CDN serves the cached copy until it expires. Purge the cache in the CDN panel or use files with a version in the name, and set a short max-age for HTML.

Plans on this topic

VPS for an online storeVPS for a websiteVPS for WordPressVPS/VDS with unlimited trafficVPS with a 1 Gbps portWeb hosting with unlimited traffic

More in the guide

  • Domains and DNS for a server ownerYou can switch servers in an evening, but a domain stays with a project for years. Through DNS, the domain points to your server, your mail and third-party services, and a single wrong record can take the site offline or send your emails to spam. Here are the records a VPS owner will need, how caching works, where to keep the zone and how to move to a new server without visitors noticing.
  • SSL certificates: free and paidA free certificate encrypts the connection just as reliably as a paid one: browsers make no distinction between them in terms of security. The difference lies in what the certificate authority checks, how long the certificate lasts and who is responsible for renewing it. According to the accsly.io catalog as of November 2026, free SSL is explicitly listed in 1,449 shared hosting plans from 178 hosts. Here is when that is enough and when a certificate is worth paying for.
  • 152-FZ and hosting: where to store the dataIf a website or service collects personal data of Russian citizens, that data must be recorded and stored in databases located in Russia: this is Part 5 of Article 18 of Federal Law No. 152-FZ. For choosing a VPS, this means the data centre's country matters, not the host's, and copies abroad fall under separate rules. Here is what the law requires, what duties fall on the server owner, how it applies to companies outside Russia and which setups are used in practice.
  • GDPR and choosing a hostThe EU General Data Protection Regulation (GDPR) does not require data to be kept in the EU, but it does require a data processing agreement with the host and a lawful mechanism for any transfer of data out of the EU. According to the accsly.io catalog as of November 2026, 61% of VPS hosts have servers in the EU, but almost half of them are registered outside the European Economic Area. Here is why that matters and what to check in the terms.
  • Hosting provider jurisdiction: what it affectsEvery server has two countries: the one where the data centre stands and the one where the company renting it out is registered. According to the accsly.io catalog as of November 2026, these are different countries for 15% of VPS hosts. The first determines latency and the rules on where data is stored; the second determines the law of the contract, the court for disputes, the documents your accountant receives and whose authorities can request your data. Here is what each of them changes.
  • How to compare VPS prices: the price of a resource unitA plan's price tells you how much you will pay, but not how much you get for that money. According to the accsly.io catalog as of November 2026, a gigabyte of memory on a 1 GB plan costs a median $8.00 a month, while on a 4 GB plan it costs $5.00. Here is how to work out the price per vCPU, per gigabyte of memory and of disk, and what to bring to a common basis before you compare two offers.
  • SLA and uptime: what hosts promiseAn SLA of 99.9% allows a host 43 minutes of downtime a month, 99.99% about four. But a percentage in an advert is not yet a commitment: the commitment is the document that says what counts as downtime, what is excluded and how much you get back. Most often that is a discount on the next invoice, not money. Here is how to read such documents and how to check availability yourself.
  • Free trials and money-back guaranteesThere are two ways to test a server before paying for a month or a year: a free trial or a money-back guarantee. According to the accsly.io catalog as of November 2026, 11% of VPS hosts offer a trial and 36% a money-back guarantee. But at many of them the terms apply only to shared hosting, only to the first order or only to card payments. Here is what to check so that the guarantee actually works.
  • Cloud server or VPSA cloud server and a VPS are usually the same KVM virtual machine. The difference lies in what surrounds it: a cloud sells resources by the hour through an API and offers network disks, snapshots and ready-made services, while a classic VPS is a fixed monthly plan with a local disk and a traffic allowance. Here is which of this you actually need and what it costs.
  • Dedicated server or VPSA VPS is a slice of a physical server, a dedicated server is the whole machine. With 4 cores and 8–16 GB of memory a VPS costs almost half as much, with 4 cores and 32 GB the prices are equal, and with 64 GB on 8 cores or 128 GB on 16 cores a dedicated server in the catalog is a third cheaper than a virtual one. Here is what else changes besides the price: neighbours, guarantees, delivery time, hardware failures and remote management.
  • Shared hosting or VPS for a websiteShared hosting is a ready place for a site where the host looks after the server. A VPS is your own server where you set everything up. For a landing page or an ordinary WordPress site, hosting is enough and costs several times less. You need a VPS when the account limits are too tight for the site or when it needs software that hosting does not allow. Below is what each option includes, what it costs and a table to help you choose.
  • DDoS protection: what hosting providers actually give youEvery second host now lists "DDoS protection" in its plans. Behind that line there may be multi-terabit filtering, or only the right to take your address offline when an attack bothers the neighbours. Here is what protection is made of, how L3/L4 differs from L7, and how to tell from the contract what you are buying.
  • Mail server on a VPS: SPF, DKIM, DMARCInstalling Postfix or a ready-made bundle like Mailcow on a VPS takes an hour. Getting your mail into the inbox rather than spam is harder: mailbox providers look at the port, the server's address, its reputation and three DNS records. Here is what to check with the host before buying and how to set up SPF, DKIM and DMARC.
  • Server monitoring: uptime, load, alertsWithout monitoring you learn that the server is down from your visitors, and that the disk is running out when the database stops writing. A few checks from outside and a dozen metrics from inside are enough to see a problem before users do. Here is what to measure, where to run checks and how to do it for free.
  • How to read hosting plans: the hidden limitsA plan card shows cores, memory, disk and a monthly price. Yet two plans with identical numbers can cost different amounts a year later and behave differently under load. The difference lies in terms printed in small type, in the acceptable use policy, or only in the contract. Below are eight places worth checking before you pay.
  • IPv4 and IPv6 on a serverA typical VPS has one public IPv4 address and, if the host supports it, an IPv6 subnet. An extra IPv4 address almost always costs money, and the cheapest plans sometimes come without their own IPv4 at all. Here is where the shortage comes from, what you can do with IPv6 alone and which address settings a mail server needs.
  • Bandwidth and traffic: what 1 Gbps and unlimited really meanA server plan usually has two network lines: port speed and traffic volume. The first says how fast the server can send data, the second how much it can send in a month. They are linked by simple arithmetic, and once you know it, it is easy to see what "1 Gbps unlimited" actually offers and whether "5 TB" will be enough for you.
  • Docker on a VPS: getting startedDocker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.
  • How to move a website from shared hosting to a VPSThe move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.
  • Server control panels: ISPmanager, FASTPANEL, aaPanelA panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.
  • Windows VPS for 1CA rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
  • Windows VPS: licensing, RDP and secure sign-inA Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.
  • When to move from shared hosting to a VPSA VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.
  • VPS backups: strategies and toolsOn a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.
  • First 10 steps after buying a VPS: securityBots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.
  • How to choose a country for your serverPut the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
  • Hourly billing: when it pays offHourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.
  • How much RAM and how many cores a website needsMost websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.
  • KVM or OpenVZ: which to chooseIn 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.
  • NVMe or SSD: does it matter for a websiteFor a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.
  • What is a VPS, in plain EnglishA VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.
  • VPS for a Telegram bot: what the bot needs and how to pick a planA bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.
  • How to test VPS ping and speed before you payThe numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.
  • Corporate network on a VPS: remote access to the officeA rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.
  • How to choose a VPS: the 7 specs that matterTwo plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.
  • VPS vs VDS: is there a difference and what actually mattersIn most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.