Getting shut down by your hosting provider
The sudden increase of traffic can cause some alarm bells to go of at your hosting provider. Some server administrators will mistake the ridiculously high hits on your site for a DDoS attack and take your site offline.

You can prevent this from happening by letting your hosting provider know that a page from your site made the front page of Digg. This is, of course, providing you know you have been Dugg.

Another reason, your web hosting provider might have, to take your site offline, is that your account has used up it’s available traffic resources. A page with only a few images and scripts can easily add up to a few hundred kb of data being transferred on a single page load.

Looking at my website statistics, it seems that my average page size is about 35 KB. If I would be running on a hosting account with a 10 GB a month data limit, I would be able to serve about 285.000 pages a month. That is plenty for most sites, but being on the front page of Digg can drive crazy amounts of visitors to your site, which can chew up your 10 GB plan in no time.

But there is something that can be far worse than having your site taken offline for reaching the bandwidth limit: it’s having your site stay online after using up your monthly bandwidth and

being presented with a bandwidth over usage bill.
Most hosting providers have ridiculous fees for any bandwidth you use on top of what’s included in your hosting plan. This happened to me last year. One of my dedicated servers used more than the plans bandwidth. The bill I was presented was quite high, but I managed to get the hosting provider to cancel the bill.

Having your site shut down or being billed extra can be easily avoided. In case the billing or shutdown would be caused by exceeding your hosting plans allowed amount of traffic, you can simply make your pages smaller. Avoid over usage of images, as they are the biggest items on any page, byte size wise. The images used on your page could be saved with a little higher compression ratio or you could offload the images to a different hosting account to share the bandwidth load. If you don’t have a second hosting account, you could host the images on a free image hosting site, there are plenty of free ones available to you.

It is also very common to have your hosting account disabled for using to much of the servers resources. This won’t happen on a dedicated server, but if you are on a shared hosting account, they can shut your site down for putting too much stress on the servers processor, which will affect other clients websites hosted on the same server. This too is easy to avoid. Have a look at your WordPress blog. Everything is stored in a database. The blog title, the tagline, the post title, the post text, the categories, the tags and much more.

When a page is requested for viewing, the software will read all the necessary information from the database. Compiling a single page involves running a lot of queries. Your web server is good at running queries and retrieving the needed information from the database at lightning speeds, but there are limits. With a few dozen page requests every second, the server will soon have trouble keeping up. Remember that there can easily be over a hundred other websites running on the same server.

Running all these queries to build a single page is not really necessary though, once the page has been created by the php code, it can be stored as a static html file. The next visitor can be presented with the html output directly, which probably uses at least 90% less processing power. Don’t worry if this sounds a bit too technical to you, there is an easy way to implement this method in your WordPress blog, its called caching and there is a nice plugin available: WP Super Cache by Donncha O Caoimh

Don’t wait implementing these until you hit the front page of Digg. Once you are on the page, there will not be much you can do. These measures should be in place before the traffic avalanche hits you. Even if it never happens, it’s better to be save than sorry. So, be prepared!