you can set that up in your .htaccess (if allowed by http.conf) and basically make your files include expiration dates, so when peeps come by and grab the images, css, js etc one time, they cache them and don't take up your BW the next time around..
it's a good thing to implement, if your server setup / hosting situation allows it
example of what i have in my http.conf (but it could just as easily be .htaccess for those who can't configure apache)
ExpiresActive On
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType text/css "access plus 1 year"
ExpiresByType application/x-javascript "access plus 1 year"
<FilesMatch "(?i)^.*\.(css|js)$">
SetOutputFilter DEFLATE
# Netscape 4.x has some problems...
BrowserMatch ^Mozilla/4 gzip-only-text/html
# Netscape 4.06-4.08 have some more problems
BrowserMatch ^Mozilla/4\.0[678] no-gzip
# MSIE masquerades as Netscape, but it is fine
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
# Make sure proxies don't deliver the wrong content
Header append Vary User-Agent env=!dont-vary
</FilesMatch>
<FilesMatch "(?i)^.*\.(ico|flv|jpg|jpeg|png|gif|js|css)$">
SetHandler None
FileETag MTime Size
Header unset Last-Modified
Header set Expires "Fri, 21 Dec 2012 00:00:00 GMT"
Header set Cache-Control "public, no-transform"
</FilesMatch>the dec 21, 2012 date was taken from the a Mayan expert on apache
![[Linked Image from navaho.infopop.cc]](http://navaho.infopop.cc/progress.gif)
