Hi Ari, Excellent question. The benefit comes from PageBlaster being able to do caching, compression, and replacements on JS & CSS, and if you configure it to handle images it will also strip the ETag header and add expires headers for those files as well. Expires headers are what is needed to make the files stay in the cache on the user's browser and keeps the browser from having to make several requests just to find out the files have not been changed. You can set expires headers directly in IIS, and you can also do compression if your server is setup for it, but some people can't do that at the server level. The downside is that sending these static files to ASP.Net and letting PageBlaster handle them may be a little slower than IIS on the first request, but it really helps to optimize how they are stored at the client. Sending them to PageBlaster also allows you to configure the expire times by page where if you do it in IIS it is for the whole site. You can learn more about these optimizations here: http://developer.yahoo.com/performance/rules.html |