While TTI has improved since our last quarterly report, there is still a lot of room for improvement. To take a glass-half-full attitude, this represents a great opportunity for site owners who are ready to take the lead in delivering faster Time to Interact (TTI) for their shoppers.
Keep-alives and compression are two of the easiest, lowest-hanging fruit on the performance optimization tree, yet almost half of the leading retail websites aren’t taking advantage of these best practices simultaneously. How to identify and fix this problem on your site.
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.
We ignore IE 7 users at our peril. At the time of this writing, IE 7 has 15% market share. This doesn’t sound like much, until you translate that number into 15 out of every 100 living, breathing human beings who come to your site and are rebuffed by its poor usability.
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.
Kids need an almost instantaneous user experience, with page load times below 200ms. So why does the average kids’ website take more than 9 seconds to load?
Five popular ASP.NET-based content management systems — Sitefinity, DotNetNuke, Ektron, Kentico, and Sitecore — are on the receiving end of some late-night voodoo science, as I compare how quickly their clients’ websites load.
Web performance consulting: What is it? Is it worthwhile? How do you find a good consultant? I decided to take these questions directly to one of today’s leading performance consultants, Andrew King.
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.