{"id":394,"date":"2010-05-06T09:50:46","date_gmt":"2010-05-06T08:50:46","guid":{"rendered":"http:\/\/gavtaylor.co.uk\/blog\/?p=394"},"modified":"2011-04-15T08:38:38","modified_gmt":"2011-04-15T07:38:38","slug":"page-speed-score-93100","status":"publish","type":"post","link":"https:\/\/gavtaylor.uk\/blog\/page-speed-score-93100","title":{"rendered":"Page Speed Score: 93\/100"},"content":{"rendered":"

Google made a post the other day about “Me and site performance, sitting in a tree…<\/a>” so I thought before we get to the “…k, i, s, s, i, n, g!” I should give her a run for her money, check she is good enough for me.<\/p>\n

First thing the post suggest is to check out Site Performance in Webmaster tools, so off I went. When this first appeared in the Labs section of webmaster tools it was updating pretty regularly and was quite useful and as the graph shows helped me tweak a few things and improve the load time of the server. But it hasn’t been updated in a while now so isn’t very relevant or useful to me.<\/p>\n

\"Webmaster<\/a><\/p>\n

Next thing it suggests is to install Page Speed for Firebug and test my site. So thats what I did and I got Page Speed Score: 93\/100!<\/strong> which is pretty impressive. So I thought next, 7% to go, what can I do to get to 100\/100. Nothing it seems… All the suggestions the tool gave me were unsolvable and prevent anyone from getting top marks.<\/p>\n

The first suggestion is to Leverage browser caching<\/strong>,
\nthe file it advises me need to do this too is “http:\/\/www.google-analytics.com\/ga.js” which I cant do anything about.<\/p>\n

The next suggestion is to Defer loading of JavaScript<\/strong>, “66.4% of the JavaScript loaded by this page had not been invoked by the time the onload handler completed” is smugly informs me.
\n– http:\/\/gavtaylor.co.uk 24 functions uncalled of 25 total functions
\n– http:\/\/www.google-analytics.com\/ga.js 154 functions uncalled of 243 total functions.<\/p>\n

On closer examination the functions it reports on my site are actually from Firebug, which must be open for the test to run? catch 22 there!
\nAnd the analytic code again is from Google and I cant do anything about that.<\/p>\n

The final suggestion is to Use efficient CSS selectors,
\n<\/strong>http:\/\/gavtaylor.co.uk\/core\/styles\/styles.css<\/a> has 12 very inefficient rules, 27 inefficient rules, and 0 potentially inefficient uses of :hover out of 101 total rules.<\/p>\n

This I can do something about and when I get a moment I will be re-coding my CSS file. But this wont improve my results more than 1 or 2 points.<\/p>\n

So this unreachable target of 100\/100 appears to be impossible. I could remove the Google code from my site which would resolve the Google plug-in issue but I cant run the test without having Firebug open so there will always be 24 out of 25 uncalled functions reported keeping me away from that 100\/100 score.<\/p>\n

So… will I be sitting in that tree, doing things I should not be?… No, not until they fix the issues with their testing tools anyway…<\/p>\n

Update 4\/4\/11:<\/strong><\/p>\n

On Thursday (31st March), Google released an online version of their page speed tool, This new test works in the same way to the Firebug plugin but uses a version of webkit installed on a server. I have written a quick follow up post with links and my initial thoughts here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Google made a post the other day about “Me and site performance, sitting in a tree…” so I thought before we get to the “…k, i, s, s, i, n, g!” I should give her a run for her money, check she is good enough for me. First thing the post suggest is to check […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[150,47,41],"tags":[116,20,223,192,144],"jetpack_featured_media_url":"","jetpack_publicize_connections":[],"_links":{"self":[{"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/posts\/394"}],"collection":[{"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/comments?post=394"}],"version-history":[{"count":10,"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/posts\/394\/revisions"}],"predecessor-version":[{"id":580,"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/posts\/394\/revisions\/580"}],"wp:attachment":[{"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/media?parent=394"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/categories?post=394"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gavtaylor.uk\/blog\/wp-json\/wp\/v2\/tags?post=394"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}