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

I thought I did that, maybe I did it wrong. Attached is a SS of how I published, then I copied the resultant directory to my web server via FTP.



Am I lost?





Keith Chisarik

No.  It generally this will work.  You might try the manual option.  Now keep in mind that the very first visitor after IIS has been restarted might take just a second to load the site.  However, after this it should always be fast.  You can be the "first visitor" to make sure the site is loaded.  Afterwards though, it should be fast for all other visitors.

Pre-compiling the website is supposed to fix the 1st page load slowdown because the when the page is stale, it has to be recompiled. 

However, if you're still getting very poor responsiveness for the first page request, you can try some other things:

1) Put the website in it's own application pool
2) Place a standard .html file in the site and see if it takes as long as the .aspx pages do