site speed

Is the J.C. Penney SEO scandal relevant to the web performance industry?

If you haven’t yet read The New York Times article The Dirty Little Secrets of Search, you should. It reads like a shady underground exposé of an art smuggling ring — making SEO sound almost glamorous. One of the most interesting things I’ve read all week.

What I found most interesting is the distinction the article makes between activities that are actually illegal and those that are “Google illegal”:

Despite the cowboy outlaw connotations, black-hat services are not illegal, but trafficking in them risks the wrath of Google. The company draws a pretty thick line between techniques it considers deceptive and “white hat” approaches, which are offered by hundreds of consulting firms and are legitimate ways to increase a site’s visibility. Penney’s results were derived from methods on the wrong side of that line, says Mr. Pierce. He described the optimization as the most ambitious attempt to game Google’s search results that he has ever seen.

In 2006, Google announced that it had caught BMW using a black-hat strategy to bolster the company’s German Web site, BMW.de. That site was temporarily given what the BBC at the time called “the death penalty,” stating that it was “removed from search results.”

BMW acknowledged that it had set up “doorway pages,” which exist just to attract search engines and then redirect traffic to a different site. The company at the time said it had no intention of deceiving users, adding “if Google says all doorway pages are illegal, we have to take this into consideration.”

J. C. Penney, it seems, will not suffer the same fate. But starting Wednesday, it was the subject of what Google calls “corrective action.”

The article doesn’t specify the exact terms of this corrective action, but it notes that J.C. Penney’s ranking has plummeted from #1 down to #68 and #71 (and worse) for several key search phrases.

A unilateral ranking change of that magnitude would be devastating to any web site. When the “mall” of the world places your store in the basement of the annex building, sales plummet and business dies.

I’ve been wondering if any of this J.C. Penney scandal is relevant to the performance industry. To date, I’ve always assumed that the automated optimization techniques used by Strangeloop and other solution providers fall into the “white hat” camp, since we derive some of our techniques from Google’s own list of performance best practices, and especially since Google has spearheaded the development of an open source tool for automating fundamental best practices called mod_pagespeed.

However, when you examine Google’s design and technical guidelines  perhaps we should not so confident. One area that caught my interest was around cloaking:

Cloaking refers to the practice of presenting different content or URLs to users and search engines. Serving up different results based on user agent may cause your site to be perceived as deceptive and removed from the Google index.

Most, if not all, of the sophisticated automated optimization solutions — Strangeloop included — serve different content to users and search engines. We do this to optimize performance, not to game search results. I have asked my friends at Google to look into this and I have been repeatedly reassured that the techniques we (and by extension our competitors) employ are safe.

Can someone at Google (Matt Cutts et al) confirm publicly for us that optimization by browser group is not “Google illegal”? That what we are doing is safe, helpful and harmonious with the Google mission of a faster web?

Has anyone else asked this question of Google? Can someone point me to a Google article that demonstrates that browser-based optimization is safe from the “cloaking” brush?

Related posts:

Slow websites make people angry

Stating the obvious, right? But I find that it’s easy to quote the well-known Aberdeen Group study and say “A one-second delay in page load time equals a 16% decrease in customer satisfaction” without thinking about the reality of that customer dissatisfaction.

So, inspired by Duncan McDougall’s recent post about searching “slow site” on Twitter to see what came up, I decided to have a go at it myself:

“Am staring at the HMRC website. It’s like staring into the abyss. Suspect hell is akin to waiting for a very slow website to load and crash.”
“Is it just me or is The Sims 3 Website like really freaking SLOW!!!! WTF EA, get some faster servers”
“Sprint’s “new” website is running so slow i feel like im running on a 14k modem.. so prehistoric stuff here..”
“Tmobile’s website reminds me of Dial Up Modems, so slow. #FAIL”
“Virgin Mobile’s site blows, mad slow and glitchy.”
“foursqure website damn slow #foursqure”
“@gizmodo @lifehacker I just had to unsubscribed from your news feeds. The new site design is too slow to load.”
“The gpodder.net website is horribly SLOW! It should not be allowed to have such a slow site in 2011! #notimpressedatall”
“Wonder if Verizon’s website is so slow because they charge themselves so much for data?”
“Why is Gmail so sluggish today? It’s almost as slow as using the MobileMe website. And that’s saying a lot!”
“Warning: The Smithsonian site is slow as molasses. >_>;”
“Jesus. The @WHSmithcouk website is super slow. I guess I’ll just go in-store and hunt for what I want ;l”
“Is the Borders website slow because my Internet is slow or because it’s facing imminent death? (Either way this makes me sad)”
“Hey @GoDaddy, how do I know when my site, hosted by you is slow? It’s when my 93 yr. old Grandma can get the job done on her abacus faster.”

