>I have already posted kind of the same question a few weeks ago. And the customer and I still can't seem to find solution to the problem. He pre-compiled the application on the server. And still, a simple Hello World (no data connection) page takes over a minute to load. This is first time, then if you try to load it or any other ASPX page, it loads very fast. Then, if you wait for some time (an hour or so), loading of page is slow again.
>
>So this leads me to the following hypothesis. What if some .NET service only starts when a page is loaded first time? How would I verify this? What ASP.NET services should I see always in the list of Services? What should I watch for in the Services on the server when a user tries to load a page?
>
>Thank you in advance for any help.

Problem solved. The issue was the Application Pool Idle timeout setting that was shutting down the worker processes after being idle for 20 minutes. Actually Paul Mrozowski mentioned it to me in me previous thread on the same subject but I could not figure what he meant.

I went to the customer and by looking around their web server IIS settings found this. I created a separate Application pool for my application and set the Shutdown setting to 2000 minutes.

Thank you, Paul.