Caching of .ASP pages

[indigojo]

We run a site that contains around 7000 articles and pulls in around 1.5 million visitors per month. The site runs on a shared hosting environment which until today ran fine. Our host decided to scale back our sites capablities which is causing lots of time out errors. They suggested that we were using a vast majority of the webserver (not SQL server) CPU's usage.

Below is some of what they have had to say

+++++++++++++++++++++++++++++++++++++++++++++

We do not provide dedicated servers. Our service is all shared hosting. When we see this issue we also suggest to customers that its not so much the traffic to the site, but the design and the backend processing that your asp/.net pages are doing. The webserver itself can handle a large quantity of traffic, but its the processing of the scripts that kills the site with these timeout errors. You might want to also see if you can cache some of your results instead of pulling them from the database and this will greatly spead up your web application.

+++++++++++++++++++++++++++++++++++++++++++++

You need to realize that you are hosting your website not on a dedicated server, but in a shared hosting environment with about hundred other websites. In the shared environment all sites have a set limit on how much resources they can consume. This allows us to keep a good level of service for all customers on the same server.

+++++++++++++++++++++++++++++++++++++++++++++

They are suggesting that we rewrite our code to cache content. I am not familiar with this. Does anyone have any pointers or suggestions before we switch to a dedicated host. I'm loathed to lose our IP address as this hurt us badly once before with Google etc