ctfeds.org

How are we doing?

Popular site noupe.com released a post 10 Hand-Picked WordPress Themes of August 2016 a few weeks ago, and we decided to have a look at the performance of those Themes. Check the pulse, have a look at the state of nation, see how we (as people who make websites) are doing. Unfortunately, it’s more of a case of “Nope” than “Noupe” (sorry).

Statistics

We decided to just look at the mobile PageSpeed scores of the demo page for each Theme (that had a demo), to get a rough read of them. Here are the results:

The highest score was 70 and the lowest was 25. Ouch.

Review

The (mean) average PageSpeed score was 47/100. The median average was a little lower at 41/100.

You could argue that some of PageSpeed’s metrics aren’t fair to test on a demo site, such as enabling compression, caching, and server response. The Theme will be deployed on a different server, where those things may be fixed. While this is true, it would be great for a demo to show off a Theme as the best it can be, and to set a good example of how to use the Theme in the wild. The h5bp project has example server configs for nginx and Apache that would help with the first two.

You could make a similar argument for optimising images. They are content that will be different from the live site, so shouldn’t be included in the score. The flipside is that Themes could require a Plugin that optimises images automagically. There are quite a few on the Plugin Directory. That way, the content author doesn’t need to remember to optimise their images: it just happens.

Eliminate render-blocking JavaScript and CSS in above-the-fold content is a bit of a fiddly one. If we’re talking about Critical CSS, that’s a tricky one. It’s still a new technique that’s a bit fiddly, and it’s perhaps unfair to expect it to be widely adopted already. However, the PageSpeed comments for these Themes refer to an older technique that most of the Themes aren’t implementing: having your script tag(s) at the bottom of your document. This metric was in “Should Fix” for the majority of the Themes because there were a lot (double digits of both CSS and JS!) of files, making the problem worse.

So, State of the Front-end Nation (or, WordPress Theme Nation, at least)? In the red. :-/


Published on Friday 9th September 2016.

Steve Barnett (@maxbarners) and Justin Slack (@justin_r_slack)

CTFEDs Organising Team