ASP.Net Web Application

I currently have an asp.net web application that has a data access and business logic layer (3-tier). In the beginning the application scaled fine and ran very well, now since the application has quadrupled in size, users are experiencing timeouts on the webpages.

 I think this is due to the fact that the save methods the page calls have grown quite a bit, and does many things in the database. When I run the methods from a dos prompt in a console app from the business logic layer they run fast and do not timeout. I think this is happening because the page is waiting for the transaction to complete, but i'm not sure.

Is there any way I can seperate the transaction from the page once the user hits the save button? And is there anyway to do this without an architecture change?

 

Thanks,
JT
...