I check the loading time from www.alexa.com for some DNN sites. The result looks a little sad. Seems the loading time of DNN site is not good.

I am not sure the real reason of the slow loading time, but I guess this due to DNN need to load .NET component when page loads...This costs a lot of system resource.

I am not familier about the web programming but I think DNN can do some cheat process to improve the loading time.

This is just my guess, if it's wrong, just skip this post.

I guess the pure HTML page's load speed is much faster than normal DNN page(.aspx) because it doesn't need to load any module.

We can do some snapshot of the site's homepage to HTML format. Just like some kind of cache. I think this would greatly improve the first page's loading time. (I think this should be the current behavior of DNN site. But the loading time still make me has many question mark.)

DNN can first generate a HTML home page, when user sent request to webserver, we can response HTML page to it directly and generate the latest home page preparing for next time's request. (It doesn't need to generate home page every time becasue it's a kind of cache.)

This is the simple idea I got. I am not sure what the real reason DNN site is not good at loading time. If somebody knows please give me some idea about how to improve it.  I have set the host set the host setting according to the suggestion here.

PowerDNN:(fast  71%slower -> 29%), 1.4 seconds.

dotnetnuke.com :Slow (61%faster->39%), 3.0 seconds.

Tedallsearch.com: average(53%slower->47%)  2.3seconds.

Dnnskins.com: very slow(88% faster -> 88%) 5.9seconds.

coolcoolgame.com: very slow(91% faster -> 91%), 6.3 seconds.

Neoteo.com: Very Slow (98% faster-> 98%) 10.9 seconds.

mitchelsellers.com:Not available

The free PageBlaster does a lot to correct this problem.

DotNetNuke Performance Improvements using Free PageBlaster

Thanks for the feedback.  That looks like a problem that I may need to address. If you are using a different language the module is supposed to fall-back to the english version of that file unless you have created your own localized version.

For now, if you have installed the new module you can look in the DesktopModules/Snapsis/PageBlaster/Config/LocalStrings folder and find the PageBlasterConfig.LocalStrings[en-US].js file, then copy/rename it to

E:\inetpub\vhosts\mystestdomain.com\httpdocs\portals\_default\Cache\LocalStrings\PageBlasterConfig.LocalStrings[zh-TW].js

I'm not sure why it is looking in the Cache Folder for that local strings file, but it may be that you already had a Snapsis.PageBlaster.config file in your website root folder and that file may have had config-folder="portals/_default/Cache" as one of the settings.

If you are starting new, I would suggest coping the global default config file from  DesktopModules/Snapsis/PageBlaster/Config/default.config to your website root folder and rename it to Snapsis.PageBlaster.config