Every byte of data your website sends to a visitor costs you bandwidth. While most hosting providers offer “unmetered” bandwidth on their starter plans, high-traffic sites quickly run into hard limits. When you cross those thresholds, you’re faced with slow load times, sudden site suspensions, or expensive overage fees.
From working with thousands of high-traffic sites, we’ve seen that the median desktop homepage reached 2.86 MB in 2025—up 110% compared to a decade ago (HTTP Archive, 2025). As sites become heavier with high-resolution images, complex JavaScript, and video content, knowing how to conserve bandwidth is critical for keeping infrastructure costs down.
📋 TL;DR • Use a CDN: A CDN serves cached copies from edge servers, so your origin answers far fewer requests. • Stop self-hosting video: Video files are massive; use a dedicated video CDN instead of local hosting. • Compress efficiently: Switch from Gzip to Brotli compression for text, and use WebP/AVIF for images. • Protect your assets: Block AI bots and prevent image hotlinking to stop others from draining your resources.
1. Deliver Assets Through a CDN
If your website serves every image, script, and stylesheet directly from your primary hosting server, you are burning through your bandwidth allocation unnecessarily.
A Content Delivery Network (CDN) sits between your server and your visitors — here’s what a video CDN does in more detail. It caches your static assets on edge servers distributed around the world. When a user requests a page, the CDN delivers the heavy files from the server closest to them, rather than making your origin server do the work.
Cloudflare does not publish a fixed percentage; it describes a CDN as serving cached content from its own servers, which “significantly reduces the amount of data the origin server must provide” (Cloudflare, accessed 2026-09-05). How much you actually offload depends on your cache-hit ratio, and premium CDNs provide more granular caching controls.
2. Stop Self-Hosting Video (And Be Careful With YouTube)
Video is the single largest consumer of bandwidth on the modern web. In fact, video bytes on median pages grew 28% year-over-year in 2025 (HTTP Archive, 2025). If you are uploading MP4 files directly to your media library, you are creating a ticking time bomb for your hosting bill.
This is exactly why you should never host video files directly on your server. A single 100 MB video viewed by 1,000 visitors will consume 100 GB of bandwidth. We’ve seen sites completely crash after a single self-hosted video goes viral.
Here is a breakdown of the bandwidth cost of different video delivery methods:
| Delivery Method | Bandwidth Cost per 10k Views (100MB Video) | Impact on Origin Server |
|---|---|---|
| Self-Hosted MP4 | 1,000 GB | High (Often causes downtime) |
| YouTube Embed | 0 GB (Video) + ~5 GB (player JS/tracking at ~500 KB/view) | Low (But hurts page speed) |
| SmartVideo | 0 GB | Zero (Fully offloaded) |
Most guides suggest embedding YouTube videos to solve this. While YouTube does offload the video file delivery, the true cost of YouTube’s free player comes in the form of heavy third-party JavaScript and tracking scripts that still drag down your initial page load speed.
3. Upgrade to Brotli Compression
For years, Gzip was the standard for compressing text-based files (HTML, CSS, JavaScript) before sending them to the browser. Today, Brotli is the modern standard.
Developed by Google, Brotli compression is supported by all modern browsers and offers denser compression than Gzip: Google measured 20–26% higher compression ratios than Zopfli, the densest gzip-compatible encoder (Google Open Source Blog, 2015). Our data shows that sites updating their server configurations to Brotli often see a noticeable drop in bandwidth consumption.
4. Serve Next-Gen Images and Lazy Load Them
Images remain the largest resource type on most pages, often weighing in at over 1 MB per page. Saving bandwidth here requires a two-step approach:
First, stop using heavy JPEGs and PNGs. Convert your images to WebP or AVIF formats. Google measures lossy WebP at 25–34% smaller than comparable JPEGs at equivalent SSIM quality, and lossless WebP at 26% smaller than PNG (Google Developers, accessed 2026-09-05). Many sites still serve heavy PNGs when WebP would cut the weight.
Second, don’t load images until the user actually scrolls down to see them. You no longer need heavy JavaScript libraries to accomplish this. Simply add the native HTML attribute to your image tags:
<img src="image.webp" alt="Description" loading="lazy">
This ensures you aren’t wasting bandwidth delivering images to visitors who bounce before scrolling past the fold.

