I just ran my site through a page load analyzer and the analyzer reported "file not found" (404) for quite a number of images.  These images were the advertising images that come on the default DNN home page when you first install DNN.  (telerikinside.jpg, dnn_proedition.jpg, maretplacetitle.gif, etc.)   Turns out that instead of calling these images right from the text/html module that they are used in DNN hardcoded the references to these images in the portal.css file.  So if you delete the text/html module and delete the images from your portal folder (which 99.9% of users will do) the references to those images are still there in the portal.css file.

I'm wondering what kind of performance impact these image 404's are having on my site?  The text/html module that used the images is gone so the images shouldn't be loading anyway but the site analyzer seems to show that the server is still having to work to locate these images because they are in the portal.css file.  Not sure how that works.

Thanks for the reply Mitch.  I've cleaned up all the orphaned references to the advertising images I threw away and, at least with regards to the analyzer I'm using, my page load speeds are faster.

Still kind of curious as to why DNN chose to reference this files in the portal.css file.

Hi Rodney, I'm still trying hard to have my static files to be compressed and cached with expiry using PageBlaster...mind to share your settings? According to my IIS, I've IIS default compressor installed and the output should have been compressed, but seems that PageBlaster is overwritten the configuration and uses PageBlaster staticfilehandle compression instead...but Google PageSpeed detected those image files are not compression still...

---

Thanks,
George

Where to eat? Visit GoEatOut for Food Promotion in Kuala Lumpur.