The Faster Cache has been built with a design philosophy that specifically shuns tweaker’s bloat, the malady afflicting many caching solutions that come laden with a kitchen sink’s worth of options that would be better tweaked elsewhere.
If you like plugins that stick to their primary job, and if you appreciate configurability that matters to performance and user convenience — and that actually belongs in a plugin dedicated to caching — then the Faster Cache might be for you.
The plugin’s main dashboard provides the performance monitoring and ACE status figures described separately (“Adaptive Cache Expiry”), as well as a basic fixed cache expiry setting for use where cache adaptation is not required (for example, on a site with content that rarely or never changes).
The plugin can be used successfully without ever configuring anything else except that one number and without ever visiting its other admin pages; a user who didn’t even configure that much — and simply left the default value in place — would still enjoy all the immediate benefits of using a file-based cache. (In fact, as every plugin author knows, it is super-easy to remove options altogether: it would be easy just to eliminate nearly all of this plugin’s options, leaving the plugin to function all the time using its built-in default values.)
However, for those who wish to do so, the advanced settings page and advanced cookie-based exclusions allow fine tuning that can make a significant difference to the experience of the site’s end users; see below for details on each section of those additional settings.
The Faster Cache can either expire cache files on a simple regular interval, or it can adapt expiry to the level of update activity occurring on your site.
The faster cache can provide special handling for visitors whose browsers carry particular cookies.
Archives and comment pages can be a little tricky when deciding how a cache should behave, but the Faster Cache has you covered.
The faster cache provides several options for clearing the cache and stored performance data.
Miscellaneous options control a few details which can be important for performance and convenience. Note that several options pertain to the handling of .htaccess rules, but for best performance on any Apache-based site, WordPress should be rescued from its usual reliance on .htaccess by employing .conf rules instead.
If you’d like the Faster Cache to collect performance data every so often when a cache file is deleted — by conducting a load time test before and after deletion — you can specify that here.