Was this an EE site?
Yes.
I’ve recently done the same thing with a few other sites, especially those on more inexpensive hosts with definite service limits (no one really believes you can get unlimited bandwidth for $4.99 a month, right?).
A web page can be served with dozens of “hits” per page request (not to mention the DB hits); the HTML file, the CSS file. favicon file, each graphic element, photos, javascripts, etc. Likewise, the number of hits to a site’s server can be reduced substantially with a little Amazon S3 thrown into the mix. For example, a single, modest sized EE page with three javascripts, two CSS files, and a dozen graphic elements can count for a couple dozen “hits.” Two dozen server “hits” can be reduced to a couple of hits, which improves performance. Effective EE caching can help out elsewhere.
Unless you’re dealing with your own multiple, load-balanced servers and essentially unlimited bandwidth, it pays to organize those elements accordingly.