Bandwidth is the line item budget VPS buyers misjudge most often in both directions. Some overbuy a 10 TB allowance they never approach, paying $20 per month for headroom they will not use. Others pick a 1 TB plan for a site that serves image-heavy pages and discover overage the month a post gets shared. This guide gives you a measured way to estimate the transfer your small VPS actually needs, then maps that figure to real plan allowances.
The core principle is simple: bandwidth is a product of page weight, page views, and a repeat-visitor factor. Inbound traffic is free at virtually every provider, so only egress counts. Get those three numbers roughly right and you can size a plan within one billing tier instead of guessing.
Measure Page Weight Before You Guess
Page weight is the total bytes a browser downloads to render one page: HTML, CSS, JavaScript, fonts, and images. A lean static page is 200-400 KB. A typical WordPress page with a hero image and a couple of plugins is 1.5-3 MB. An image-heavy gallery or e-commerce category page can run 4-8 MB.
Measure it rather than assume. Browser developer tools report transferred bytes per page, and a small crawl with a tool that reports sizes gives you an average across your real templates. Compression matters here: Brotli or gzip on text assets cuts HTML, CSS, and JS by 60-80 percent, and modern image formats cut photos by 30-70 percent against JPEG. A page that starts at 3 MB can drop under 1 MB with correct image dimensions and modern formats, which changes your bandwidth tier entirely. Test on a real mobile device, not a desktop browser at full resolution, because mobile users are where most of the bytes actually go.
The Repeat-Visitor Factor
Not every visitor downloads the full page weight. Returning visitors have cached CSS, JavaScript, and fonts, so they pull perhaps 20-40 percent of the first-load bytes. Browser caching plus a CDN pushes the ratio lower still.
For a content site with a returning readership, multiply first-load page weight by 1.3-1.6 pages per visit and by a caching factor of 0.6-0.8. A first-timer-heavy site, by contrast, sits near a caching factor of 1.0. If you serve a global audience, assume fewer cache hits unless you front the site with a CDN.
Session length and bot traffic also shift the number. Analytics often reports pageviews that include crawlers and monitoring probes, which do not download images or CSS. Filtering bot hits out of your pageview count typically reduces the true human figure by 10-30 percent, which matters when that figure decides whether you buy the $5 or the $10 plan.
Worked Examples at Real Traffic Levels
Take a WordPress site at 2 MB average page weight, 1.5 pages per visit, and a caching factor of 0.7. That is 2.1 MB of transfer per visit.
- 10,000 visits/month = 21 GB
- 50,000 visits/month = 105 GB
- 100,000 visits/month = 210 GB
- 500,000 visits/month = 1,050 GB (about 1 TB)
Most small sites land under 200 GB, which fits comfortably inside a 1 TB allowance. An image-heavy store at 5 MB per page and 100,000 visits hits 525 GB, still within 1 TB but closing on the ceiling. Push to 5 MB and 250,000 visits and you cross 1 TB, where overage pricing starts to matter.
A static documentation site behaves very differently. At 300 KB per page, 100,000 visits is only 30 GB, so even a tiny allowance is generous. Software downloads and video are the exceptions that break this model: a single 500 MB installer served 5,000 times is 2.5 TB on its own, which belongs on object storage or a CDN rather than a VPS transfer allowance.
Why Almost Every Small Site Fits in 1 TB
Budget plans commonly include 1-2 TB of transfer, and larger tiers advertise 4-10 TB. Because most small sites serve under 200 GB, the realistic risk is not the monthly allowance but the spike. A single link from a large platform can deliver 50,000 visits in a day, which at 2 MB per visit is 100 GB in 24 hours.
That is survivable on a 1 TB plan but consumes 10 percent of the month in one day. Two such events in a month, plus normal traffic, gets uncomfortable. This is exactly the scenario to model before choosing a tier, and it is why plan allowances should be compared with spikiness in mind. See how we lay out allowances in our budget VPS comparison table.
Cutting Egress Without Paying More
Four levers reduce transfer at zero licensing cost:
- Enable Brotli or gzip for text assets.
- Serve WebP or AVIF images with correct sizing.
- Set long cache headers so returning visitors fetch less.
- Put static assets behind a CDN with a generous free tier.
A free-tier CDN absorbs the bulk of static egress and leaves the VPS serving HTML and API responses only. That alone can cut origin transfer by 60-80 percent, turning a potentially tight 1 TB plan into one with genuine headroom.
Reading the Billing Fine Print
Overages are billed per GB above the allowance, usually $0.005-0.02 per GB, but granularity varies. Some providers bill in 1 GB increments; others round up to 100 GB or even 1 TB blocks. On a 100 GB block provider, a 5 GB overage charges as 100 GB, which can multiply the effective rate twentyfold.
Also confirm whether the allowance resets monthly or pools across the billing term, and whether unused transfer rolls over. A plan with a slightly smaller allowance but fine-grained overage billing is often safer than a larger one that rounds aggressively.
A final caution: unmetered or unlimited transfer is never truly unlimited. Providers enforce a fair-use clause and can throttle or suspend an instance whose bandwidth threatens their network. Read that clause before relying on a plan that claims no limit, because the practical ceiling is often lower than a metered 2 TB plan with published overage rates.
Bottom Line
Measure your page weight, multiply by visits and a caching factor, then add a spike buffer of two to three times the normal month. If the result is under 500 GB, a 1 TB plan is ample and you should spend the savings on RAM or backups. If it approaches 1 TB, either upgrade a tier or offload static assets to a CDN, which is usually the cheaper fix. For a shortlist of providers with sane allowance-to-price ratios, compare budget VPS plans before you commit.
Related Articles：
VPS Price Tier Breakpoints: What $5, $10, and $15/Month Plans Actually Buy in 2026
Your First Hour on a $5 VPS: A Setup Checklist That Keeps a Budget Server Fast
Hosting Multiple Websites on One Budget VPS: Nginx Server Blocks, PHP-FPM Pools, and RAM Planning
How to Cut Your VPS Bill by 40-60%: Contract Renewal, Provider Switching, and Resource Optimization
