I just published a SF/SQL website and the first time a visitor goes to the site, the pages are slow to load. My understanding of this is because the HTML is dynamically rendered in ASP.NET and the first time it essentially just takes longer.



Is there any way to speed this up other than throw hardware at it?



The initial pages are not complex but still take 3-10 seconds to load the first time, subsequent visits are much faster but I think this still leaves the wrong initial impression.



Any help or insight will be appreciated.

Keith Chisarik

Another option I find helpful is to disable idle timeouts on the Application Pool in IIS.  Do that under the Performance tab of the Application Pool.  Either uncheck the idle timeout checkbox or set it to a higher value.  I have noticed that over weekends where I work the IIS worker processes will shutdown making our ASP.NET websites slow to load on Monday morning.  By removing the idle timeout we don't have to worry about it.  I would not recommend doing this to the Default pool though so create a new pool, add your site to that pool, and remove the idle timeout.