manojtd

Easy PageSpeed is a simple and efficient plugin desgined to do just two things:
<ol>
<li>Serve your static resources (files of types) from the Content Delivery Network (CDN) that you specify. Using a CDN can improve the performance of your blog significantly.</li>
<li>Remove the query strings that WordPress adds to your static files (indicating the WP version). The existence of the query string on a file directs the web browsers not to cache it, which may adversely affect the blog performance.</li>
</ol>
Both these functionalities are available on most caching plugins, such as WP Super Cache or W3 Total Cache. If you use any of them, you may not need to use Easy PageSpeed. However, if you have a high performance web server, a caching plugin may be an overkill, and most of the performance boosts may be gleaned by this simple Easy PageSpeed plugin, and a good PHP accelerator at the server level.
<h4>Pro Version</h4>
In addition to the fully functional Lite version, Easy PageSpeed also has a <a href="http://buy.thulasidas.com/easy-pagespeed" title="Easy PageSpeed -- simple page speed tool, $6.95" rel="nofollow ugc">Pro version</a>, which gives you more control over how your CDN servers are used, with these extra features:
<ol>
<li>Supports multiple CDNs, for load balancing or parallel loading (domain sharding), as recommended by most page speed tools.</li>
<li>Allows customization the file types to be served from CDNs.</li>
<li>Multiple groups of CDNs, each with their own file types, so that you can serve, for example, images from <code>http://img.example.com</code> and style sheets from <code>http://css.example.com</code> and so on.</li>
</ol>

Easy PageSpeed

I wrote this plugin for my own use. I just needed to rewrite the URLs of static resources using my CDN servers, and get rid of the query strings on js and css files. Nothing fancy. This plugin does just that, and adds only a couple of milliseconds to the processing time. Hope you will find it useful.



Author Review

Easy PageSpeed rewrites the URLs on your blog to serve your static resources from your CDN. It also removes query strings to leverage browser caching.

fculross

Page Guard Redirect uses a single URL parameter or POST variable as a means of providing a token to guard access to any page on which this plugin’s shortcode is placed – redirection can be made to occur when the token fails to match what is expected (the alternative, i.e. redirect when token DOES match – is also included for completeness.)
The shortcode to use is ‘pgredirect’ – its attributes are:
<pre><code>tokenparam (required): a string value containing the name of the token URL param - e.g. 'mytoken'
tokenvalue (required): a string value containing the expected value of the tokenparam - e.g. 'x34ggj45b'
redirectURL (required): a string value containing the URL to redirect to (you can use an existing page as the target for the redirection - alternatively, for many configurations, setting this to a non existent page will make WordPress redirect to the default 404 "not found" page.)
redirectWhen (optional): -> when = "1", redirects when match is found, otherwise defaults to redirect on non-match
</code></pre>
Syntax examples:
<pre><code> redirect on non match (default) -
 [pgredirect tokenparam="mytoken" tokenvalue="1234abcd" redirecturl="http://my.redirurl.com/notfound" /]

 redirect on match (add redirectwhen="1" as an attribute) -
 [pgredirect tokenparam="mytoken" tokenvalue="1234abcd" redirectwhen="1" redirecturl="http://my.redirurl.com/notfound" /]
</code></pre>
<h3>Usage</h3>
A typical use scenario might be to prevent access to a downloads page. Suppose you have a PayPal “Buy Now” button on your site which allows visitors to make a payment for say, an eBook or audio recording. When setting up the button in your PayPal account you specify a URL on your site to which the visitor is returned after they’ve made payment. On this return page you’ve added a link the visitor can use to download their purchase – however, you don’t want any non paying visitors to find the return page by chance!
Add a parameter to the end of the return URL (using any name and value you want) when you set up your button in PayPal e.g.
<pre><code>"http://your.wordpress.site/download/?dltoken=Xc345Fd77"
</code></pre>
Next, add a pgredirect short code to your return page in WordPress –
<pre><code>[pgredirect tokenparam="dltoken" tokenvalue="Xc345Fd77" redirecturl="http://your.wordpress.site/notfound" /]
</code></pre>
This will cause a redirect if Page Guard Redirect detects either the lack of the expected token in the URL parameter, or a value which doesn’t match the one in the short code’s tokenvalue attribute.

Page Guard Redirect

Adds a short code which allows page redirection based on the value of a token passed as a URL parameter or POST variable

Easy PageSpeed vs Page Guard Redirect