Measure a visit rather than guessing from page count
A hundred small pages can transfer less data than a single photo-heavy landing page. Open a representative journey in browser developer tools and inspect the bytes actually transferred. Include a first visit and a repeat visit. The result depends on compressed responses, image choices and what the browser already has cached.
Use a deliberately simple model
For an initial planning exercise, multiply uncached page weight by page views. If a page transfers 1.5 MB and receives 20,000 views, the rough total is 30,000 MB, or 30 GB using decimal units. This is an illustration, not a forecast: bots, downloads, video, API traffic and cache hits can move the real number in either direction.
Separate downloads from ordinary reading
A 50 MB PDF downloaded 1,000 times adds another 50 GB to the illustrative total. Keep large files in a separate row so they do not disappear inside an average page weight. If media is served by another service, find out which provider bills that transfer; it has not become free merely because it is absent from the origin log.
Read the allowance definition
Ask whether the quoted limit concerns outbound traffic, both directions or a particular network port. Find out what happens at the limit: a charge, a speed restriction or a suspension. Do not compare a transfer allowance with a port speed as if they were the same unit. One describes an amount over time; the other a rate.
Replace the estimate with observation
After launch, compare the calculation with actual transfer records for a representative period. Keep notes on unusual downloads or campaigns. Optimise oversized images before buying capacity to carry avoidable bytes, but retain image quality that matters to the article. The useful outcome is a repeatable budget, not a suspiciously precise prediction.
Put it into practice
| Item | Calculation | Transfer |
|---|---|---|
| Reading pages | 1.5 MB × 20,000 | 30 GB |
| PDF downloads | 50 MB × 1,000 | 50 GB |
| Subtotal | Before other traffic and cache effects | 80 GB |
Sources & further reading
Examples and worksheets on this page are illustrative. Documentation links were checked in November 2026; follow the relevant product’s current instructions.
