Why We Switched from WP Super Cache to Quick Cache (and What to Use Now)

Back in February 2012 we switched our main caching plugin from WP Super Cache to Quick Cache. This post keeps that story and the setup tips we learned, and adds what happened to Quick Cache since and which WordPress caching plugin makes sense in 2026.

Quick answer: We left WP Super Cache in 2012 because of server-specific bugs that stopped us clearing the cache, and moved to Quick Cache, which worked out of the box. Quick Cache was later renamed ZenCache and then Comet Cache and is no longer listed on WordPress.org. WP Super Cache is still free and maintained, and remains a simple, safe choice today.

Why We Moved Away from WP Super Cache

We had used WP Super Cache for over five years, and it is one of the best caching plugins around. But after one release we hit bugs on our own server and could not delete the cache. Logging in by FTP to clear it by hand got tedious, and reinstalling the plugin brought strange 403 errors. It was time to try something else.

These were isolated issues on our server. WP Super Cache is an excellent plugin, hugely popular and widely recommended.

Why Every WordPress Site Needs Caching

A caching plugin is one of the most important plugins for a WordPress blog. It saves PHP-generated pages as static HTML files, which cuts server load, keeps pages loading even when the server struggles, and helps your site survive traffic spikes on shared hosting.

I looked at W3 Total Cache with a CDN such as Amazon CloudFront (which we already used for some static files), but its many options were overwhelming. The forums were full of praise for Quick Cache, so I gave it a try.

Setting Up Quick Cache (2012)

Quick Cache worked out of the box. You simply activated it and turned caching on. Most sites, including ours, did not need to change any other setting.

Quick Cache WordPress plugin settings screen

  • Cache expiry: we raised it from the default 3600 seconds (1 hour) to 36000 (10 hours) because our content did not change often.
  • Logged-in users: pages were not cached for admins and known users, so you had to log out to see caching work.
  • Smart clearing: editing a post refreshed only that post, and comments refreshed their page. A clear cache button handled the rest.
  • Cache files: WP Super Cache mirrors your site structure in its cache folder, while Quick Cache stored pages as MD5 hash files.

Gzip compression with Quick Cache

Unlike WP Super Cache, Quick Cache had no gzip option. Its FAQ suggested two manual methods. The .htaccess mod_deflate method did not work for us, but the second did, because our host had zlib installed. We created a file named php.ini in the site root containing:

zlib.output_compression = on

Pages were then compressed, which we confirmed with an HTTP compression test tool. Today most hosts compress pages at the server level, so check with yours before adding this.

What Happened to Quick Cache

Quick Cache added a Pro version in 2013 (see our post on the Quick Cache Pro update), then was renamed ZenCache and later Comet Cache. We wrote about moving from QuickCache to ZenCache at the time. The original plugin is no longer available on WordPress.org, so don’t install old copies.

WP Super Cache and Other Choices in 2026

  • WP Super Cache: free, simple and maintained by Automattic. A good default on most shared hosts.
  • LiteSpeed Cache: the best fit if your host runs a LiteSpeed web server. QOT uses it today.
  • W3 Total Cache: powerful with many options, better for people who like fine control.

Use only one page caching plugin at a time, and check whether your host already provides caching. For more speed tips, see how to make WordPress faster and safer, and note that caching can delay RSS feed updates.

FAQ

Is WP Super Cache still good in 2026?

Yes. It is free, maintained and easy to set up, which makes it a solid choice for most small and medium blogs.

Can I still download Quick Cache?

No. Quick Cache became ZenCache and then Comet Cache, and the original plugin is no longer offered on WordPress.org.

Should I run two caching plugins together?

No. Two page caching plugins can conflict. Pick one, and add a CDN separately if you need it.

Why don’t I see cached pages when logged in?

Most caching plugins skip caching for logged-in users by default. Log out or use a private window to test.

Found this useful? Share it with someone who needs it.

Get our free weekly email: new tech guides and tools, no spam.

New and updated tech guides, a free tool worth bookmarking and one useful pick, once a week. No spam, unsubscribe anytime.

One email a week. Unsubscribe anytime. See our privacy policy.

Related Tech Guides

Leave a Reply

Your email address will not be published. Required fields are marked *

9 Comments

  1. I will be staying with WP Super Cache. The problem with Quick Cache is that it does not cache compressed files. Even if a page is cached, it is still compressed on the fly for every connecting user, which is bound to increase your server load. COmpression is highly CPU intensive.

    Super Cache on the other hand just does the compression once, then just sends the same gzipped file each time. My testing shows that fetching a compressed page with QC actually takes longer than fetching the uncompressed page. Turn on compression with Quick Cache and your blog may actually slow down.

    Cheers,
    Jim

  2. I was looking for a caching plugin, I think the newest one i.e Hype Cache is one of the best and the fastest!

  3. how to remove some pages from caching from w3 super cache plugin.
    is it required mod rewrite??

  4. Using Cloudflare for caching purposes has served far more helpful than any wordpress plugin.

  5. WP Super Cache is my first choice and I’m using this plugin from the very beginning of my blogging

  6. Quick cache is what I use, it handles more traffic , faster, more sturdy, lighter on cpu and ram.
    I used W3 Cache for over a year, then switched to super cache for a year or so. Been using Quick Cache for over a year too. It really depends on your environment, so you have to see for your self which is the good one. They’re all top cache plugins. But Quick Cache to me is the best!
    W3 Cache and SuperCache have crashed on my site a few times but never with Quick Cache.

  7. Daniel – its an isolated issue which we have not been able to fix. We have successfully used Supercache for over 5 years and it is very good.

  8. At the moment, I have not got any issue with SuperCache. Honestly, I have just switched from W3 Cache since the hosting provider staff recommended that. I also have no problem when trying to delete cache.