5. Rate Limit AI Crawlers
A new bandwidth drain has emerged in recent years: AI web scrapers. Companies training large language models deploy aggressive bots to crawl sites, often ignoring standard request limits and downloading your entire site structure repeatedly.
If you check your server logs and notice massive bandwidth spikes without a corresponding increase in real human traffic, bots are likely the culprit. A common mistake we see is site owners confusing AI crawler spikes with legitimate traffic growth. You can conserve significant bandwidth by using Bot Management tools or adjusting your robots.txt file to block known AI crawlers from scraping your heavy media assets.
🚀 Need a faster way to serve video? SmartVideo automatically fetches your videos, encodes them for optimal web delivery, and serves them via our global edge network—saving your server bandwidth while keeping visitors on your site. See how SmartVideo works.
6. Set Aggressive Cache-Control Headers
Browser caching dictates how long a visitor’s browser should store your files locally. When a user visits a second page on your site, they shouldn’t have to re-download your logo, CSS, or fonts.
By setting proper Cache-Control and Expires headers, you instruct the browser to hold onto these static files for weeks or months. This dramatically reduces the bandwidth required for returning visitors. How much a returning visitor re-downloads depends on your asset mix and cache lifetimes.
7. Minify CSS, JavaScript, and HTML
Minification removes whitespace, comments, and unnecessary characters from your code without changing its functionality. When you minify your CSS, JavaScript, and HTML, the files become significantly smaller.
Minification strips bytes before compression and Brotli compresses what remains, so the combined saving depends on your bundle; measure it as before/after transfer size. Most caching plugins and modern frameworks handle this automatically during the build process.
Optimizing your server configuration and delivery pipeline is the most direct way to cut bandwidth costs.
8. Remove Unused Web Fonts
Custom fonts add a unique look to your site, but loading five different weights of Google Fonts can add hundreds of kilobytes to every pageview.
We’ve found that paring down your font choices to just two weights (regular and bold) per font family can save massive amounts of data. Also, ensure you use the modern WOFF2 format instead of older, heavier formats.
9. Prevent Image Hotlinking
When another website links directly to an image hosted on your server, they are stealing your bandwidth every time their page loads. This is called hotlinking.
Our data shows that high-ranking image assets often become targets for scrapers and lazy bloggers. You can block hotlinking by adding a simple rule to your .htaccess file or by toggling hotlink protection in your CDN settings, instantly cutting off the unauthorized drain on your resources.
10. Paginate Long Comments and Content
If you run an active blog or forum, loading hundreds of user comments on a single page forces the server to send massive amounts of text and avatar images with every visit.
From what we’ve seen, simply paginating your comment section (e.g., loading 50 comments per page) or using a “Load More” button drastically reduces the initial data payload. This limits the bandwidth used to only what the visitor actively requests to read.
Stop Paying for Wasted Bandwidth
Reducing your website bandwidth isn’t just about avoiding overage fees—it directly impacts your conversion rates by creating a leaner, faster experience for your users. Start with the easy wins: enable Brotli compression, implement lazy loading, and route your traffic through a CDN.
However, if you’re serious about conserving bandwidth, you must address your heavy media. When you’re comparing options, our guide to the best video hosting platforms breaks down the trade-offs. Using a dedicated video delivery network is the most effective way to embed video without ads while keeping your server load completely flat. SmartVideo handles the heavy lifting of video hosting so your site stays fast, regardless of how much traffic you get.
Frequently Asked Questions
What uses the most bandwidth on a website?
Video files are consistently the largest consumer of website bandwidth, followed by high-resolution images and heavy JavaScript bundles. A single unoptimized background video can easily consume more bandwidth than the rest of the page combined (HTTP Archive, 2025).
How do I calculate my website bandwidth needs?
You can estimate your bandwidth by multiplying your average page size by your monthly pageviews. For example, if your average page is 2 MB and you get 10,000 pageviews a month, you will need at least 20 GB of bandwidth, plus extra buffer room for traffic spikes.
Does a CDN really reduce bandwidth usage?
Yes, a CDN reduces bandwidth usage on your origin server by storing copies of your static files on global edge servers. When visitors request your site, the CDN serves the files locally, which cuts the data your origin has to transfer; the share offloaded depends on your cache-hit ratio (Cloudflare, What is a CDN?, accessed 2026-09-05).
Why is my bandwidth usage suddenly so high?
Sudden bandwidth spikes are typically caused by a viral piece of content, a DDoS attack, aggressive AI web scrapers crawling your site, or a large video file that was recently embedded directly on a popular page instead of being hosted externally. If you notice an unexpected surge in traffic without a matching increase in real users, check your server logs for bot activity or hotlinked media assets.
What happens if I exceed my hosting bandwidth limit?
If you exceed your bandwidth limit, your hosting provider may throttle your site’s speed, temporarily suspend your website, or automatically charge you premium overage fees per gigabyte used over your limit. These overage charges are often significantly more expensive than upgrading to a higher-tier hosting plan beforehand.
Is Brotli compression better than Gzip?
Yes, Brotli compression is generally more efficient than Gzip, particularly for text-based files like HTML, CSS, and JavaScript. It can produce files that are 15 to 20 percent smaller than Gzip, which directly translates to saved bandwidth (Web Dev, 2025).
Does embedding YouTube videos save bandwidth?
Yes, embedding YouTube videos saves your server from delivering the heavy video file. However, the YouTube player still requires downloading nearly 1 MB of external JavaScript and tracking code, which still impacts your total page weight and load time.
How much bandwidth does a small business website need?
Most small business websites without heavy media require between 5 GB and 10 GB of bandwidth per month. However, if your site features high-resolution portfolios, downloadable assets, or embedded video content, your minimum requirements will likely start closer to 50 GB.
Does lazy loading save bandwidth?
Yes, lazy loading saves bandwidth by preventing off-screen images and media from downloading until a user scrolls near them. This ensures you only transfer data for assets that visitors actually see, rather than forcing them to download the entire page content up front.