Slow websites make people frustrated and angry. We all know this. But it never hurts to get a real-world reminder.

Related posts:

Page load speed races:
AOL vs The Huffington Post

Everyone has their own take on AOL’s acquisition of The Huffington Post. Here’s mine:

AOL has a proven commitment to performance, but is weaker on the content side. Huff Post is editorially stronger, but how does it compare, performance-wise? What do these two media entities have to teach each other?

Who was faster?

I ran Webpagetests on a half dozen of each of AOL’s and Huffington Post’s parallel properties. The first batch of tests pit the landing pages of these sites against each other:

  • Huffington Post home page vs AOL home page
  • Huff Post Sports vs AOL Sports
  • Huff Post Entertainment vs AOL Entertainment

Here are the results:

In round two, I put these sites in the ring:

  • Huff Post Tech vs AOL Tech
  • Huff Post World vs AOL World
  • Huff Post Business vs AOL Business

Here’s how they looked:

And the winner is…

The AOL pages came out well ahead, with an average load time of about 8.5 seconds. The average load time for the Huffington Post pages was almost twice as long — 16.3 seconds (dragged down considerably by the Huff Post Business page, which had a bit of script that took ages to finally load and resulted in a final load time of 30 seconds).

How fast did they deliver usable content?

Since wonky scripts can skew load time numbers (and since mega-blogs seem to have more than their share of wonky scripts, due to ads, banners, and social media widgets), I thought it would be more fair to look at the sites from a user’s perspective, and focus on the time it took for meaningful content to load. I used Webpagetest’s slide view to get a frame-by-frame look at round one and round two.

  • All of the AOL pages started delivering usable content by the 3-second mark.
  • At the 6-second mark, only four out of six of the Huffington Post pages had started to deliver usable content. The remaining two — World and Sports — started to deliver at 7.5 and 8 seconds, respectively.

I’ve read comments to the effect that AOL is where acquisitions go to die. I’d argue that this doesn’t have to be the case. Between Huff Post’s content and AOL’s performance experience and audience reach, these two entities are primed for success. Developing a killer performance strategy could take them to the next level.

Related posts:

Is web performance optimization a “green” issue?

I live in a city with a bold ambition: to be the greenest city in the world by 2020. I try to do my part. I take the bus or walk to work, my family has only have one car that we use rarely, and we even use the ugly energy-efficient Christmas lights.

When it comes to my work, I also believe that I have a positive impact, and it makes me feel good when green is highlighted in our industry.

Last May, Steve Souders came up with a list of predictions about the future of web performance optimization. Prediction #3 was this:

“Finally we’ll see studies conducted that quantify how improving web performance reduces power consumption and ultimately shrinks the web’s carbon footprint.”

When I first read this, my immediate reaction was, “Wow. That’s a really cool, bold expectation.” Ever since, I’ve kept my eyes open for anything I can find about the impact of performance on energy use. Maybe I’m hanging out in the wrong part of the internet, but I haven’t had much luck.

Analyzing the trade-off between performance optimization and energy use is a huge challenge. It’s not enough to say, “We’re delivering smaller pages and fewer/smaller objects, therefore using less energy. Problem solved!” We also have to take into consideration:

  • the energy consumed by new machines added to the network to automatically transform web pages,
  • the impact on servers as more is offloaded in the network,
  • the change in use of a content delivery network,
  • the change in energy consumption at the client level based on increased or decreased CPU use,
  • the change in energy consumption of the user as they browse more pages and buy more,
  • etc., etc.

