Sybre Waaijer

<h4>This plugin puts your W3 Total Cache configuration on auto pilot.</h4>
It’s great when you have users that don’t have access to W3 Total Cache control but still need to purge the cache.
It’s also brilliant when you have created a blog for a customer, this way they won’t even know it’s there: All cache is purged automatically.
It’s absolutely great on MultiSite installations, especially when you allow untrusted users to create a blog.
What this plugin does:
On the front end:
<ul>
<li>No more W3 Total Cache comments in the HTML output</li>
</ul>
Behind the screens:
Purge cache, whenever:
<ul>
<li>a post is updated.</li>
<li>theme is changed.</li>
<li>a widget is updated or changed from position.</li>
<li>a sidebar is updated.</li>
<li>the theme is edited in Customizer.</li>
<li>the nav menu is updated.</li>
</ul>
MultiSite, if not Super-Admin:
No more:
<ul>
<li>purge from cache button on pages and posts edit screens.</li>
<li>admin menu on the admin bar.</li>
<li>admin menu in the dashboard.</li>
<li>amin notices in the dashboard after settings change or on error.</li>
<li>admin scripts in back end.</li>
<li>admin scripts on front end.</li>
</ul>
WPMUdev Domain Mapping support
<ul>
<li>This plugin fixes a few issues when you’re combining W3TC and Domain Mapping by automatically flushing the posts on a site. This eliminates confusion. 
This plugin allows you to adjust the output of a few filters. However, the defaults should work out for everyone.</li>
</ul>
<h3>Filters</h3>
Add a greater amount of pages and posts to be flushed on several actions 
 add_filter( ‘wap_limit_flush’, ‘my_wap_limit_flush’ ) 
 function my_wap_limit_flush() { 
 $limit = 50; // Default is 20.
<pre><code> return $limit;
}
</code></pre>
Flush everything, ignoring the limit 
 add_filter( ‘wap_flush_all’, ‘__return_true’ );

W3TC Auto Pilot

Put W3 Total Cache on auto pilot. This plugin allows you to control W3 Total Cache by simply using your website. So your cache is always up to date.

Benjamin Intal

Gambit Cache Menus caches the menus that you use in your front end. This may not be much (an estimate of 18 milliseconds per menu), but if you have large multilevel menus, and a lot of site visitors, then the speed savings may bring a lot of benefits.
Just install and activate the plugin, there are no settings page.
A menu rendered normally takes around 0.02 seconds; activating this plugin reduces this step to 0.002 seconds.
<h4>Features</h4>
<ul>
<li>Shaves off 18ms per menu</li>
<li>Uses the Transient API</li>
<li>Lightweight</li>
<li>Cleanly coded plugin</li>
</ul>
<h4>How Does it Work</h4>
It’s all about the Transient API. When a menu is rendered in the front end, the rendered menu is saved as a transient for caching. Future menu renderings use this cached copy afterwards. When the menu is updated, or when menu locations are changed, the transient is forcibly expired to make way for the updated menu.
<h4>This Is Also a Tutorial</h4>
Transients are cool. If you’re not familiar with them then we documented the code well so that you can check it out.
There should be a companion tutorial about Transients soon.

Gambit Cache Menus

Shave off a few milliseconds on your site loading time

W3TC Auto Pilot vs Gambit Cache Menus