Accounts 
Unmetered traffic on shared hosting: what runs out first
On shared hosting, "unlimited traffic" has long been the norm rather than a selling point. This selection includes around 3,500 plans from nearly 900 hosts, and none of them cap the amount of data transferred. The median price is around $7.70 a month, and the cheapest options start at about $0.40–0.50. So choosing a plan by the "traffic: unlimited" line makes no sense; what matters is figuring out which resource your site will run out of first.
Why traffic is almost never the bottleneck
A typical CMS page weighs 1–3 MB including images, and a good share of those files is cached by the browser. Even 3,000 visitors a day, each opening five pages, add up to roughly 30–50 GB a month. For a host that's trivial: the server's uplink is built for hundreds of accounts at once. Long before traffic becomes noticeable, your site will hit the limits on CPU, memory or concurrent processes.
Serving data is cheap for a host, while computing is expensive. That's exactly why traffic is handed out generously and the real limits are tucked away in other plan parameters.
What hides behind the word "unlimited"
Most hosts isolate accounts with CloudLinux and its LVE mechanism. Each customer gets a "box" with hard limits:
- CPU: a share of a core, typically from 25% up to one or two cores. When you exceed it, processes slow down and pages start taking several seconds to load.
- Memory (PMEM): from 512 MB to a few gigabytes for the whole account. When it runs out, PHP processes crash and visitors see a 503 or 508 error.
- Processes (EP and NPROC): the number of simultaneous entries into PHP. A limit of 20 processes means the twenty-first concurrent request gets an error, no matter how "unlimited" the traffic is.
- IOPS and disk throughput: a cap on input/output operations. Heavy database queries and large catalogs without indexes hit this limit.
- Inodes: the maximum number of files. Cache plugins, thumbnails and mailboxes eat into this limit over time, and eventually the site can no longer save new files.
Beyond the technical limits, the terms of service almost always include a "fair use" clause. It lets the host ask you to move to a higher plan or a VPS if your account puts noticeable load on the shared server. Formally traffic isn't capped, but no host will let you run a file archive off shared hosting.
When traffic volume does matter
There are scenarios where bandwidth really counts:
- Video and audio uploaded straight to your hosting instead of a video platform. A single high-quality clip weighs hundreds of megabytes.
- Downloadable files: software installers, PDF price lists, archives of 3D models, game mods.
- Photo galleries and portfolios with uncompressed original images.
- Sudden spikes after a post in a large Telegram channel or landing in recommendations.
But even in these cases, it isn't traffic that breaks first, it's the process limit: hundreds of simultaneous downloads hold connections open, and new visitors can't get a response. That's why it makes more sense to serve large files from somewhere other than shared hosting.
A CDN and external storage instead of a "fat" pipe
If your site serves a lot of static content, add a CDN. The delivery network caches images, stylesheets and scripts on its own servers closer to visitors, so only HTML requests reach your hosting. The load on your account drops several times over, and pages load faster for visitors in other countries. Many CDNs have a free plan that's enough for a small site.
Video is better uploaded to video platforms and embedded with a player, and large files are better kept in S3 object storage and served via a direct link. Then your hosting serves only the site itself, and LVE limits stop being a problem.
How to tell your site is hitting its limits
The signs are almost always the same: pages occasionally take 5–10 seconds to load, 503 or 508 errors appear during peak hours, and the CMS admin area is slower than the site itself. cPanel and other panels with CloudLinux have a resource usage section showing how many times a day the account hit its CPU, memory or process limits. If you see dozens of hits a day, the problem isn't traffic. Start by enabling page caching, disabling unused plugins and checking whether bots are loading your site: on small sites, search engine and third-party crawlers often generate more requests than real visitors.
How to choose a plan from this list
- Find the CPU, memory and process limits in the plan description. If the host doesn't publish them, ask support before paying.
- Check the disk type. About 35% of plans in this selection use NVMe and the rest SSD; for sites with a large database, filter for NVMe hosting.
- Consider disk size: the median here is 20 GB, which is enough for almost any site that doesn't host its own video.
- Pick a server location close to your audience. For visitors in Russia, hosting in Russia is the logical choice, with minimal latency.
- Check how many sites are allowed. Many cheap plans allow exactly one domain.
If your site consistently hits process and memory limits rather than traffic, the next step is a VPS for websites, where resources are reserved for you instead of being shared with neighbors.