| Web hosting bandwidth is the total data your server sends to visitors each month, measured in gigabytes. Calculate it by multiplying average page weight by pages per visit, then by monthly visits. Most small business sites use under 20GB a month, well inside any standard plan. |
Bandwidth is the most misunderstood number on a hosting invoice. Buyers usually read it as speed, because that is what the word means on a home internet plan. In hosting, however, it means volume. Your host is telling you how much data it will send out of the server on your behalf during a billing month, not how fast it will send it. Speed comes from server resources, caching and network routing, which we cover in why your website is slow.
This guide gives you the formula, a worked example with real numbers, the four things that quietly inflate the figure, and the point at which bandwidth genuinely becomes a reason to upgrade.
Bandwidth, data transfer and throughput are not the same thing
Three terms get used interchangeably in hosting marketing, so it helps to separate them clearly.
| Term | What it measures | Typical unit | Where you see it |
| Bandwidth (as hosts use it) | Total data sent per month | GB or TB per month | Plan comparison tables |
| Throughput | Data moved per second at a moment in time | Mbps or Gbps | Network and port specifications |
| Latency | Delay before the first byte arrives | Milliseconds | Speed tests and TTFB reports |
A plan can offer generous bandwidth and still feel slow, because the delay a visitor notices usually comes from latency and server response time rather than from the monthly cap. If your pages feel sluggish rather than blocked, read what network latency is instead. Bandwidth only becomes visible to users when you exhaust it, at which point the host either throttles the account or suspends it until the next cycle.
The formula for calculating bandwidth
The calculation is straightforward, and you can run it in under a minute.
| Monthly bandwidth = average page weight x pages viewed per visit x monthly visits x redundancy factor |
Three of those inputs come from your analytics. The fourth, the redundancy factor, accounts for crawlers, retries, uncached repeat visits and any file downloads. Use 1.5 as a working multiplier if you have no data, and 2 if you serve large media files.
Page weight is the input people guess wrong most often. Median page weight measured across the public web sits in the low megabytes for desktop pages, and image files account for the largest share of it. Your own figure matters more than any median, so measure it rather than assume it.
A worked example with real numbers
Take a Nepali business site running WordPress with a moderate image load. Assume a 1.8MB average page, three pages per visit and 5,000 monthly visits.
| Step | Calculation | Result |
| Data per visit | 1.8MB x 3 pages | 5.4MB |
| Raw monthly transfer | 5.4MB x 5,000 visits | 27,000MB, roughly 27GB |
| With 1.5 redundancy factor | 27GB x 1.5 | Roughly 40GB per month |
| Headroom for growth | 40GB x 2 | Provision for about 80GB |
Eighty gigabytes a month sounds substantial until you compare it against a plan allowance. It is a fraction of what a standard shared hosting account provides. That is the honest conclusion for most readers: your traffic is not the problem, and bandwidth is rarely the number that should decide your plan.
Now change one input. Replace the 1.8MB page with a 6MB page carrying uncompressed hero images, and the same 5,000 visits produce roughly 135GB after redundancy. The traffic did not change. The page weight did.
Four things that inflate bandwidth without more visitors
Uncompressed images
Images dominate page weight on almost every content site. Converting JPEG and PNG assets to WebP or AVIF commonly cuts image payload by a third or more at visually identical quality. Serving a 3000 pixel wide photograph into a 800 pixel container wastes the difference on every single request.
Video served from your own server
A single two minute video at moderate quality can exceed 40MB. One thousand plays consume 40GB by themselves, which is more than the entire example site above. Host video on YouTube, Vimeo or object storage, then embed it. This is the single largest bandwidth decision most sites make.
Bots and crawlers
Search engine crawlers, uptime monitors, security scanners and AI training crawlers all consume transfer. Googlebot and Bingbot are worth every byte. AI crawlers such as GPTBot, ClaudeBot and PerplexityBot are a business decision, since blocking them protects bandwidth but removes you from the surfaces that increasingly answer buying questions. Scrapers and vulnerability scanners deserve no bandwidth at all, and you can block them at the firewall or through Cloudflare.
Missing cache headers
Without expiry headers, a returning visitor downloads your logo, stylesheet and scripts again on every page view. Correct cache control turns those repeat downloads into local cache hits and often removes half your transfer on content sites.
How to check your actual bandwidth usage
Do not estimate when you can measure. In cPanel, three tools give you the real figure.
- Bandwidth, under Metrics, shows monthly transfer by month, split by HTTP, FTP and email.
- AWStats or Webalizer breaks the same data down by day, by file type and by user agent, which is how you spot bot consumption.
- Raw Access lets you download the server log itself if you need to inspect a specific spike line by line.
Compare that figure against the allowance printed on your plan, not against your analytics sessions. Analytics tools count human visits and often miss bots entirely, so the server log is always the higher and more honest number.
What unmetered and unlimited bandwidth really mean
Unmetered bandwidth means the host does not bill per gigabyte. It does not mean the server will serve any volume you send at it. The binding limits are CPU, memory and process counts, which throttle long before transfer becomes an issue, plus the acceptable use policy. The pattern is identical to the one described in our guide to unlimited storage and fair use, and the honest reading is the same: the limit exists, it is simply written in a different unit.
In practice, an account on a shared server hits resource limits when a traffic spike arrives. The response is a 508 or 503 error, not a bandwidth invoice. Anyone selling you a bigger transfer allowance to fix that is selling you the wrong upgrade.
A content delivery network changes the maths
A CDN caches your static files on servers close to your visitors. Once the cache is warm, images, CSS and JavaScript are served from the edge rather than from your origin, so those bytes never touch your hosting allowance. On an image heavy site this commonly removes the majority of origin transfer, and it improves load time for distant visitors at the same time.
For a Nepali site with buyers in Nepal, India, the Gulf and North America, that geographic spread is the stronger argument. Bandwidth savings are the side benefit. If most of your audience sits in one country, choosing the right hosting type and server location does more for you than a CDN will.
When bandwidth is genuinely your upgrade signal
Move up when at least two of these hold true, and not before.
- Your measured monthly transfer sits above roughly 70 percent of the plan allowance and keeps climbing month on month.
- You have already compressed images, moved video off the server and set cache headers, and the figure has not fallen.
- Traffic spikes produce 503 or 508 errors rather than slow pages, which points at resource limits rather than transfer.
- You serve downloadable files, software or media as a core part of the product.
When those conditions hold, a VPS gives you defined resources you can size rather than shared limits you discover by hitting them. If they do not hold, stay where you are. Compare current Bisup hosting plans on CPU, memory and support quality instead, because those are the numbers that will actually decide your experience.
Frequently asked questions
Multiply your average page weight by pages per visit and monthly visits, then add 50 percent for crawlers and repeat requests. A typical small business site with 5,000 monthly visits and 1.8MB pages needs roughly 40GB. Media heavy sites need several times more.
No. In hosting, bandwidth means total monthly data transfer measured in gigabytes. Speed depends on server response time, latency and caching. A plan with a large transfer allowance can still deliver slow pages, and a small allowance does not make pages slower.
Most providers either throttle the account, charge an overage fee, or suspend the site until the billing cycle resets. Check which of the three your provider applies, because suspension and throttling have very different consequences for a business site.
No. Unmetered means the host does not bill per gigabyte. CPU, memory and process limits still apply and usually bind first. A traffic spike on shared hosting typically produces a resource error rather than a bandwidth charge.
Yes. Search crawlers, uptime monitors, security scanners and AI crawlers all consume transfer. Server logs and AWStats show usage by user agent, which is the only reliable way to see how much of your monthly total is not human traffic.
[…] you are budgeting for a new site, it also helps to estimate your hosting bandwidth needs alongside your SSL certificate cost, since both are part of the same annual hosting budget. And if […]