The case:
I have a 3-tier app, which caters to specific services for my company's Intranet.
Here, as the Browser makes the very first request to the site, the AppServer
runs a lot of initialisation routines, does quite a few database trips and
presents the first page. So the first page loading is really slow, while
consecutive browsing of the site is pretty fast.

The problem is, majority of my Users, when opening up the website casually,
fires up the session-specific initialisation process of the Appserver, and
then impatiently closes the browser window or visits another URL. This puts
a great unnecessary stress on the Appserver. Is there a way I could put a
check and arrest/kill the unnecessary running/firing of init process of the
appserver, by sensing the Browser Window's events (closing the window or
visiting some other url) - that would save a lot of processing power and
speed up my application too.

Any further questions, suggestions and expert comments would be cordially
welcome.

Thanks in advance.