In the spirit (um, no pun intended) of this spooky season, we came up with this set of infographics to illustrate some scary stats around ecommerce performance. Try sharing these with a colleague to see if you can give them a fright. You know, as an alternative to leaving a fake severed hand on their desk.
Performance has only recently started to make headway into the conversion rate optimization (CRO) space. These inroads are long overdue, but still, it’s good to see movement. In the spirit of doing my part to hustle thing along, here’s a collection of infographics representing real-world examples of the huge impact of page speed on conversions.
This past Wednesday, I had the great privilege of hanging out with the New York Web Performance Meetup crowd, and doing a session on web performance automation. Here’s the slide deck and an overview of the session highlights.
Yesterday the Reddit community made Subway.com the target of a driveby performance critique. Today, Subway.com released a better-optimized site, with thanks to the Redditors.
After a stint as the poster child for web performance optimization, Shopzilla lost its way and saw its page load times slowly creep from an impressive sub-2 seconds up to more than 5 seconds. Lead architect Tim Morrow explains exactly what went wrong.
It’s not enough to have a fast site. Time after time I see “high performance” sites that make the same mistake: having their most important content load dead last. Here’s a case study from Symantec.com.
The mainstream web performance community is rapidly amassing reams of data in this area. But when it comes to the mobile web, we’re pretty much at square one. The problem is threefold: lack of performance-measuring tools, need for large-scale A/B testing, and lack of information sharing.
No two performance tests give the same results. To illustrate, I put a high-traffic site, Target.com, through its paces on a handful of commonly used tests — Gomez, Keynote, HTTPWatch and Webpagetest — to see how it performs.
In this webinar, Hooman Beheshti analyzes Google’s home page performance using Web Page Test and HTTPWatch, demonstrates how to interpret waterfall charts, and talks about ways to diagnose and isolate common web application performance problems.
Mystified by waterfall charts, or know someone who is? Today I thought it would be a good idea to take a bird’s eye view of a typical performance waterfall – pre- and post-acceleration – that you can take away for your own reference or pass along to anyone you think could benefit from having this information.