abhishek

<h4>1. Add an Expires Header</h4>
<p>Web pages are becoming increasingly complex with more scripts, style sheets, images, and Flash on them. A first-time visit to a page may require several HTTP requests to load all the components. By using Expires headers these components become cacheable, which avoids unnecessary HTTP requests on subsequent page views. Expires headers are most often associated with images, but they can and should be used on all page components including scripts, style sheets, and Flash.</p>
<p>Using WP Avoid Slow reduces number of HTTP requests affecting the page load performance.</p>
<h4>2. Configure Etags</h4>
<p>Entity tags (ETags) are a mechanism web servers and the browser use to determine whether a component in the browser’s cache matches one on the origin server. Since ETags are typically constructed using attributes that make them unique to a specific server hosting a site, the tags will not match when a browser gets the original component from one server and later tries to validate that component on a different server.</p>
<p>WP Avoid Slow Configure Etags helping browsers to validate the component !!</p>
<h4>Please Note</h4>
<p>Performance can be measured via Yslow. <a href="http://developer.yahoo.com/yslow/" rel="nofollow ugc">Read More</a> about Yslow .</p>


WP Avoid Slow

WP Avoid Slow - Add .htaccess tricks to boost your WP Blog Speed.

Samuel Aguilera

<p>There’s a lot of WordPress security plugins with many many options and pages to setup. And that is fine if you know what to do.<br />
But most of the times, you don’t need so much or simply you’re not sure about what to set or not.</p>
<p>This plugin adds some extra security to your WordPress with only one click. <strong>No options page, just activate it!</strong></p>
<h4>Features</h4>
<p>Like many other security plugins SAR One Click Security adds well known .htaccess rules, but only the ones probed to be safe to use in almost any type of site (including WooCommerce stores), to protect your WordPress from common attacks. This allows you to have a safer WordPress without worries about what protection you should be using.</p>
<ul>
<li>Turn off ServerSignature directive, that may leak information about your web server.</li>
<li>Turn off directory listing, avoiding bad configured hostings to leak your files.</li>
<li>Blocks public access (from web) to following files that may leak information about your WordPress install: .htaccess, license.txt, readme.html, wp-config.php, wp-config-sample.php, install.php</li>
<li>Blocks access to wp-login.php to dummy bots trying to register in WordPress sites that have registration disabled.</li>
<li>Blocks requests looking for timthumb.php, reducing server load caused by bots trying to find it. (*)</li>
<li>Blocks TRACE and TRACK request methods, preventing XST attacks.</li>
<li>Blocks direct posting to wp-comments-post.php (most spammers do this) and access with blank User Agent, reducing spam comments a lot and also server load.</li>
<li>Blocks direct access to PHP files in wp-content directory (this includes subdirectories like plugins or themes). Protecting you from a huge number of 0day exploits.</li>
<li>Blocks direct POST to wp-login.php and access with blank User Agent, preventing most brute-force attacks and reducing server load.</li>
<li>Blocks access to .txt files under any plugin/theme directory to prevent scans for installed plugins/themes.</li>
<li>Blocks any query string trying to get a copy of the wp-config.php file.</li>
<li>Blocks gf_page=upload query string argument, this was deprecated in Gravity Forms on May 2015, if your copy of Gravity Forms still uses it, update now!</li>
<li>Removes version information from page headers. This includes not only the page header (html or xhtml) but also feed headers (rss, rss2, atom, rdf) and opml comments. Only the version number is removed, not the entire generator information.  </li>
</ul>
<p>(*) If your theme uses TimThumb, you can disable that blocking rule, check FAQ before installing the plugin to see how.</p>
<h4>Requirements</h4>
<ul>
<li>WordPress 3.9.2 or higher. (Works with WordPress network/multisite installation).</li>
<li>Apache 2.4.x web server</li>
</ul>
<p>It has been tested in many servers including large providers like HostGator, Godaddy and 1&1 with optimal results, and it will work fine in any decent hosting service (that allows you to set options from .htaccess files).</p>
<p>Anyway, if you get any problem after activating the plugin, check FAQ for instructions on how to manually uninstall it.</p>
<p>If you’re not sure of which server is your hosting company using or if they allow to use custom .htaccess rules, I would recommend you to contact with your host support <strong>before</strong> installing the plugin.</p>
<h4>Usage</h4>
<p>To apply above mentioned security rules simply install and activate the plugin, no options page, no user setup!</p>
<p>If you need to remove the security rules for some reason, simply deactivate the plugin. If you want to add them again, activate the plugin again, that easy 😉</p>
<p>And remember, <strong>if your theme uses TimThumb, check FAQ before installing the plugin</strong>.</p>


SAR One Click Security

Adds some extra security to your WordPress with only one click.

WP Avoid Slow vs SAR One Click Security