Hi Everyone, I am still in the process of populating this site The site takes a very long time to load, even before it had no content in it. Is the skin slowing it down? thank you in advance

I took a look at your site.  Once the site loads initially, and once individual pages have loaded once, then the site responds quickly.

This is the standard behavior with ASP.NET sites, and not just DotNetNuke.  ASP.NET has to load and compile the site.  If your traffic is low, and depending on how your web server is configured, your site may get unloaded.  Then, when you go back to the site, you have to wait through the initial loading again.

The trick here is to keep your site loaded.  If you control your web server, you can configure it NOT to unload.  If you don't control it, you need to use a "keep-alive" service to hit your site on a regular basis to keep it loaded.  Generally, keep-alive services hit the site every 5 minutes.

You should also configure the Performance Settings (under Host Settings) for best performance. Look at this link for a current description of increasing the performance of DotNetNuke sites.

Hi Joe,

I refer to your statement "ASP.NET has to load and compile the site. If your traffic is low, and depending on how your web server is configured, your site may get unloaded."

I'm currently experiencing the same issue on a particular site hosted by our own company. And it only happens randomly to random users across my country and the issue is that the home page of this .aspx site takes forever to load.

I do not really understand by the trick that you have mentioned "keeping your site loaded", how do I get about configure it to "keep alive" and "keeping it loaded" in the web server?

Help me as soon as you read this post..

really appreciate it!

Thanks in advance.

If you Google "keep alive" you will find lots of services that will ping your site on a regular basis.  These all work by sending requests to your site.  If these happen sufficiently often - 5 to 10 minutes - your site will have enough traffic to keep is from being unloaded.

I use a program (purchased, I believe, through Snowcovered) that I use on one of my computers to do this. 

Hello. I do control my server. Since reading this I have been searching how to do this. Could you help me understand better? My DNN 5 intranet site (not yet in production) runs on Server 2003 R2, IIS 6, ASP.net 2.0. I am running Active Directory Provider, if that matters. I would think this is a setting in IIS and I see on the properties of my site Connections timeout and Enable HTTP keep alives. Am I in the right neighborhood? Doxey

IF you look for "Keep alive" services, that is the easiest approach.  These services will hit your site frequently so that the site is not unloaded.

You can also configure IIS to not unload the site.  I think that having DNN running in its own application pool is advisable if you choose this option.

If your problem is page to page loading times, you might want to look at Mitchel Sellers' Blog for tips on getting the best performance out of DotNetNuke.

You may also want to have a look at:
Performance Tips - Fast Site - Keep Alive Tools - Hosting

It would be really great if the tip above links to the actual article. It takes me a page with a bunch of articles.

And ... http://www.iowacomputergurus.com/wh...apers.aspx