Bandwidth Calculator — How Much Does Your Website Need, and Which Plan Carries It
A site with 35,000 monthly visits, 2 pageviews per visit and 2 MB pages moves 35,000 × 2 × 2 = 140,000 MB ÷ 1,024 ≈ 136.7 GB raw — and LiteSpeed/CDN caching divides that by 2-4 (modeled ÷3) to about 45.6 GB/mo, a need a 2026 shared plan carries comfortably. Peak hour is no threat either: 35,000 ÷ 30 × 5% ≈ 58 concurrent sessions → 116 pageviews ≈ 0.52 Mbps average — a 1Gbps port carries this hundreds of times over. Tier verdict: shared fits; past 50 GB/mo a CDN becomes mandatory to absorb bursts, past 150 GB/mo you are in cloud/VPS territory — and "unlimited bandwidth" is limited by port speed and fair-use clauses, not by gigabytes.
| visits/mo | pages | type | caching | GB/mo | tier |
|---|---|---|---|---|---|
| 5,000 | 2 | Light blog | ÷3 | 2.6 | Shared |
| 10,000 | 2 | Standard site | ÷3 | 13.0 | Shared |
| 35,000 | 2 | Standard site | ÷3 | 45.6 | Shared |
| 35,000 | 2 | Standard site | off | 136.7 | Cloud + CDN |
| 50,000 | 3 | E-commerce | ÷3 | 146.5 | Cloud + CDN |
| 60,000 | 4 | Image-heavy | ÷3 | 312.5 | Cloud/VPS + CDN |
| 100,000 | 5 | Image-heavy | ÷3 | 651.0 | Cloud/VPS + CDN |
| Verdict | Cache first, then size the tier: LiteSpeed/CDN caching divides raw transfer by 2-4 and usually lands you a full tier below what raw traffic suggests — and "unlimited bandwidth" caps the port speed, not the gigabytes. | ||||
Bandwidth Calculator — How Much Does Your Website Need, and Which Plan Carries It
Inputs
Monthly pageviews: 70,000 (35,000 visits × 2 pages)
Blogs usually 1-2, business sites 2-3, stores 3-5.
Standard site · 1.5-2.5 MB: The typical small-business or content site — 1.5-2.5 MB per pageview in 2026; we model 2.0 MB.
LiteSpeed page cache plus a CDN typically serve over half of requests from edge or page cache, so raw transfer divides by 2-4 — we model ÷3. Cache misses (logged-in carts, search, checkout, first visits) set the floor; nothing divides to zero.
Caching is doing the heavy lifting: raw ≈136.7 GB drops to ≈45.6 GB (÷3) — the difference between a cloud bill and a shared plan that fits comfortably. At this size "unlimited bandwidth" is no trap: the port, not the GB, is the limit.
Cache first, then size the tier: LiteSpeed/CDN caching divides raw transfer by 2-4 and usually lands you a full tier below what raw traffic suggests — and "unlimited bandwidth" caps the port speed, not the gigabytes.
"Unlimited" plans are measured by their port (a shared 1Gbps) and a fair-use clause — not by a GB allowance. Peak-hour math: daily sessions ≈ visits ÷ 30; the busiest hour concentrates 4-6% of them (we model 5%). A 1Gbps port moves ~125 MB/s — hundreds of times a normal hour's average. What the port actually limits is cache-miss bursts (20-50× the average) and viral spikes, which is why a CDN becomes mandatory past ~50 GB/mo rather than a bigger GB allowance.
Methodology: deterministic planning bands from published 2026 medians — page weights (light 0.8 MB, standard 1.5-2.5 modeled 2.0, e-commerce 3, image-heavy 4), caching ÷2-4 from real LiteSpeed/CDN hit rates (modeled ÷3), and a 4-6% peak-hour share of daily sessions. Not live measurements: read your actual GB from the hosting panel monthly and recalibrate.
| visits/mo | pages | type | caching | GB/mo | tier |
|---|---|---|---|---|---|
| 5,000 | 2 | Light blog | ÷3 | 2.6 | Shared |
| 10,000 | 2 | Standard site | ÷3 | 13.0 | Shared |
| 35,000 | 2 | Standard site | ÷3 | 45.6 | Shared |
| 35,000 | 2 | Standard site | off | 136.7 | Cloud + CDN |
| 50,000 | 3 | E-commerce | ÷3 | 146.5 | Cloud + CDN |
| 60,000 | 4 | Image-heavy | ÷3 | 312.5 | Cloud/VPS + CDN |
| 100,000 | 5 | Image-heavy | ÷3 | 651.0 | Cloud/VPS + CDN |
Results
Embed This Calculator
Share this tool with your audience. 100% free and fully responsive.
How the bandwidth & plan-tier calculator works
Why this calculator is honest about its numbers: it uses deterministic 2026 planning bands — page weights from published medians (light 0.8 MB, standard 1.5-2.5 modeled 2.0, e-commerce 3, image-heavy 4), a ÷2-4 caching factor from real-world LiteSpeed/CDN hit rates (modeled ÷3), and a 4-6% peak-hour share of daily sessions. Every figure can be re-derived by hand from the formula under the result, nothing is fetched live — and the real calibration is your hosting panel's monthly GB reading.
- 1
Step 1
Enter monthly visits (typed or via common-value chips) and pageviews per visit on the slider (1-10) — multiplied by your page type's weight: light blog 0.8 MB, standard 2 MB, e-commerce 3 MB, image-heavy 4 MB.
- 2
Step 2
Toggle caching: on, raw transfer divides by 2-4 (modeled ÷3) as LiteSpeed/CDN hit-rate reality — the monthly GB appears with the raw and cached figures side by side.
- 3
Step 3
Read the full output: the peak-hour estimate (visits ÷ 30 × 5% × pages, in Mbps), the matching tier (shared to 50 GB, cloud+CDN to 150, cloud/VPS beyond), the common-cases table, the caching verdict and the "unlimited" fine print.
Use Cases
A blogger choosing a first hosting plan: 10-40k monthly visits on 0.8-2 MB pages — the calculator shows 10-50 GB after caching makes an "unlimited" shared plan genuinely right, and pins the upgrade point (~50 GB) before any unneeded tier is bought.
A WooCommerce owner torn between shared and cloud: 50,000 visits × 3 pages × 3 MB = 439 GB raw — caching brings it to ~146 GB, cloud-tier territory, and the calculator shows the CDN has become mandatory, not optional, at this size.
An agency or freelancer auditing client sites before renewal: enter each site's visits and weight to get a tier table — who approaches ~50 GB and needs a CDN this month, and who is past 150 GB and needs a cloud/VPS plan rather than "more bandwidth" on the same tier.
Tips
- 1
Page weight is a ranking metric before it is a bill: Google scores LCP and INP on the same megabytes this calculator counts — a 4 MB page loses Core Web Vitals and bandwidth together, and converting images to WebP/AVIF fixes both in one step.
- 2
Caching and a CDN improve TTFB for visitors far from the server: a Gulf visitor gets content from a nearby edge node instead of a trip across oceans — faster loads that feed directly into crawl rate and rankings.
- 3
Compare your actual monthly GB from the hosting panel against this estimate: a wide gap means uncompressed images or bot crawl — crawlers and scrapers eat bandwidth with zero SEO value, and robots.txt rules cut them off when needed.
Common Mistakes
Treating "unlimited" as a guarantee: the real limits are port speed and the fair-use clause — hosting video or large files gets throttled or suspended even on unlimited plans, while a normal text site never approaches the cap.
Counting visits alone instead of pageviews × weight: 30k visitors on an image-heavy site (4 MB × 4 pages) consumes more than 120k visitors on a light blog — demand is measured in transferred megabytes, not headcount.
Forgetting spike months: a product launch or viral hit multiplies traffic 5-20× within days — plan with 2-3× headroom over your monthly estimate and let the CDN absorb the burst instead of your site being throttled in its biggest week.
FAQs
How do I calculate the bandwidth my website needs per month?
What does 100 GB of bandwidth mean in actual visits?
Does "unlimited bandwidth" hosting actually exist?
How does a CDN change the bandwidth math?
Which page-weight reductions save the most bandwidth?
Should I self-host video on my hosting plan?
How does peak-hour math work — and does it change my plan?
What happens when I exceed my bandwidth limit in 2026?
Related tools
Pick another tool to continue your calculation.