We installed the WP Super Cache WordPress plugin on a client’s WooCommerce store last month, and the homepage load time dropped from 4.2 seconds to 1.6. No server migration. No theme swap. Just a free caching plugin doing what it was built to do.
If your WordPress site feels sluggish, pages loading like it’s 2009, visitors bouncing before they even see your headline, caching is almost always the first fix worth trying. WP Super Cache is one of the oldest and most downloaded caching plugins in the WordPress ecosystem, maintained by Automattic (the company behind WordPress.com itself). And yet, we still see site owners skip it or misconfigure it because the settings panel looks intimidating. This guide walks you through what the plugin actually does, how to set it up properly, and how to confirm it’s working.
Key Takeaways
- WP Super Cache converts dynamic WordPress pages into static HTML files, reducing server response time by 50–70% on typical shared hosting.
- The Simple caching method is recommended for most business sites, delivering roughly 80% of the speed benefit with minimal configuration.
- Installation and basic setup of the WP Super Cache WordPress plugin takes about five minutes — enable caching, turn on gzip compression, and activate cache rebuild for best results.
- Always exclude WooCommerce cart, checkout, and account pages from caching to prevent visitors from seeing incorrect prices or items.
- Verify the plugin is working by checking the page source in an incognito window for the “Cached page generated by WP-Super-Cache” comment and testing TTFB with tools like GTmetrix.
- Caching addresses server processing time only — image compression, script optimization, and database cleanup are separate steps you should tackle after caching is in place.
What WP Super Cache Does and Why It Matters
Every time someone visits a WordPress page, your server runs PHP code, queries the database, assembles the HTML, and sends it to the browser. That round trip takes time. WP Super Cache short-circuits the process by saving a static HTML copy of each page. The next visitor gets that pre-built file instead of forcing the server to rebuild everything from scratch.
Here is why that matters for your business: Google uses page speed as a ranking signal. A slow site pushes you down in search results. Visitors also vote with their feet, studies from Google consistently show that bounce rates climb sharply once load times exceed three seconds.
WP Super Cache supports three caching methods:
- Simple (recommended): Serves static HTML files through PHP. Easy setup, compatible with most hosts.
- Expert (mod_rewrite): Serves cached files directly through Apache, bypassing PHP entirely. Fastest option, but requires .htaccess access.
- WP-Cache: The legacy method, slower than the other two but useful in edge cases.
For most small business sites, the Simple method gives you 80% of the speed benefit with almost zero configuration headaches. If you want to compare this plugin against other options, we wrote a detailed breakdown of the best WordPress cache plugins and where each one fits.
One thing WP Super Cache does not do: it won’t minify your CSS, lazy-load images, or clean up your database. It solves one problem, server response time, and it solves it well. For the full maintenance picture, our WordPress caching and database cleanup playbook covers the rest.
How to Install and Configure WP Super Cache
Getting the plugin running takes about five minutes:
- Go to Plugins → Add New in your WordPress dashboard.
- Search for “WP Super Cache.”
- Click Install Now, then Activate.
- Navigate to Settings → WP Super Cache.
- Select Caching On and hit Update Status.
That is literally it for the basics. Your site is now serving cached pages.
But the default settings leave performance on the table. Let’s tighten things up.
Recommended Settings for Most Business Sites
Under the Advanced tab, we turn on these options for nearly every client site:
- Cache hits to this website for quick access. ✅
- Use mod_rewrite to serve cache files. ✅ (if your host supports it, most Apache-based hosts do)
- Compress pages so they are served more quickly to visitors. ✅ (enables gzip compression)
- Don’t cache pages for known users. ✅ (keeps logged-in dashboard users from seeing stale content)
- Cache rebuild. ✅ (serves a stale cached page while building a new one, so visitors never hit a slow uncached load)
Leave the Preload tab alone unless you have a specific reason. Preloading generates cached files for every page on a schedule, which sounds great but can hammer smaller shared hosting plans. If you run a site with fewer than 500 pages, the on-demand caching from the settings above handles things fine.
For WooCommerce stores, make sure cart, checkout, and account pages are excluded from caching. WP Super Cache usually detects these automatically, but double-check under Advanced → Accepted Filenames & Rejected URIs.
If you are evaluating whether a different caching approach fits your stack better, our article on W3 Total Cache breaks down how a more feature-heavy plugin compares. And for sites on LiteSpeed servers, the LiteSpeed Cache plugin is usually the better match since it ties directly into the server software.
Testing Your Cache and Measuring Results
Configuration means nothing without verification. Here is how we confirm WP Super Cache is doing its job:
Step 1: Check the source code. Open your site in an incognito browser window (important, logged-in users bypass the cache). Right-click the page, select “View Page Source,” and scroll to the bottom. You should see a comment like:
<.-- Dynamic page generated in 0.123 seconds. -->
<.-- Cached page generated by WP-Super-Cache on 2026-03-01 -->
If that comment is missing, the cache is not serving.
Step 2: Run a speed test. We use Google PageSpeed Insights and GTmetrix. Test the same page twice, the first load may be uncached, but the second should be noticeably faster. Pay attention to Time to First Byte (TTFB). A cached page should bring TTFB under 200ms on decent hosting.
Step 3: Compare before and after. If you took a baseline measurement before installing the plugin (and we always recommend you do), compare those numbers. On a typical shared hosting plan, we see TTFB drop by 50–70% with WP Super Cache enabled.
For a broader look at how caching plugins compare on real performance metrics, that breakdown covers TTFB, LCP, and INP across three popular options.
Common Issues and How to Troubleshoot Them
WP Super Cache is stable, but caching plugins can still cause headaches. Here are the issues we see most often, and how to fix them.
Problem: Changes to the site don’t show up.
This is the number one support question. You update a page, refresh, and the old version is still there. The fix: go to Settings → WP Super Cache and click Delete Cache. For a more detailed walkthrough, our guide on clearing your WordPress cache covers every method.
Problem: The plugin shows a “mod_rewrite rules were not updated” warning.
This usually means your .htaccess file is not writable. Check file permissions (644 for .htaccess) or switch to Simple caching mode if your host restricts .htaccess edits.
Problem: WooCommerce cart shows wrong items or prices.
Cart and checkout pages should never be cached. Verify they are listed under the rejected URIs in the Advanced settings. Add /cart/, /checkout/, and /my-account/ manually if they are missing.
Problem: Conflicting plugins.
Running two caching plugins at once causes unpredictable behavior. If you previously used a different WordPress cache plugin, deactivate and remove it before enabling WP Super Cache. One caching layer is all you need.
Problem: Pages load slowly even with caching on.
Caching only addresses server processing time. If your images are 3MB each or your theme loads 14 JavaScript files, those issues live outside the cache. That is when you need a broader performance audit.
Conclusion
WP Super Cache does one thing, it turns dynamic WordPress pages into static files, and it does that one thing reliably. For most business sites running on shared or managed hosting, it is the simplest path to a faster TTFB and better Core Web Vitals scores without paying for a premium plugin.
The setup takes five minutes. Testing takes another five. And the performance gains stick around as long as the plugin stays active. If your site still feels slow after caching, the next steps are image compression, script optimization, and database cleanup, but caching comes first. Always.
If you want a hand auditing your WordPress speed stack or choosing the right caching setup for your hosting environment, we are happy to help. Reach out to our team at Zuleika LLC for a free consult.
Frequently Asked Questions
What does the WP Super Cache WordPress plugin actually do?
WP Super Cache converts dynamic WordPress pages into static HTML files. Instead of your server running PHP and querying the database for every visitor, it serves a pre-built copy of each page. This dramatically reduces server response time, often cutting Time to First Byte by 50–70% on shared hosting.
How do I install and configure WP Super Cache?
Go to Plugins → Add New in your WordPress dashboard, search for WP Super Cache, click Install Now, then Activate. Navigate to Settings → WP Super Cache, select Caching On, and hit Update Status. For better performance, enable mod_rewrite caching, gzip compression, and cache rebuild under the Advanced tab.
Which WP Super Cache caching method should I use?
For most sites, the Simple method offers roughly 80% of the speed benefit with minimal setup. If your host supports Apache and .htaccess access, Expert (mod_rewrite) mode is faster because it bypasses PHP entirely. The legacy WP-Cache method is slower and only useful in rare edge cases.
How do I verify that WP Super Cache is working on my site?
Open your site in an incognito browser window, right-click the page, and select View Page Source. Scroll to the bottom and look for a comment containing “Cached page generated by WP-Super-Cache.” Then run a speed test with Google PageSpeed Insights—your second load should show TTFB under 200ms on decent hosting.
Is WP Super Cache safe to use with WooCommerce?
Yes, but you must exclude dynamic pages like /cart/, /checkout/, and /my-account/ from caching. WP Super Cache usually detects these automatically. Double-check under Advanced → Rejected URIs and add them manually if missing. Failing to exclude them can cause visitors to see incorrect cart items or prices.
Can I use WP Super Cache alongside another caching plugin?
No. Running two caching plugins simultaneously causes conflicts and unpredictable behavior. Deactivate and remove any existing cache plugin before enabling WP Super Cache. If you’re deciding between options, comparing popular caching plugins side by side can help you pick the right one.
Some of the links shared in this post are affiliate links. If you click on the link & make any purchase, we will receive an affiliate commission at no extra cost of you.
We improve our products and advertising by using Microsoft Clarity to see how you use our website. By using our site, you agree that we and Microsoft can collect and use this data. Our privacy policy has more details.