Speed & performance · Info
W3 Total Cache Recommended Settings Explained: What Each Option Does

Short answer
Start W3 Total Cache with Page Cache on using Disk: Enhanced, Browser Cache and Opcode Cache on, and Object Cache only with Redis or Memcached. Leave Database Cache and Minify off until you test them, then change one setting at a time and check your pages.
Key takeaways
- Page Cache with Disk: Enhanced is the biggest and safest win on most hosts.
- Use Object and Database Cache only with memory storage like Redis or Memcached.
- Minify often breaks layouts, so enable it one file type at a time.
- Browser Cache and Opcode Cache are low risk and usually worth enabling.
- Run the Setup Guide, then test each change with caches cleared.
What are the recommended W3 Total Cache settings?
For most sites, turn on Page Cache with Disk: Enhanced, Browser Cache and Opcode Cache, use Redis or Memcached for Object Cache if your host offers it, and leave Database Cache and Minify off until you test them.
W3 Total Cache has more settings than most caching plugins. That flexibility is useful, but it also makes it easy to slow a site down or break the layout by switching on everything.
The safest approach is to start with the features that rarely cause trouble, then test the risky ones one at a time. If you are new to the plugin, our overview of what W3 Total Cache is explains what it does before you change anything.
Here is a starting point for a typical shared or managed host:
| Setting | Recommended start | Why |
|---|---|---|
| Page Cache | On, Disk: Enhanced | Biggest speed win for visitors |
| Minify | Off at first | Can break layouts and scripts |
| Opcode Cache | On if available | Speeds up PHP itself |
| Database Cache | Off on shared hosting | Disk storage often makes it slower |
| Object Cache | On only with Redis or Memcached | Disk object cache adds overhead |
| Browser Cache | On | Lets browsers reuse files |
| CDN | On if you use one | Serves static files from nearby servers |
| Lazy Load | On, unless your theme already does it | Delays offscreen images |
All of these live under Performance > General Settings, with detail pages for each feature in the same menu.
Should you run the Setup Guide first?
Yes, the built-in Setup Guide tests page, database, object and browser caching on your server and suggests options that actually help.
When you first activate the plugin, W3 Total Cache offers a Setup Guide. You can also open it later from the Performance menu. It measures response times with different storage methods and shows the results.
Treat its suggestions as a strong hint, not a rule. A test on an empty cache with no traffic is not the same as a busy day. Still, it is a far better starting point than guessing.
The plugin's support documentation covers the guide and each settings screen in detail.
What does Page Cache do and which method is best?
Page Cache saves finished HTML pages so WordPress does not rebuild them for every visitor, and Disk: Enhanced is the best method on most hosts.
Without page caching, every request runs PHP and database queries. With it, visitors get a stored copy, which is much faster.
Storage methods compared:
- Disk: Enhanced writes static files the web server can serve directly. Best for most shared and VPS hosts.
- Disk: Basic still runs some PHP per request. Use it only if Enhanced does not work on your server.
- Redis or Memcached store pages in memory. Useful for multiple servers or very busy sites.
In the Page Cache settings, keep pages for logged in users uncached. Turn on cache preload with your sitemap URL so popular pages are ready before visitors arrive.
Never cache cart, checkout or account pages on shops. W3 Total Cache excludes many common ones, but check any custom URLs you use.
Should you turn on Minify?
Turn on Minify only after testing, because combining and shrinking CSS and JavaScript often breaks layouts, menus and forms.
Minify removes spaces and comments from files and can join them together. On modern hosts with HTTP/2 and compression, the gain is often small.
If you try it, use auto mode first and enable one file type at a time:
- Turn on HTML minify only, then check key pages
- Add CSS minify, then check again
- Add JavaScript minify last, and test menus, sliders and forms
If something breaks, exclude the problem file or turn that part off. Our guide on removing unused CSS covers a more effective way to cut CSS weight.
What are Opcode Cache, Database Cache and Object Cache?
Opcode Cache stores compiled PHP, Database Cache stores query results, and Object Cache stores WordPress data objects between requests.
Opcode Cache uses PHP's built-in OPcache to skip recompiling PHP files. It is safe and almost always helps. The PHP OPcache manual explains the mechanism, and our guide on what PHP OPcache is covers it in plain English.
Database Cache keeps query results. On shared hosting with disk storage, reading cache files can be slower than MySQL itself. Leave it off unless the Setup Guide shows a clear gain with memory storage.
Object Cache stores the results of WordPress's object cache, documented in the WP_Object_Cache reference. It shines with Redis or Memcached, especially on WooCommerce and membership sites. With disk storage it often adds overhead.
Our comparison of page cache vs object cache explains when each one matters.
What Browser Cache settings should you use?
Turn on Browser Cache with expires headers, cache control headers and compression, and keep the default lifetimes unless you have a reason to change them.
Browser caching tells visitors' browsers how long to keep CSS, JavaScript, images and fonts. Return visits then load faster. MDN's Cache-Control reference describes the headers involved.
Settings to check:
- Set expires and cache control headers for CSS, JS and media
- Enable gzip or Brotli compression if your server supports it
- Keep prevent caching of objects after settings change on, so updates reach visitors
If you use a CDN or a host that already sets these headers, check for duplicates. Two sets of conflicting headers can confuse browsers.
Should you use the CDN and User Experience options?
Enable the CDN section only if you have a CDN account, and use the User Experience options for lazy loading and removing small unused features.
The CDN section rewrites file URLs to a CDN host. If you use Cloudflare as a proxy, you often do not need this, because Cloudflare already sits in front of the whole site.
The User Experience section includes lazy loading images, disabling emoji scripts and removing the embeds script. Lazy loading is worth turning on unless your theme or WordPress core already handles it, since doubling up causes no extra gain.
Some features, such as delaying scripts, need careful testing for the same reasons as Minify.
Which W3 Total Cache settings need Pro?
Pro adds extras such as fragment caching, REST API caching and more detailed statistics, but the free plugin covers what most sites need.
The free version from the WordPress plugin directory includes page, browser, object, database and opcode caching, minify, CDN support and lazy loading.
Pro is mainly useful for developers who cache parts of pages, or for busy sites that need deeper tuning. Check the vendor's site for current Pro pricing and features, since they can change.
How do you test your settings?
Change one setting at a time, clear all caches, then check speed with a testing tool and click through key pages, forms and checkout.
A simple routine:
- Run a speed test before changes and save the result
- Change one feature, purge all caches, and test again
- Load the home page, a post, a form and a product page in a private window
- Check the browser console for script errors
If speed gets worse or something breaks, undo the last change. Our guide on clearing cache in WordPress shows how to purge every layer.
If you are comparing plugins, our guide to WP Super Cache settings shows how a simpler tool handles page caching.
On LiteSpeed servers, the LiteSpeed Cache settings guide is a better fit, since that plugin works with the server's built-in cache.
Frequently asked questions
What is the best page cache method in W3 Total Cache?
Disk: Enhanced suits most shared and VPS hosts because the web server can serve cached pages directly. Choose Redis or Memcached when you run several servers or have them available on a busy site.
Should I enable Database Cache in W3 Total Cache?
Usually not on shared hosting. Disk-based database caching can be slower than the database itself. Enable it only with memory storage and only if testing shows faster pages.
Why did W3 Total Cache break my site layout?
Minify or script delay settings are the usual cause. Turn off JavaScript and CSS minify, purge all caches and check again, then re-enable features one at a time with exclusions.
Can I use W3 Total Cache with Cloudflare?
Yes. Many sites use both. Keep page caching in W3 Total Cache, let Cloudflare handle static files, and purge both caches after changes so visitors get fresh content.
Is W3 Total Cache good for WooCommerce?
It can be, with care. Exclude cart, checkout and account pages, keep logged in users uncached and use Redis or Memcached for object caching on busy stores.
Sources
- W3 Total Cache WordPress.org Plugins
- W3 Total Cache Support BoldGrid
- OPcache PHP Manual
- WP_Object_Cache WordPress Code Reference
- Cache-Control MDN Web Docs
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.


