Niteo

<p>Spider Blocker blocks most common bots that consume bandwidth and slow down your blog.<br />
It accomplishes this by using .htaccess file to minimize impact on your website. It’s hidden from external scanners.</p>
<p>Spider Blocker is specifically designed for Apache servers with mod_rewrite enabled, allowing you to effortlessly safeguard your website from the most prevalent bots that hamper performance and drain resources.</p>
<h4>Plugin Features</h4>
<ul>
<li>Block Unlimited bots from viewing your site</li>
<li>Easy Export/Import rules (comes with most common list of bots)</li>
<li>Zero Footprint</li>
</ul>


Spider Blocker

Does what it promises to do. No more bad bots to my WP blog :)

Perfect!

SpiderBlocker will block most common bots that consume bandwidth and slow down your blog.

PiotrPress

Clearcode

<p>The CC-Cache plugin supports caching of Posts, Pages, and any public Custom Post Types – including single and archive pages.<br />
It also supports a “static page display” option: Front page, Posts page, and standard Latest Posts listing.<br />
This plugin is compatible with Multisite WordPress installations.</p>
<h4>How does it work?</h4>
<p>When a user (i.e. someone who is logged out of WordPress) opens a page for the first time, the plugin saves all the rendered html to a file in the wp-content/cache directory.<br />
From this moment onwards, any user who accesses the site will be served content directly from the generated html file. WordPress at this point is not initialized for this page.<br />
The generated cache file will be removed when you make changes to the corresponding Post/Page, and then the process starts from the beginning.<br />
You can also clear all cached files from the Cache options page (visit the ‘Settings > Cache’ page in wp-admin), or manually delete files from the wp-content/cache directory.</p>
<h4>Tips & Tricks</h4>
<p>You can check if a page’s content is served from a cache file by opening the page’s source code in the browser and scrolling down to the closing <code><body></code> html tag.<br />
If the content is cached, you should see a comment with the date and time the page was last cached, for example:<br />
    </p>
<p>You can disable cache for a single request and get the raw html by adding <code>cache=false</code> to a URL’s parameter, for example:<br />
    http://example.com/?cache=false</p>
<p>You can disable cache for a single request and get the raw html by adding <code>cache=false</code> HTTP header.</p>
<p>Logged-in users always get the raw html.</p>
<h4>Ideas for future versions</h4>
<ol>
<li>Add support for Categories, Tags, Taxonomies, and Authors.</li>
<li>Add support for RSS/Atom feeds.</li>
<li>Add support for Nginx and IIS servers.</li>
<li>Add support for other WordPress Filesystem Methods.</li>
<li>Add regenerate function for all cache files.</li>
</ol>
<h3>Requirements</h3>
<ol>
<li>Apache server</li>
<li>mod_rewrite</li>
<li>Write access to wp-content/cache directory</li>
<li>PHP interpreter version >= 5.3</li>
</ol>

CC-Cache

A simple and fast cache plugin based on static-rendered html files served by Apache with mod_rewrite.

Spider Blocker vs CC-Cache