Website Bandwidth Calculator

Monthly bandwidth from traffic, page size, and visitor behavior.

Inputs

Site Presets

MB
≥ 1.0

How Website Bandwidth Is Calculated

Website bandwidth is the total data transferred from your server to visitors over a period. It combines page views, asset sizes, and delivery overhead, then multiplied by a redundancy factor to account for repeat loads, images, and JavaScript bundles.

Monthly BW = Daily Views × Page Size × Redundancy × Bot Factor × CDN Factor × Cache Factor × 30.44

Website Bandwidth by Site Type

Site TypeDaily ViewsAvg Page SizeMonthly BW
Personal Blog5001 MB~15 GB
Small Business2,0002 MB~120 GB
News Website50,0002 MB~3 TB
Ecommerce Store20,0003 MB~1.8 TB
Video Platform10,00050 MB~15 TB
SaaS Application30,0001.5 MB~1.4 TB

5 Ways to Reduce Bandwidth Costs

01

Enable a CDN

Content Delivery Networks cache assets at 200+ edge locations globally, serving 60–80% of requests without touching your origin server.

02

Optimize Images

Switch to WebP or AVIF format and enable lazy loading. A single uncompressed hero image can be 80% of a page's total weight.

03

Leverage Browser Caching

Setting Cache-Control headers instructs browsers to store static assets locally. Returning visitors skip re-downloading CSS, JS, and fonts.

04

Enable Brotli Compression

Brotli compresses HTML, CSS, and JavaScript 15–25% more efficiently than gzip, reducing transfer sizes with zero content change.

05

Block Bot Traffic

Automated scrapers and crawlers can account for 20–40% of raw bandwidth. Implementing Cloudflare or Nginx rate limiting eliminates this waste.

Choosing the Right Hosting Plan

Shared Hosting (0–200 GB/month)

Suitable for blogs and small business sites. Bandwidth shared across many users — can spike and throttle unexpectedly under heavy load.

VPS Hosting (200 GB – 1 TB/month)

Dedicated virtual resources with burstable bandwidth. Ideal for growing sites with consistent traffic and predictable load.

Dedicated Server (1–10 TB/month)

Full hardware ownership. Necessary for high-traffic news sites, large ecommerce, and applications needing sustained multi-gigabit throughput.

CDN + Object Storage (10 TB+/month)

The most cost-effective path for extreme scale. Store static assets in S3/R2, serve via Cloudflare or Fastly. Scales to petabytes.

About This Bandwidth Calculator

Accurate Formulas

Built on IEEE 1541 IEC binary standards and SI decimal definitions per NIST Special Publication 330.

Free & Private

All calculations run in your browser. No data is sent to servers, stored, or used for analytics.

Independently Verified

Results cross-checked against Wolfram Alpha unit conversions and network engineering references.

Related tools: Unit Converter, Speed Calculator, Time Calculator, IP Subnet Calculator, Percentage Calculator.

Frequently Asked Questions

The fundamental formula is: Monthly Bandwidth = Daily Page Views × Average Page Size × Redundancy Factor × 30.44. For a site with 10,000 daily views, 2 MB pages, and 1.5× redundancy: 10,000 × 2 MB × 1.5 × 30.44 = 912 GB/month ≈ 1 TB. Add 20–30% for bot traffic, subtract 30–60% if you use a CDN, and add caching savings for returning visitors.

The redundancy factor accounts for all the extra data transferred beyond the base page HTML — images loaded in subsequent requests, JavaScript bundles, CSS files, fonts, and API calls. A factor of 1.0 means only the page HTML; 1.5 means 50% more data than the page size alone. For content-heavy sites, factors of 1.5–2.0 are realistic. Video-heavy sites may use 5–10×.

Yes — web crawlers from search engines (Googlebot, Bingbot), SEO tools (Ahrefs, SEMrush), and malicious bots all request pages and consume bandwidth. Legitimate search bots are generally courteous and respect crawl delays, but aggressive scrapers can consume 20–40% of your bandwidth. Tools like Cloudflare's bot management can filter these requests before they reach your origin server.

A well-configured CDN with high cache hit rates can reduce your origin server's bandwidth by 60–80%. The calculator models CDN coverage at 70% offload efficiency per percentage covered. For example, at 50% CDN coverage, origin bandwidth is reduced by 50% × 0.7 = 35%. For maximum savings, configure your CDN to cache all static assets (images, CSS, JS) with long TTLs.

Google's Core Web Vitals recommend keeping total page weight under 1.5–2 MB for optimal performance. The average web page weighed about 2.5 MB in 2024, up from under 1 MB in 2012. For SEO and user experience, targeting under 2 MB is advisable. Reducing images to WebP format and deferring non-critical JavaScript are the two highest-impact optimizations.

Shared hosting suits sites under 10–50 GB/month. VPS (Virtual Private Server) handles 50 GB–1 TB/month at predictable performance. Dedicated servers support 1–20 TB/month. For over 20 TB/month, a CDN-first architecture (Cloudflare + object storage like S3/R2) becomes more cost-effective than raw server bandwidth. Always add 50% headroom above your estimated usage.

Your hosting control panel (cPanel, Plesk) shows real-time and historical bandwidth under 'Statistics' or 'Bandwidth.' For more detailed analysis, Cloudflare analytics, Google Analytics (via user sessions × page size), or server log parsers (AWStats, GoAccess) provide page-level breakdowns. Most cloud providers (AWS, Vercel, Netlify) show bandwidth in their billing dashboard.

Peak bandwidth is the maximum instantaneous transfer rate, typically 3–10× the daily average due to traffic spikes (viral content, news coverage, promotions). If your server can't sustain peak bandwidth, visitors see slow loads or errors. This calculator estimates peak at 5× average. Your hosting plan's burst capability, not just the monthly cap, determines whether you survive a traffic spike.

Yes — dramatically. A page with embedded video or audio is 10–100× larger than a text page. A 30-second auto-play video at 720p adds ~15 MB to a page load. Even 5 video embeds per page at 5,000 daily views adds 375 GB/day — 11+ TB/month from video alone. Host media on a CDN or video platform (YouTube, Vimeo, Cloudinary) and serve only thumbnails from your origin.

Server-side caching (Varnish, Nginx FastCGI, WordPress caching plugins) serves prebuilt pages without hitting your database, dramatically reducing server CPU and memory load. Browser caching instructs visitors' browsers to store static files locally, so returning visitors skip re-downloading CSS, JS, and images. Combined, aggressive caching can reduce origin bandwidth by 40–60% for sites with significant return traffic.