Troubleshooting
WP Fastest Cache Not Working: Causes and How to Fix It

Short answer
WP Fastest Cache usually looks broken because you are testing while logged in, Cache System is not enabled, the .htaccess file is not writable, or another cache layer conflicts. Test in a private window, check the page source and fix each cause in turn.
Key takeaways
- Logged-in admins see uncached pages by default.
- Look for the WP Fastest Cache comment in the page source.
- The Cache System box must be ticked and saved.
- The plugin needs a writable .htaccess and mod_rewrite.
- Run only one page cache and clear every cache layer.
Why is WP Fastest Cache not working?
WP Fastest Cache usually seems broken because you are testing while logged in, the Cache System option is off, the .htaccess file cannot be written, another cache plugin or host cache conflicts, or the page is excluded from caching.
Most of the time, the plugin is working and the test is wrong. Logged-in admins see uncached pages by default, so the site never looks cached to you.
The other common group of problems is server-related. WP Fastest Cache relies on rewrite rules to serve cached files quickly, and some servers block or ignore those rules.
Work through the checks below in order. Each one rules out a cause before you move to the next.
How do you check if WP Fastest Cache is working?
Open the page in a private window while logged out, view the page source, and scroll to the bottom to look for a WP Fastest Cache comment saying the cache file was created.
- Log out, or open a private or incognito window.
- Visit a normal page, such as a blog post.
- Reload it once so a cache file is created.
- Press Ctrl+U (Windows) or Cmd+Option+U (Mac) to view the source.
- Scroll to the end and look for a comment mentioning WP Fastest Cache.
If the comment is there, caching works. If it is missing, keep reading.
You can also check response headers in your browser's DevTools Network panel. Headers from a host cache or CDN may show that another layer is serving the page instead.
Is the Cache System option turned on?
Go to Settings > WP Fastest Cache, make sure the Cache System checkbox at the top is ticked, then click Submit, because the plugin does nothing until that main option is saved.
New installs sometimes have the plugin active but caching off. Activating the plugin alone does not start caching.
While you are on that screen, review the other options:
- Preload builds cache files in advance.
- Logged-in Users controls whether logged-in visitors see cached pages.
- Mobile controls whether mobile visitors get the desktop cache.
- New Post and Update Post control when the cache clears.
Our guide to WP Fastest Cache settings explains each option in detail.
Is the .htaccess file writable?
WP Fastest Cache writes rewrite rules into your .htaccess file, so if the file is not writable, missing or overwritten by another plugin, cached pages are not served correctly.
The plugin usually shows a warning when it cannot edit .htaccess. Look for notices at the top of its settings page.
To fix it:
- Connect with your host's file manager or SFTP.
- Find .htaccess in the WordPress root folder.
- Set permissions to 644 so WordPress can write to it.
- Go back to Settings > WP Fastest Cache and click Submit again.
- Open .htaccess and check that a WP Fastest Cache block was added.
If you edit .htaccess by hand, read how to edit the htaccess file in WordPress first. A small typo can take a site offline.
These rules need the Apache mod_rewrite module. Most hosts enable it, but if yours does not, ask support to turn it on.
Does WP Fastest Cache work on Nginx?
Nginx ignores .htaccess files, so the WP Fastest Cache rewrite rules do not apply there and cached pages may be served more slowly or not at all unless your host adds equivalent rules.
Check which web server you run in Tools > Site Health > Info > Server. If it says Nginx, read the plugin's notes for Nginx users on the WP Fastest Cache plugin page and ask your host for help.
Many Nginx hosts already provide server-level caching. In that case, a plugin cache adds little and may cause conflicts.
LiteSpeed servers read .htaccess, but they usually work best with the host's own LiteSpeed Cache plugin.
Is another cache plugin or host cache conflicting?
Running WP Fastest Cache next to another page cache plugin or a host-level cache causes conflicts, so keep only one page cache active and decide which layer does the job.
| Conflict | Sign | Fix |
|---|---|---|
| Second cache plugin active | Two cache comments, odd behaviour | Deactivate one plugin fully |
| Host server cache | Host headers show HIT, WPFC comment missing | Use the host cache or disable it |
| Cloudflare page caching | Old pages after clearing WPFC | Purge Cloudflare as well |
| Optimisation plugin with caching | Duplicate minify or cache features | Turn off overlapping options |
Leftover files from an old cache plugin can also cause trouble. Check for an advanced-cache.php file in wp-content and remove it if it belongs to a plugin you no longer use.
For Cloudflare purging, follow how to clear the Cloudflare cache in WordPress.
Are some pages excluded from the cache?
WP Fastest Cache skips some pages by design, such as WooCommerce cart and checkout, pages with certain query strings or cookies, and any URLs you added to the Exclude tab.
Open the Exclude tab in the plugin settings and review the rules. A broad rule, such as excluding everything that contains a common word, can exclude far more than you meant.
URLs with query strings, like tracking parameters, are often served uncached. That is normal and protects dynamic pages.
If only one page is uncached, check whether it has a form, a cart widget or personalised content. Those features can trigger exclusions.
Why do changes not show after updating content?
If edits do not appear, the old cached copy is still being served, so clear the WP Fastest Cache, then any host cache, CDN and browser cache, and check the clear-on-update settings.
Click Clear Cache in the admin bar, or Delete Cache in the plugin settings.
Then clear other layers. Our guide on how to clear cache in WordPress covers each one.
Make sure Update Post is ticked in the settings, so editing a post clears its cache automatically.
Is minify or combine breaking the site?
If pages look broken or scripts fail after enabling Minify or Combine options, those features are changing files your theme or plugins need, so turn them off one at a time to find the culprit.
- Untick Minify CSS, Combine CSS, Minify JS and Combine JS.
- Click Submit and clear the cache.
- Test the site.
- Turn options back on one by one, testing after each.
Keep only the options that do not break anything. Combining files matters less on modern HTTP/2 hosting than it once did.
Open the browser console to spot JavaScript errors. They often name the script affected by minification.
Could a plugin conflict or permissions problem be the cause?
Yes, security plugins, membership plugins and wrong folder permissions on wp-content/cache can stop cache files being created, so test for conflicts and check the cache folder is writable.
WP Fastest Cache stores files in wp-content/cache/all. If that folder is missing after browsing the site logged out, the plugin cannot write there. Folder permissions of 755 usually work.
For conflicts, deactivate other plugins on a staging copy and test again. Our plugin conflict guide walks through the process.
What should you do if nothing fixes it?
If WP Fastest Cache still does not work, check the plugin's support forum, ask your host whether server rules block it, or switch to your host's recommended cache plugin.
Search the WP Fastest Cache support forum for your exact symptom. Many server-specific problems have known fixes.
The WP Fastest Cache website also has tutorials for each setting and premium feature.
Some hosts simply work better with their own tools. If your host provides a built-in cache, using it is often faster and simpler.
| Symptom | Most likely cause | First fix |
|---|---|---|
| No cache comment in source | Logged in or Cache System off | Test logged out, enable Cache System |
| Warning about .htaccess | File not writable | Set .htaccess to 644 and resubmit |
| Works on Apache but not now | Moved to Nginx | Ask host for rules or use host cache |
| Old content showing | Cache not cleared | Clear all cache layers |
| Broken layout | Minify or combine | Turn those options off and retest |
Frequently asked questions
How do I know WP Fastest Cache is caching pages?
Open a page in a private window while logged out, reload it once, then view the page source. A comment near the end that mentions WP Fastest Cache confirms the page came from the cache.
Why does WP Fastest Cache not work when I am logged in?
By default, the plugin does not serve cached pages to logged-in users, because admins need to see live changes. Always test caching in a private window or while logged out.
Can I use WP Fastest Cache with Cloudflare?
Yes. WP Fastest Cache handles page caching on your server, and Cloudflare caches static files at the edge. Purge both after big changes, and avoid enabling Cloudflare full-page caching unless you know how it interacts.
Does WP Fastest Cache need .htaccess?
On Apache and LiteSpeed servers, yes. The plugin writes rewrite rules into the .htaccess file so cached pages load quickly. If the file is not writable, caching may fail or run slowly.
Should I use WP Fastest Cache with my host's cache?
Usually not. Running two page caches causes conflicts and stale pages. Pick either your host's cache or WP Fastest Cache, and turn off the page caching in the other.
Sources
- WP Fastest Cache plugin WordPress.org
- WP Fastest Cache support forum WordPress.org
- WP Fastest Cache WP Fastest Cache
- Apache mod_rewrite Apache HTTP Server Project
- Inspect network activity Chrome for Developers
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