So while it would be great to see a simple “If _____, then _____” equation for calculating performance/energy savings, perhaps it’s not a huge surprise that not a lot of people have tackled this big hairy question.

A (very) few people have tried to tackle this question. These are the best articles and blog posts I’ve come across:

Steve Souders: How green is your web page?

This blog post is almost three years old, but still worth reading. Huge kudos to Steve for this exercise in quantifying how specific performance improvements (he uses Wikipedia as an example) could lead to energy savings. When I imagine helpful equations for calculating performance/energy benefits, I imagine them looking a lot like this.

Boston.com: Taking a different measure

Really interesting article that came out last fall about how Akamai is auditing the carbon footprint of its 70,000-server network. It’s a hugely ambitious project, which the company undertook after realizing that 87% of its carbon footprint came from its network operations. This is the kind of data we need. It’s a key piece of the puzzle in figuring out how to quantify performance and energy use.

Fast Company: Is the Internet Sustainable When Everyone On Earth Uses Over 3 Gigabytes of Data Per Day?

Scary quote alert…

“That’ll come to 2,570 exabytes per year for the global population, by 2030. (An exabyte is a billion gigabytes.) The average power needed to sustain such activity would be 1,175 gigawatts. It takes an entire large coal-fired power plant to produce just one gigawatt of energy, so imagine 1,175 of those churning out power just to fuel the world’s data hunger.”

That piece came out right before Christmas, and the fact that it appeared in a relatively mainstream publication like Fast Company is an indicator of the fact that these questions are not going to go away.

According to this report, video is a major bandwidth hog. Streaming/downloaded content from Netflix, YouTube, BitTorrent, and iTunes accounts for 40% of peak U.S. web traffic. (It may be a sad statement that, when I learned that YouTube users are uploading 35 hours of video per minute, my reaction was, “That’s all?”) Video also dominates mobile in pretty much the same proportion.

And that’s just the activity in the United States. Internet users in China log a total of one billion hours online every day, twice as much as Americans. Adoption rates are expected to more than double in the next three years, and not just in China. India, Brazil, Russia, and Indonesia are also poised to see a huge growth in the amount of time their citizens spend online.

So that’s it, the sum total of information I’ve found.

I’m an optimist. I believe that most problems have solutions. My hunch tells me that Steve is correct in postulating “Make your pages faster. It’s good for your users, good for you, and good for Mother Earth.” However, I don’t think we have enough data to confirm or deny what seems obvious. We need more data, and I for one am trying to work with customers to put together case studies that demonstrate positive environmental impact, as much for myself, so I can sleep at night, as for our industry as a whole.

Related posts:

Delivering customer experience: Bridging the gap between bricks and clicks at the NRF

Strangeloop is at the NRF’s Big Show this week (if you’re there, stop by booth 2843 and say hi to Nat, Kerry, and Kelly), so of course I’ve been following the NRF blog closely. This post yesterday jumped out at me: 9 retailers who get customer experience right.

The post highlights companies’ efforts in the bricks and mortar world, focusing on things like great staff and product selection. But since, to my mind, customer experience extends to the online world, I couldn’t resist doing a little cheap and easy performance testing.*

Here’s a screen grab of the first 3 seconds of load time for the home pages of all nine sites:

NRF: Home page load times for 9 top retail websites

As you can see, after 3 seconds, no usable content had loaded on any of the sites. If you click through the image, you can see the full filmstrip, which shows that the first page to load usable content was the Wiliams-Sonoma home page, at 3.5 seconds. Anthropologie and Chipotle Mexican Grill were the latecomers, taking 9.5 and 17 seconds, respectively, to load usable content.

These are good companies, and I believe that they deserve NRF’s praise for their focus on customer service. And the performance of their sites is fairly typical of ecommerce sites in general, so I don’t think they have anything in particular to be embarrassed about. But given their focus on offline customer service, and given this other NRF post — Why has the web won? — I think the days of settling for 3.5 seconds as an acceptable time frame for loading usable content are numbered.

*All tests conducted on Webpagetest — IE7 on DSL via the server in Dulles, VA. See the test results page, with links to the individual results page for each site, here.

Related posts: