search engine optimization

Your 10 favorite posts of 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.

1. Early findings: 97% of mobile end-user response time happens at the front end

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.

2. How to perform a 5-minute page speed/revenue analysis of your e-commerce site

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.)

3. The 12 most-asked questions about how Google factors page speed into its search rankings

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.

4. Automating complexity: The future of website performance optimization

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.

5. Google’s new Page Speed service: A handy resource for smaller site owners

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.

6. Fourth-party calls: What you don’t know can hurt your site… and your visitors

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.

7. Slow websites make people angry

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.

8. Front-end optimization: It isn’t over till it’s over. And it’s never over.

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.

9. This is your brain on a slow website: Lab experiments quantify “web stress”

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.

10. Why the performance measurement island you trust is sinking

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.

Related posts:

FAQs: The 12 most-asked questions about how Google factors page speed into its search rankings

It’s a well-known fact that site speed is a critical ranking factor for organic search. The big question has been how exactly Google does this. This is probably one of the most-asked questions I receive, and the answers aren’t easy to find.

Over the last year and a bit, I’ve done quote a bit of digging to get the answers, and I thought it would be useful to create an FAQ-style repository for the answers.

(Note: Google is, understandably, not 100% forthcoming with how it works. I’ve tried my best to fact-check my answers with Google employees and outside sources. If you think my answers are incorrect, let me know in the comments.)

1. Does the Google search bot track page load time?

No. The Google search bot has nothing to do with speed.

2. Does Google use synthetic test or real end user monitoring to gather its data?

I’ve talked in the past about how misleading speed metrics can be. Google actually uses real end user monitoring (RUM) to check site speed. This is the right thing to do. They’re measuring from users’ actual web browsers from real bandwidths — no simulations.

3. How does Google gather the data?

Google crowdsources page measurement by measuring site speed using the Google toolbar with Pagerank checking activated on the public’s computers. The results are “radioed” back to the mothership.

4. What browsers does the Google toolbar use?

The toolbar is available on Internet Explorer and Firefox only. More specifically, the toolbar is available on IE 6+ and Firefox 2-4. It is not supported on Firefox 5 which has led to speculation that Google has another plan for capturing this data but no other details have emerged.

5. What does the Google toolbar measure?

It measures onload time. This also includes third-party display ads, third-party scripts, etc.

6. What pages does Google measure?

They measure all pages visited by users on your site.

7. Do they measure pages marked as non-crawlable?

Yes. They measure pages your users use, not what you have told Google is crawlable

8. What if my page is personalized and has very different content for authenticated users but the same URL?

The measurement makes no distinction for personalized content if the URL remains the same. The results will be averaged together.

9. Does Google use its new Google Analytics page speed feature?

No, to the best of my knowledge they do not use any of the new data collected in Google Analytics for this purpose, but they should as it would allow them to sample more modern browsers.

10. Will pre-loading content on a page hurt my ranking?

No, because the results are based on the onload time measurement.

11. Will deferring a call help my rankings?

Yes. Anything that helps the page get to the onload event faster will help.

12. Will having pages start render faster help my rankings?

Unfortunately, no. It would be great to augment the system with some way to benefit pages that start loading faster.

Do you have any new/different/conflicting answers? Questions that aren’t answered here? Let me know in the comments.

For more reading on this subject, check out these articles:

Related posts: