Installing WP Super Cache

WordPress is a popular tool that generally works very well to run your website.

However, once your site begins to receive a significant amount of traffic, you may notice that WordPress runs less efficiently. This is because whenever a page is visited, it must be processed by PHP and then served via Apache which can consume vast amounts of memory if your site gets even a moderate traffic spike.

Installing a cache plugin can help cut down on memory usage by serving cached static files instead of requiring each request to retrieve the same information from the server. This also helps your site survive large traffic spikes and keep it up and running in DreamHost's shared hosting environment.

View the WordPress caching options page for further details.

Configuring WordPress permalinks

WP Super Cache requires the use of permalinks.

When configuring permalinks within WordPress, you’ll notice several options available. Please note that all permalink settings work with WP Super Cache except for the default settings.

To change the default settings:

  1. Go to your WordPress dashboard (example.com/wp-admin).
    01 WP Super Cache.fw.png
  2. Navigate to ‘Settings -> Permalinks’.
    Any of the options aside from Default will work, so your settings should look something like this:
    02 WP Super Cache.fw.png
  3. Click the Save Changes button to save your new settings.

Setting up WP Super Cache

Before you install WP Super Cache

If you have previously installed any other caching plugin, you should deactivate and remove it. In general, double caching is a bad idea and can create conflicts that could slow down your WordPress site. Known plugins that conflict are WP Cache and W3 Total Cache.

Make sure you remove them fully before installing WP Super Cache. This can be done from the WordPress Dashboard – click ‘Plugins’ on the left to view and edit your list of plugins.

Installing WP Super Cache

To install WP Super Cache:

  1. Download the WP Super Cache plugin via your WordPress Admin Dashboard at example.com/wp-admin.
    03 WP Super Cache.fw.png
  2. Once logged in, click ‘Plugins > Add New’.
  3. Towards the top right of the screen, search for WP Super Cache (or wp-super-cache).
    04 WP Super Cache.fw.png
  4. Click the Install Now button next to WP Super Cache.
    05 WP Super Cache.fw.png
  5. Click the OK button to save your changes.
    This will install WP Super-Cache and allow you to immediately activate it.
    06 WP Super Cache.fw.png

Activating WP Super Cache

To activate the WP Super Cache plugin:

  • Click the 'Activate Plugin' link on the installing page (see previous section), or
  • Go to the Plugins area of your admin dashboard (Plugins -> Installed Plugins), and then click the 'Activate' link.
When you activate the WP Super Cache plugin, the following appears:
07 WP Super Cache.fw.png
  • Click the ‘Settings’ link to open the WP Super Cache configuration page.
From there, adjust your settings to look similar to the following:
08 WP Super Cache.fw.png

WP Super Cache automatically adds the following line to your wp-config.php file:

define( 'WP_CACHE', true );

If it fails to do so, WordPress provides links to its own troubleshooting documents.

Verifying WP Super Cache is actually working

To test WP Super Cache:

  1. Open the WP Super Cache admin page.
    09 WP Super Cache.fw.png
  2. Click the Test Cache button which tests if WP Super Cache is functioning.
    The following appears when you click the Test Cache button:
    10 WP Super Cache.fw.png

Caching types

While WP Super Cache supports three modes, it defaults to PHP:

  • Mod_rewrite Mode
  • PHP Mode
  • Legacy Mode

You can change these in the ‘Advanced Settings’ tab:

11 WP Super Cache.fw.png

There are pros and cons to each option. However, in terms of performance or if your content is not going to change that often, you will most likely use mod_rewrite mode which speeds up the Time to First Byte (TTFB) by orders of magnitude. This is because it doesn't have to search for additional PHP handlers to parse the cached file. Instead, it writes the content as raw HTML, and then serves the HTML by itself.

If you're using NGINX, you'll want to use PHP Mode as opposed to Legacy.

mod_rewrite mode

If you switch to using mod_rewrite, you are prompted to update your .htaccess file:

12 WP Super Cache.fw.png
  1. Scroll down on the Advanced Page until see a large section with an orange background.
    Wpsc-updatemod.png
  2. Click the Update Mod_Rewrite Rules button.
    The following displays which tells you that your .htaccess file has updated:
    Wpsc-modsecwin.png

Page Speed Optimization

View the following article for further details:

Making WP Super Cache work with Nginx

With WP SuperCache you might want to put the four lines above right before the permalinks section. The following lines are just a snippet from a whole wordpress.conf file.

###### rest of wordpress.conf above...
###

# only rewrite to the supercache file if it actually exists
if (-f $document_root$supercache_file) {
  rewrite ^(.*)$ $supercache_file break;
}

### stats
if ($request_uri ~* ^/(stats|doc|failed_auth\.html).*$) {
  break;
}

# all other requests go to WordPress
if (!-e $request_filename) {
  rewrite ^.*$ /index.php last;
}

View the following article for further details

See also

Internal links

External links

Did this article answer your questions?

Article last updated .