Bandwidth Calculator — Website Traffic & Hosting

Monthly visitors

Avg page size

Unit

Page views / visit

Monthly bandwidth

Yearly (with margin, add ~50%)

Share X / Twitter Facebook LinkedIn WhatsApp

How to use Bandwidth Calculator

Enter monthly visitors — from analytics, or your traffic goal.
Enter pages per visit and average page size — DevTools' Network tab measures a real page load.
Read monthly/yearly GB — then add ~50% headroom for spikes, bots and downloads.
Compare against hosting plans — and note a CDN can offload 60–90% of it.

What is Bandwidth Calculator?

A bandwidth calculator estimates the data a website serves per month: visitors × page views per visit × average page size. 10,000 monthly visitors viewing 3 pages of 2 MB each transfer 10,000 × 3 × 2 MB ≈ 59 GB/month — the number hosting plans meter and cap.

It's the right-sizing tool for hosting decisions: too small a plan throttles or bills overages exactly when traffic spikes (success becomes an outage); wildly oversized plans waste money. The missing ingredient in naive math is headroom — spikes, bots and file downloads — which is why the standard practice adds ~50%.

About the Bandwidth Calculator

Enter monthly visitors, pages per visit and average page size (KB or MB), and read the monthly and yearly bandwidth — then add the ~50% margin the yearly figure hints at before choosing a plan.

Getting the inputs honest: average page size comes from your speed test or DevTools' Network tab (media-heavy pages run 2–5 MB; lean pages under 1 MB); pages-per-visit from analytics (2–4 is typical). Remember non-page traffic: file downloads (each PDF or video download is its full size), API calls, and bot/crawler traffic that analytics undercounts but servers still serve — heavier than expected on content sites.

Context that changes the answer: a CDN (Cloudflare et al.) serves cached assets from its own network, offloading commonly 60–90% of origin bandwidth — the reason modest hosting plans survive big traffic. And "unmetered" shared hosting still enforces fair-use CPU/IO limits, so the calculation stays relevant even without a hard GB cap.

Frequently Asked Questions

Small sites (1–5k visitors/month): 5–30 GB. Mid-size blogs (10–50k): 60–300 GB. Anything serving video or downloads: multiples of that. Page weight × traffic — both levers matter equally.

Open DevTools → Network, load the page fresh (cache disabled), read the "transferred" total. Test your heaviest templates too — a media-rich article can weigh 5× your homepage.

The usual suspects: bots and crawlers (invisible to JS analytics but served by the host), hotlinked images serving on other sites' pages, file downloads counted at full size, and traffic spikes concentrating a month's budget into a day.

Commonly 60–90% — the CDN's edge serves cached images, CSS and JS from its own network, and your host only sees cache misses and dynamic requests. It's the single biggest lever for outgrowing a small plan slowly.

Marketing shorthand for "unmetered with fair-use limits" — shared hosts enforce CPU, memory and IO caps instead, and throttle sites that hog them. Your realistic ceiling is those resources, not a GB number.