Using the "WP Super Cache" WordPress plugin
WP Super Cache is a WordPress plugin that dramatically speeds up the performance of WordPress sites. Installing it is one of the steps we recommend for improving WordPress performance.
On this page:
- Activating WP Super Cache
- Configuring WP Super Cache
- Other configuration tips
- Looking for even better performance?
- Don’t enable “preload mode”
- Enabling WP Super Cache for a domain name alias with mod_rewrite
- What about W3 Total Cache?
Activating WP Super Cache
The plugin can be activated from within the WordPress “Dashboard” admin pages.
If you used our WordPress “one click installer”, the plugin is already part of your site and just needs activating:
- Click Plugins.
- Locate the line for the “WP Super Cache” plugin.
- Click Activate Plugin.
If you installed WordPress yourself (without using our installer), do this instead:
- Click Plugins.
- Click the Add New button.
- Search for the term WP Super Cache, then click Install Now when you find it. After installing it, you’ll be told that WordPress “Successfully installed the plugin”.
- Click Activate Plugin.
Configuring WP Super Cache
You should verify that the WP Super Cache settings are correct after activating it:
- Click Settings on the left side of the WordPress Dashboard.
- Click WP Super Cache under the Settings.
- Click the Advanced tab to set the caching options.
It will look like there are lots of options, but actually, configuring it is easy: simply choose all the “recommended” options that you can check, and leave everything off that’s not marked “recommended”.
In particular, do check these options unless you have a good reason not to:
- Cache hits to this website for quick access.
- Use PHP to serve cache files.
- Compress pages so they’re served more quickly to visitors.
- 304 Not Modified browser caching. Indicate when a page has not been modified since it was last requested.
- Don’t cache pages for known users.
- Cache rebuild. Serve a supercache file to anonymous users while a new file is being generated.
- Extra homepage checks. (Very occasionally stops homepage caching)
And don’t check anything else unless you have a good reason to do so. It should look like this (we’ve highlighted the recommended settings for you):
When you’ve set things that way, click “Update Status” to save the changes. You’re finished!
If you prefer, we’ll be glad to install WP Super Cache for you, at no charge, on any copy of WordPress. Just contact us.
Other configuration tips
When you configure the WP Super Cache settings, do not check the box marked “Clear all cache files when a post or page is published”. Using that checkbox effectively disables WP Super Cache for a few minutes every time you create a new post.
Our instructions above recommend Use PHP to serve cache files because it's simple to setup. The “Use mod_rewrite to serve cache files” option is slightly more efficient on very busy sites, but harder to configure. It can be used if you absolutely need the extra speed.
Looking for even better performance?
If you didn’t use our “one click installer”, this tip will help (our installer already takes care of it): If your site doesn’t display different content when search engine robots index it, and you care about how quickly Google and other search engines think your pages load (you should), you can remove “bot, ia_archive, slurp, crawl, spider, Yandex” from the “Rejected User Agents” section of the Advanced settings — just make that space blank. This helps search engines get the same speed benefits.
We also recommend increasing the “Cache Timeout” to 172800 seconds in the “Expiry Time & Garbage Collection” section of the Advanced settings for the reasons described here, even though it suggests setting it lower for a busy site.
Don’t enable “preload mode”
WP Super Cache offers a feature called “preload mode”. However, this feature disables automatic removal of old cached files, causing outdated pages to appear in some cases. This happens especially on the non-primary hostname of your site — for example, if WordPress thinks your site is at “www.example.com”, preload mode can cause outdated content to appear at “example.com” without the “www”.
For this reason, we don’t recommend using preload mode.
Enabling WP Super Cache for a domain name alias with mod_rewrite
If you use the “Use mod_rewrite to serve cache files” option, and you enable WP Super Cache using a URL that’s a domain name alias, four of the lines that WP Super Cache adds to your .htaccess file may be incorrect. This is caused by a WP Super Cache bug.
Specifically, if your .htaccess file contains “/var/www/html/ex/example.com” in the RewriteCond and RewriteRule lines that were added, that extra text is wrong and should be removed. We can help you troubleshoot and fix this problem if you contact us.
What about W3 Total Cache?
“W3 Total Cache” is a plugin that tries to do the same thing as WP Super Cache. However, we’ve found that it’s harder to use and sometimes doesn’t give the same performance. Stick with WP Super Cache unless you have a good reason to switch. If you do use it, be sure to use our recommended W3 Total Cache settings.