Can your shared hosting survive from slashdotted? And what do you do to make yr site survive from slashdottedd?

1. Change your dynamic page to flat HTML.

If the page visitors are landing on is written in PHP, ASP, Perl, CFM, or anything besides HTML, change it. Simply go to the page and select (in Firefox) File > Save Page As. Put the HTML page into a new directory on your site and make sure that is the page people land on. You will have to edit the HTML to reflect the new location by making sure that the images and CSS still load and the links still work. If the landing page is a blog post or another interactive page, people will still be able to post comments if the form is targeted, but you will have to occasionally move the comments from the live version to the flat HTML version manually by viewing the source and copy-pasting.

By removing the scripting language and database from the page load, you鈥檝e probably done enough to buy yourself breathing room. If you can only do one thing to prepare, do this.

2. Move your images and CSS to a different hosting account.

If you have more than one hosting account, you can spread around the bandwidth usage by relocating the CSS and image files. Not only will you save on bandwidth by possibly avoiding overage charges, you will also speed up the load time by distribution. Remember, you only have to do this for the main page on which people are landing; you don鈥檛 have to make the changes site wide as most visitors will only view the first page.