How monthly bandwidth is estimated
The base calculation is straightforward:
bandwidth = visitors × pages per visit × page weight
50,000 visitors viewing 3 pages of 1,800 KB each gives 270,000,000 KB, or about 270 GB per month.
Two adjustments make the estimate realistic. Caching reduces it, because returning visitors and second page views reuse assets already in the browser cache. Headroom raises it, because traffic spikes, bots, and growth all consume capacity that an average-case calculation misses.
Page weight is usually the problem
The median web page is now well over 2 MB, and images typically account for more than half of it. That is where the leverage sits.
Modern image formats. WebP is typically 25–35% smaller than equivalent JPEG, and AVIF often 50% smaller. Both have broad browser support, and the <picture> element handles fallbacks cleanly.
Correct sizing. Serving a 3000px image into a 400px slot wastes most of the bytes. The srcset attribute lets the browser choose an appropriate file.
Lazy loading. Adding loading="lazy" to below-the-fold images means they are never fetched unless the user scrolls.
Compression. Brotli or gzip typically reduces HTML, CSS, and JavaScript by 70–80%. This should be on by default and frequently is not.
What a CDN changes
A content delivery network caches your static assets at locations close to users. The effects on bandwidth are twofold.
Your origin bandwidth drops substantially — often by 80–95% — because the CDN serves most requests without contacting your server. If your host charges for origin transfer, this is a direct saving.
Your total bandwidth does not fall; it moves to the CDN, which has its own pricing. The saving comes from CDN rates typically being lower than origin hosting rates, plus reduced server load.
The other benefit is latency. Serving from a nearby edge location is faster for the user regardless of bandwidth economics.
What the calculation misses
Real bandwidth usually exceeds a naive estimate for reasons that are easy to overlook:
- Bots and crawlers can be 20–40% of requests on a public site, and they do not cache.
- API calls from single-page applications are not page views but do consume transfer.
- Video and large downloads dwarf page weight if you host them yourself.
- Failed and abandoned requests still transfer partial data.
- Uploads from users count toward transfer on most hosts.
- Traffic spikes. A month's average tells you nothing about the day a post is shared widely.
Choosing a plan
“Unlimited bandwidth” shared hosting is not unlimited — the acceptable use policy will contain limits, and exceeding them typically means throttling or a forced upgrade. It is a marketing term rather than a technical one.
Metered plans are more honest but need headroom. Overage charges are usually punitive relative to the base rate, so sizing at roughly double your expected usage is a reasonable default.
For most content sites, a CDN in front of modest origin hosting is both cheaper and faster than a large hosting plan. And before buying more bandwidth, it is worth spending an hour on image optimisation — halving page weight halves the bill.
Frequently asked questions
How much bandwidth does a website need?
Multiply monthly visitors by pages per visit by average page weight, then adjust down for caching and up for growth and bots. A site with 50,000 visitors at 3 pages of 1.8 MB uses roughly 270 GB before adjustments.
Does a CDN reduce my bandwidth costs?
It reduces origin bandwidth substantially, often by 80-95%, and moves the rest to the CDN's typically cheaper rates. Total bytes transferred stay similar, but cost and latency both usually fall.
Is unlimited bandwidth hosting really unlimited?
No. The acceptable use policy will contain limits, and exceeding them typically results in throttling or a forced upgrade. It is a marketing term rather than a technical guarantee.
What is the easiest way to reduce bandwidth?
Optimise images. They are typically over half of page weight, and switching to WebP or AVIF with correct sizing and lazy loading often halves total transfer.