22 Dec 2011
A couple of days ago, I said that it wouldn’t be December without a set of predictions. But it really wouldn’t be December without a roundup of the most-read posts on this site.
I revisited Steve Souders’s four-year-old stat that says that 80% of end-user response time occurs at the front end, and made a surprising discovery: After analyzing beacon data from 5 million Strangeloop customer transactions, I found that the front end is where a whopping 97% of mobile response time happens.
I converted a performance non-believer, first by showing him that his site was 30% faster in IE8 than in IE7, and then by pointing out that the value per visitor on his site was 29% higher for IE8 than it was for IE7. Using two simple tools you probably already have at hand, you can quickly calculate how a faster user experience correlates to greater order value on your own website. (We later used this post as the basis for a short webinar, which you can watch here.)
It’s a well-known fact that site speed is a critical ranking factor for organic search. One of the most-asked questions I receive is: How exactly does Google do this? Over the last year and a bit, I’ve done quite a bit of digging to get the answers. I thought it would be useful to start an FAQ-style repository for the answers.
Applying performance best practices in a general sense will take care of 80% of front-end web performance problems, but the last crucial 20% can only be achieved through painful real world testing and iterative problem solving. We need to find a way to do this quickly and cost-effectively. Back in January, this was my vision.
When Google announced their Page Speed service in July, the most frequent question fielded was, “Is the Page Speed service a threat?” In short, no. If anything, it offers yet more validation that site speed is a crucial business issue.
There’s a growing awareness of the fact that third-party content can cause a major hit to your website’s performance. Good. Great. Now we need to tackle what I’ve dubbed “fourth-party calls”. Not only can these insidious server calls leach performance, they also have massive security implications.
Aberdeen Group has reported that “A one-second delay in page load time equals a 16% decrease in customer satisfaction.” But what does that customer dissatisfaction look like in the real world? I searched Twitter to find out. It wasn’t pretty.
A concise example illustrating three important things about front-end optimization (FEO): the current performance rules are not complete; these performance rules will never be static; and the front-end optimization market is evolving faster than the current performance tools can measure.
Fascinating study: Brain wave analysis reveals that people have to concentrate up to 50% more when using badly performing websites. EOG technology and behavioral analysis also reveal greater agitation and stress in these periods.
I routinely encounter customers that have been led, by the very experts they trust, into believing that their site performance can be measured by the wrong tools. This post was written to explain exactly why you can’t always believe the experts.
This is my last post of 2011. Before I sign off for the year, I want to take a moment to thank you for coming to this site, for reading, and for your thoughtful comments. It’s a privilege to write for such an engaged community at such an exciting time in our industry. I’m looking forward to even more exciting times ahead.