Last week, we released our quarterly State of the Union for ecommerce web performance, which found (among other things) that the median top 100 retail site takes 5.4 seconds to render primary content, and 10.7 seconds to fully load.
Earlier this week, I had the privilege of speaking at the RWD Summit, alongside awesome folks like Tim Kadlec, Brad Frost, and Jenn Lukas. I presented some of the findings of research we conducted here at Radware about how mobile users engage with ecommerce sites, and how this engagement is affected when pages are slowed down even by marginal amounts.
Earlier this month, we released our quarterly State of the Union for ecommerce web performance. Today, I want to share the poster version of the infographics we created to accompany the report. Feel free to download and share. And if you have any questions about any of these findings, let me know.
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.
Important information for those who use Webpagetest’s video-capture feature to gather performance data.
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.
An historical overview of the evolution of the front-end performance industry, from 1995 to the present, highlighting everyone from early players such as Akamai and F5 to more recent entrants like Strangeloop and Aptimize.
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?
Updating my performance stats “cheat sheet” with brand-new data from Gomez and old-ish data from Forrester.
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.