A CDN helps users, to re-use common files already downloaded for other sites like jQuery and jQueryUI, which don't need to be downloaded again or might be downloaded from a different server, saving you traffic and allowing a bit faster download from your server, but I don't provide much improvements and only on the first page upon first visit of a user. However, your site is already using CDN for these files.

YSlow is also suggesting to use CDN for your static files, which is possible but requires quite some work, I.e. you need a 2nd site where to put it and adjust the links. It makes sense for some of the larger files, while smaller images would benefit from combining into an image sprites.

Expires header/ETags will be included in DNN 7.3.0, but don't expect too much of improvement.

However, your site requires long time to retrieve thumbnails, which seem to be generated on the fly (and not being cached on the server), and don't get outputted in the right size, because they are displayed smaller than the output.

And finally, the sliding background images on your home page are large (~100k each) and cost a lot of traffic.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Thank you for your descriptions....