Hi Rick,

>When you say every time, what does that mean? Every hit or every time you get to the site?

I guess I wasn't very clear and actually wasn't sure myself. It seemed like every time I went to the site, but today I have been going there constantly to see how it responds. It is better when I access it often. Because of this, it may very well be what you suggest below. I will try to monitor it on a time slot and see if I can figure out if on a consistent time.
Thanks
Tim

>Most likely what's happening is that your IIS Application Pool is unloaded. If that's the case IIS has to spin up a new Application Pool (an Exe), initialize it, Initialize ASP.NET then recompile your application adn then finally run it.
>
>Once up however the application should run fast. I suspect if you have only those few precompiled files you indicate there should be nearly no overhead for JIT compilation...
>
>All the slowness comes from first time load of the infrastructure.
>
>Application Pools are by default configured to time out after 20 minutes which unloads the EXE that hosts the pool. This is configurable and you can set this to never time out. If you're hosted at an ISP though you won't have choice about this and they may actually have the timeouts set even lower to reduce resource usage. In that case you can set up some ping code (in ASP.NET itself to 'ping itself') or use an external tool to hit the site every few minutes to keep the application pool alive.
>