WordPress Hyper Cache 2.0 Plugin · English

Because of the Yandex.Fotki plugin, which connects to Yandex—a service that is slow to respond to external connections—I needed a caching plugin.

I was familiar with three candidates:

After some Googling, I concluded that Hyper-Cache suited me better, since it caches pages and queries, but only for guests. And since I don’t have registration enabled on my blog, I don’t need caching for logged-in users.

For anyone that doesn’t suit, I recommend taking a look at Wp-Super-Cache.

Installation

lecactus has described how to install this plugin, so I won’t repeat it…

By the way, it’s best to enable caching before the block

 if ( !defined('ABSPATH') )
       define('ABSPATH', dirname(__FILE__) . '/');
    require_once(ABSPATH . 'wp-settings.php');

That’s what it says here, at least… In other words, we’ll end up with:

define('WP_CACHE', true);

 if ( !defined('ABSPATH') )
       define('ABSPATH', dirname(__FILE__) . '/');
    require_once(ABSPATH . 'wp-settings.php');

Configuration

Again, I won’t repeat lecactus… There really is nothing complicated about it.

The main thing to remember here is that if you’re currently logged in, pages won’t be cached for you, which confused me after installation :) Just open another browser (without logging in) and test the cache there. The plugin’s admin panel has an item showing the number of cached pages; that number should keep going up!

After enabling Hyper-Cache, I started getting a response in 0.3 seconds (with Yandex.Fotki), compared with 1.7 seconds (without Yandex.Fotki) and 7 seconds (with Yandex.Fotki). I measured this using the http://tools.pingdom.com/ service.