Content revised 21 October 2026.
Hosting plans sometimes use bandwidth to describe a monthly data-transfer allowance. Distinguish that allowance from connection capacity, storage and the processing resources your website needs.
Separate the measurements
Connection capacity is a rate, commonly expressed in bits per second. Data transferred over a period is an amount, often billed or limited in bytes. Storage is the space occupied by files. Those figures describe different constraints and should not be compared as if they were the same resource.
Make a rough transfer estimate
For planning, multiply an estimated transferred page size by page views, then consider media, downloads and automated requests separately. For example, a hypothetical 1 MB transfer repeated 10,000 times is roughly 10 GB before other traffic and overhead. The example is not a prediction for your site.
Check the assumptions
- A repeat visit may reuse cached resources.
- Large video or downloads can dominate transfer.
- Page types may have different payloads.
- Bots and unexpected demand can add usage.
Read the hosting terms
Ask how the provider measures transfer, whether a CDN changes the calculation and what happens at a limit. An unmetered label may still have other resource or acceptable-use conditions. Compare the actual terms rather than assuming unlimited application capacity.
Use measured data to refine the plan
Review real transfer and performance over a suitable period, allowing for campaigns and growth. Optimise unnecessary payloads while keeping useful content available. A bigger transfer allowance alone will not repair slow application code or guarantee faster pages.
Official guidance: Google web.dev’s explanation of resource reuse.