Bandwidth is the total data your site transfers to visitors, search engines, and bots over a billing period: every page load, every image, every CSS and JS file, every API response. If your traffic is climbing fast, the fix is usually caching and image weight, not a bigger plan: LiteSpeed's built-in LSCache and, on WordPress sites, the pre-installed LiteSpeed Cache plugin with Redis object cache already cut most of the repeat-request load.
What actually counts
Every byte sent from your hosting account counts, regardless of who's asking:
- Normal visitor page loads: HTML, CSS, JS, images, fonts, video.
- Search engine crawlers (Googlebot, Bingbot) re-fetching your pages.
- AI crawlers and scrapers, which can add to bot traffic (see fighting unwanted inbound traffic).
- Direct file downloads: PDFs, zip files, software builds, anything linked from your site.
- Email sending and receiving through your hosting account, though this is usually small next to web traffic.
If you're using our Cloudflare CDN, turning on the proxy and enabling caching for a domain can move a share of repeat traffic off your origin server.
Where usage actually goes
Three things tend to eat bandwidth faster than raw visitor count would suggest:
- Unoptimized images. A handful of multi-megabyte photos on a homepage can outweigh thousands of regular page views. Resize and compress before upload; cPanel's Images tool (Thumbnailer, Scaler, Converter) can help after the fact.
- Hotlinking. Other sites embedding your images directly serve your bandwidth to their visitors. Hotlink Protection in cPanel stops this by refusing image requests that don't originate from your own domain.
- Bot traffic. AI crawlers can add up on active sites. If you're on the Cloudflare CDN, the AI Crawlers panel lets you allow, block, or restrict search crawlers, AI assistants, and model-training bots separately, per domain.
Checking your usage
In cPanel, the Bandwidth tool under Metrics shows your usage over time, so you can see whether a spike lines up with web traffic or something else, like a large file being transferred repeatedly. Visitors and Awstats can help you spot whether a spike is real visitors, a crawler, or a single heavy file being hit on a loop. Raw Access gives you the underlying server logs for deeper investigation if you need to dig further.
Reducing load without losing traffic
The goal is never to block real visitors. Start with caching: LSCache and, on WordPress, the LiteSpeed Cache plugin serve repeat requests from cache instead of regenerating pages, which cuts both CPU load and bandwidth. Turning on the Cloudflare proxy adds a second layer of caching in front of that. From there, compress images before upload rather than relying on the server to do it, enable Hotlink Protection if other sites are embedding your media, and use the AI Crawlers controls to restrict training bots that add no real value to your traffic. A fast, well-cached site naturally uses less bandwidth per visit too.
When to open a ticket
If usage jumps suddenly and Awstats or Raw Access don't make the source obvious, or if you suspect a compromised script is being used to distribute files through your account, open a ticket from the portal. Our team can help investigate what's driving the spike.