This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.


Vendi Cache takes your slow database-driven pages and turns them into very fast static HTML files.

Squirrel image from


  • Settings for cache mode and options.
  • Cache management and exclusions.
  • Admin menu location.


Before activating this plugin, please disable Wordfence’s caching system.


Is this plugin affiliated with Wordfence?

The authors of this plugin are not affiliated with Wordfence. The caching engines used by this plugin were ported from Wordfence’s code after they decided to remove them from their codebase.

Does this plugin replace Wordfence?

No, but it does replace a feature that they will be removing soon. Wordfence is one of the best security plugins available for WordPress and for about 2 years their product included a very awesome caching engine. In October of 2016 they decided that they would be removing this caching engine which is why this plugin was created.

Can I programmatically stop Vendi Cache from caching a specific page/post?

Yes, the caching engine may be stopped for a given request in several ways. The preferred way (as of 1.2.0) is via a filter: add_filter( \Vendi\Cache\api::FILTER_NAME_DO_NOT_CACHE, '__return_true' ). For legacy reasons we also still support a public static method \Vendi\Cache\api::do_not_cache(). Lastly, if you wish to globally stop the caching engine site-wide you can define the WFDONOTCACHE constant somewhere in your code.

For historical reasons, if defined the global constant is always honored first and cannot be undone via the filter. This might be changed in the future if someone actually has a need for it but generally speaking, constants are used to make global changes by administrators that local code should not be able to undo.


8. juuli 2018
Hello WP Lovers, First off, I have No connection to the makers of VC. I actually “signed up” a new account here so i could login and rave about VC. They deserve it. Should be #1, honestly, as the rest are either bloated or confusing or both. Over the years I’ve tried them all, from Rocket to WTC3 to you-name-it-plugin AND I’ve also used many different codes to avoid using an extra plugin. The problem with using codes to your .htaccess file is that themes change, the web changes and in the end there will be a glitch on your end sooner or later. So, get a clean coded theme, use LIGHT plugins, try Autoptimize + Optimize DB + Leverage Browser Caching + Vendi Cache and YOU WILL see a much faster site. A lazy load plugin will also help as photos are the #1 slower downer of your site. Getting your photos optimized is the #1 pro thing to do to speed up your site. Several plugin options out there OR resize/crunch them yourself. Vendi Cache used to be included in the Wordfence security plugin and boy did it speed things up. Then WF got bloated and slow–not sure how they are now–and they removed “Falcon” cache. So, now Falcon has reappeared as Vendi Cache and IMO it is the BEST cache plugin for 99% of websites. Try it for yourself using to A/B your site speed w and w/o Vendi. Cheers!
14. veebr. 2017
This has got to be the easiest drop in cache solution available. Works as expected without pages and pages of options.
11. nov. 2016
I was looking for a replacement of the Wordfence Falcon Engine. Thank you so much, it works perfectly!
30. okt. 2016
Vendi Cache is an excellent drop-in replacement for Wordfence caching. I was very happy to hear Vendi offered this as I have been using the Falcon cache and really wanted to just keep using what I had in the past. Thank you!
Read all 10 reviews

Contributors & Developers

“Vendi Cache” is open source software. The following people have contributed to this plugin.


Translate “Vendi Cache” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • Bug Fix: Incorrect function signature for error handling.


  • Add API class for all future public contracts.
  • Add filter \Vendi\Cache\api::FILTER_NAME_DO_NOT_CACHE (preferred) and function \Vendi\Cache\api::do_not_cache() (legacy) to allow people to disable caching per request.
  • Add cache_stats class to use instead of array, make strings translatable.
  • Add clear_entire_cache to public API.
  • Deprecate Vendi\Cache\Legacy\wordfence::do_not_cache() in favor of above.


  • Do not cache if PHP throws a fatal exception or error in someone else’s code.


  • Minor change, no update needed, added screenshots for WP


  • Minor change, no update needed, removed github badges from readme


  • Inlined a PHP constant
  • Fixed a couple of typos (props laxbobber)


  • First public release


  • First private beta.