Last week, I had the great privilege of presenting an O’Reilly webcast as part of the lead-up to Velocity Santa Clara. The catch was that I didn’t want to give away what I’ll be presenting at Velocity, so I needed to come up with a brand-new topic. I decided to talk about third-party scripts, for two reasons…
I talk to a lot of people who have taken on the role of in-house performance evangelist at their organization, and I know it can be a hard, lonely job. Often it’s a self-appointed role because you’re genuinely passionate about web performance. And often you’re fighting a one-person battle in a workplace that’s already struggling to cover a lot of other technical bases with limited resources.
Over the past few months, we’ve been slowly rolling out Expert Talks, a series of easy-to-digest, solution-agnostic videos that provide brief explainers of key performance concepts. One of our goals in creating this series is to make it easier for you to evangelize within your organization by offering videos that you can use to explain whatever performance issue you’re trying to define or solve.
I ran side-by-side performance tests of TechCrunch, Mashable, GigaOM, Technology Review, and the tech blogs for the New York Times and LA Times. My point: to illustrate why, if you’re looking at just the amount of time it takes for your pages to load, you may be focusing on the wrong thing.
The three greatest third-party performance culprits — performance-leeching widgets, badly designed ads, and poorly optimized pages — and real-world tips for dealing with them.