The key point is actually taken from someone else's blog post at http://jetnexus.blogspot.com/2010/03/what-does-application-acceleration-mean.html http://jetnex

The key point is actually taken from someone else's blog post at http://jetnexus.blogspot.com/2010/03/what-does-application-acceleration-mean.html http://jetnexus.blogspot.com/2010/03/what-does-application-a..., and it's this: You might think that there's no point using transparent compression for a website most of whose content is in images, since image files generally compress poorly if at all. However, 1. those images are presumably embedded in web pages, and if compressing those gets them to the user faster then it's a win; 2. many of those images will already be in the browser cache, so the fraction of your traffic that's in images may be smaller than you think.