Skip to content
Mar 6 / kkrizka

Make Sure You Have The WP-Cache Plugin

If you tried to access my blog yesterday, you might have been greeted with an “Account Has Been Suspended” error that took several hours to resolve. It turned out that my blog started using up more resources than was allocated to it, and so the LovingHosting auto monkey automatically suspended my domain. After several hours of waiting, the LovingHosting support staff told me that their servers might not be adequate to handle the load on my website and I might want to look for a different host, preferable a Virtual Private Server.

I found this quite weird, because I only get a bit above 1000 unique visitors every day. Such a small load should not overload a server, but it might but a bit of strain on it. One problem I did notice after a bit of investigation was that I did not have the WP-Cache plugin enabled. This means that every page someone visits will be regenerated everytime, which does take up a lot of resources especially if you have a lot of plugins enabled. The wp-cache plugin generates a page only once, saves it to the disk, and sends that static page to the visitor. This is a very efficient process for a blog, because most posts are just static pages, rarely ever edited.

So are you running the wp-cache plugin? You can check by logging into your WordPress admin page and clicking onto the Plugins tab. Then just search the page to see if it is enabled or not. If you find that it is enabled, you also have to go into the Options tab and look for the WP-Cache subtab. There is another button you have to press to enable it.

If you do not find it in the Plugins tab, then what are you waiting for? Download the wp-cache2 plugin from its official website, upload it into the wp-content/plugins directory of your blog and enable it! It will help you keep your blogrunning fast and avoid pissing off your hosting company.

For now I will be staying with LovingHosting, because their support has been quite excellent so far.Yesterday’s delay was a rare exception, and it should not happen again now that I have the wp-cache plugin.

Leave a comment