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 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. Output of alternative content can be made to occur when the token is missing or fails to match what is expected – if the token received matches the expected one, the controlled content can be revealed to the visitor.
For this version, an additional shortcode attribute “title” also allows the page title to be changed conditionally PROVIDED JAVASCRIPT IS ENABLED IN THE BROWSER (it has no effect if JavaScript is turned off!)
The shortcode to use is ‘pageguard’ – its attributes are:
<pre><code>tokenparam (required) -> a string value containing the name of the token URL param - e.g. 'mytoken'
eq (optional) -> a string value containing the expected value of the tokenparam - e.g. 'x34ggj45b'
ne (optional) -> as for "eq" but when used, shortcode will output content on non matching token
absent (optional) -> when absent="1", shortcode will output content on detection of missing token
title (optional) -> a string containing a page title to apply when the parent shortcode's criteria are met 
</code></pre>
Syntax examples:
<pre><code> show block on matching token -
 [pageguard param="token" eq="download"]
 Text to be output on matching token found
 [/pageguard]

 show block on non match + change title
 [pageguard tokenparam="token" ne="download" title="Downloads - invalid token"]
 Error text for output when token fails to match
 [/pageguard]

 show this on no token found + change title
 [pageguard tokenparam="token" absent="1" title="Downloads - missing token"]
 Error text for output when token is missing
 [/pageguard]
</code></pre>
<h3>Usage</h3>
A typical use scenario might be to control 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 have access to the download link(s) on the page! If you also want the page title to reflect any error conditions, you an use the “title” attribute to do this (please be aware however that this functionality depends on JavaScript being enable in the user’s browser – it disabled, “title” has no effect.)
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=x34ggj45b"
</code></pre>
Next, add pageguard short codes for the cases you intend to handle to your return page in WordPress –
<pre><code>[pageguard param="token" eq="x34ggj45b" title="Title for matched token"]
Text to be output on matching token found
[/pageguard]

[pageguard tokenparam="token" ne="x34ggj45b" title="Title for failed match"]
Error text for output when token fails to match
[/pageguard]

[pageguard tokenparam="token" absent="1" title="Title for missing token"]
Error text for output when token is missing
[/pageguard]
</code></pre>
This will correctly display the main content for the page when Page Guard detects a matching token. It also provides for the possibility of providing different error content for the page in the event of the token being incorrect or missing.

Page Guard

Adds a short code which allows conditional output of page content and title based on the value of a token passed as a URL parameter or a POST variable

Easy PageSpeed vs Page Guard