Step a. Set General Settings
- Check box next to “Cache hits to this website…”
- Select button next to “Expert”
- Check box next to “304 Not Modified browser caching”
- Check box next to “Don’t cache pages for known users”
- “Cache rebuild” & “Extra homepage checks” should already be checked, leave them that way.
- Check box next to Mobile device support. (External plugin or theme required. See the FAQ for further details.)
- (Recommended)
- Select “Update Status” button.
Step b. Set Mod_Rewrite Rules
- Select “Update Mod_Rewrite Rules” in the yellow box.
Step c. Set Garbage Collection
- “Expiry Time & Garbage Collection” and enter “3600” in the box, then select “Change Expiration”
Step d. Under tab Preload set:
Refresh preloaded cache files every minutes. (0 to disable, minimum 30 minutes.)
Preload mode (garbage collection only on legacy cache files. Recommended.)
Preload tags, categories and other taxonomies.
Send me status emails when files are refreshed.
Many emails, 2 emails per 100 posts.
Medium, 1 email per 100 posts.
Less emails, 1 at the start and 1 at the end of preloading all posts.
Explanation of the Options Selected
Cache hits to this website…
Enables caching
Use mod_rewrite to serve cache files
Fastest caching method, uses mod_rewrite rules in client’s .htaccess file
304 Not Modified browser caching
Indicates to the client’s browser whether a requested file has been modified or not (see: http://www.addedbytes.com/for-beginners/http-status-codes/ or elsewhere for more info on that apache code)
Don’t cache pages for known users
This prevents logged-in users from being served cached pages and is the default for almost every caching plugin out there.
Expiry Time & Garbage Collection
The default setting will allow cache files to age 1 hour (3600 seconds) prior to being removed which is ideal. This setting can be increased for sites that do not have many posts (1,000 or less ) if you do not update your content often. If you have a very large amount of posts ( 25,000+ ), a lower setting around 1800 may be more viable to prevent stat/CPU issues due to the amount of files being created.
Rejected User Agents
It is recommended that you do not remove the default user agents from the list, to prevent bots from caching content and pages not normally seen by your visitors. (For example, if you have a calendar, a real visitor may only browse months close to now, but a bot will index every month forever as if it is a different page. Caching these pages real visitors are unlikely to visit wastes resources.)