Easy PageSpeed

Description

Easy PageSpeed is a simple and efficient plugin desgined to do just two things:

  1. 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.
  2. 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.

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.

Pro Version

In addition to the fully functional Lite version, Easy PageSpeed also has a Pro version, which gives you more control over how your CDN servers are used, with these extra features:

  1. Supports multiple CDNs, for load balancing or parallel loading (domain sharding), as recommended by most page speed tools.
  2. Allows customization the file types to be served from CDNs.
  3. Multiple groups of CDNs, each with their own file types, so that you can serve, for example, images from http://img.example.com and style sheets from http://css.example.com and so on.

Screenshots

  • Easy PageSpeed admin page, showing the simple, single-page, easy-to-understand settings.
  • Easy PageSpeed Pro admin page, showing the extra features.
  • My blog performance with no CDN support.
  • My blog with Easy PageSpeed set up.

Installation

To install Easy PageSpeed, please use the plugin installation interface.

  1. Search for the plugin Easy PageSpeed from your admin menu Plugins -> Add New.
  2. Click on install.

It can also be installed from a downloaded zip archive.

  1. Go to your admin menu Plugins -> Add New, and click on “Upload Plugin” near the top.
  2. Browse for the zip file and click on upload.

Once uploaded and activated, visit the plugin admin page to specify your CDN server (or servers in the Pro version).

FAQ

Installation Instructions

To install Easy PageSpeed, please use the plugin installation interface.

  1. Search for the plugin Easy PageSpeed from your admin menu Plugins -> Add New.
  2. Click on install.

It can also be installed from a downloaded zip archive.

  1. Go to your admin menu Plugins -> Add New, and click on “Upload Plugin” near the top.
  2. Browse for the zip file and click on upload.

Once uploaded and activated, visit the plugin admin page to specify your CDN server (or servers in the Pro version).

What does *Easy PageSpeed* do?

Here is what Easy PageSpeed does when a reader visits one of your blog posts or pages:

  1. It looks at the HTML being prepared for the reader, and removes all the query strings (things that look like ?ver=4.4.1) from any local links of static resources (files with extensions jpg, jpeg, gif, png, js and css).
  2. It rewrites all the local links in the page (again, only for files with extensions jpg, jpeg, gif, png, js and css) so that they point to the CDN server that you have specified.
What is a CDN and how do I use it?

Content Delivery Network (CDN) is a collection of geographically distributed servers that mirror and serve you static contents (images, JavaScrip/CSS files, movies etc.) to your readers much faster than your own blog server can. It can speed up your blog tremendously.

The most common (and easiest) type of CDN is the origin-pull kind, where you specify the URL from where it can pull contents. Amazon CloudFront is one such CDN that most bloggers will find useful. While setting up the CDN, you will specify that the contents are to be pulled from your blog, http://yoursite.com/.

Once a CDN server is set up on Amazon CloudFront (or anywhere else), you will get a URL that you can place instead of http://yoursite.com/ for each of the static resources that you want to serve from your CDN.

To make the CDN URL look nicer, you may want to use your cPanel DNS Zone Editor to define a CNAME. For example, you can have a name like http://cdn.yoursite.com as your CDN URL.

Since most browsers limit the number of concurrent connection to a server, you may want to define multiple CDNs using the CNAME trick, all pointing to the same URL you got from CloudFront (or your provider). This technique is called domain sharding, and is fully supported in the Pro version of this plugin.

Of course, you need to make WordPress generate HTML with your CDN addresses instead of http://yoursite.com/ for static resources. While it can be done using certain filters (e.g. pre_option_upload_url_path), it is far more convenient to use this plugin.

Why not let my caching plugin do this job?

Many caching plugins can handle CDNs and query strings. Why use this plugin? Because many of the popular caching plugins are so heavy and feature-rich that they actually slow down your blog, especially on the admin side. Most (90%) of the performance improvements that a caching plugin buys you may be had with this plugin (and a decent PHP accelerator at the server level).

If you like the way this plugin works, you might want to get the Pro version, so that you can benefit from CDN sharding and finer control of what files are served from where.

Reviews

Author Review

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.

Read all 1 review

Contributors & Developers

“Easy PageSpeed” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Easy PageSpeed” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

  • V1.40: Compatibility with WP4.8. Sunset edition. [Aug 1, 2017]
  • V1.30: Restricting the scope of query string removal to user-specified types. [Aug 11, 2016]
  • V1.21: Making the diagnostic comment optional. [May 23, 2016]
  • V1.20: Compatibility with WP4.5. [Apr 12, 2016]
  • V1.11: Minor interface and documentation changes. [Feb 25, 2016]
  • V1.10: Deprecating translation interface in favor of Google translation. [Feb 23, 2016]
  • V1.01: Minor bug fix. [Feb 9, 2016]
  • V1.00: Initial release. [Feb 1, 2016]