Back to Community
Home / Community / Plugin → Wp fastest cache

Understanding WP Fastest Cache's Recommended Settings

11 threads Sep 16, 2025 Plugin → Wp fastest cache

Content

WP Fastest Cache is a popular tool for improving WordPress site performance, but its array of options can be confusing for new users. A common question in the community is: "What are the recommended settings?" Based on numerous support threads, a clear pattern of advice from the plugin's representatives has emerged.

The Most Common Advice: "Enable All Checkboxes"

In multiple threads, when users ask for a basic setup guide or recommended configuration, the advice is consistently straightforward. The most frequent official response is to simply enable all the checkboxes on the settings page. This is presented as a simple starting point that should work for most general use cases.

Why This Advice is Given

This blanket recommendation appears to be a default stance for providing quick, general-purpose caching. Enabling all options activates page caching, browser caching, Gzip compression, and other core features designed to speed up a site immediately after activation.

When to Deviate from the Default Advice

While "enable all" is a common starting point, the sample threads reveal specific scenarios where you might need a more tailored configuration:

  • WooCommerce Sites: Users have reported issues with shopping carts displaying incorrect product counts. For e-commerce sites, you may need to manually exclude the woocommerce_items_in_cart cookie from caching to ensure cart functionality works correctly.
  • Divi Theme Users: If you use the Divi theme, it is often recommended to disable the "Static CSS" option. For other Divi-related settings, the advice has been to disable them all.
  • Logged-in Users: If your site has a strong membership or user interaction component, you might consider enabling "Don't show the cached version for logged-in users" to provide a dynamic experience for registered visitors.
  • .htaccess Constraints: The plugin requires write access to your .htaccess file to apply certain rules. If your server configuration locks this down (for security or performance reasons), you may encounter errors and need to explore alternative setups, such as serving cache via PHP.

Important Limitations to Know

Based on community interactions, several frequently requested features were not available at the time of these threads:

  • There is no built-in import/export functionality for settings.
  • The plugin does not support ZSTD compression.
  • There is no option to manually manage rewrite rules for users who do not use .htaccess.

Final Recommendation

For most users on a standard WordPress site, beginning with all options enabled is a valid approach to quickly achieve basic caching. However, it is crucial to thoroughly test your site's functionality—especially forms, carts, and user-specific content—afterward. Be prepared to fine-tune specific options, particularly for e-commerce or membership sites, to balance speed with dynamic functionality.

Related Support Threads Support