At Radware, we recently released one of our most-anticipated reports of the year — our annual State of the Union for Mobile Ecommerce Performance. Today, I want to share the poster-style infographic we created to accompany the report. It offers a great snapshot of our key findings, as well as some background info about mobile commerce in general.
Mobile has never been more crucial to business success than it is right now. More than half of all time spent on retail sites takes place on a mobile device. The average online shopper makes 6.2 visits to a company’s website, using 2.6 devices, before they buy. And just a one-second delay in mobile load times can hurt conversions and cart size by up to 3.5%.
This is why sites need to perform quickly and consistently across all platforms. This is why it’s critical for site owners to have visibility into the real-world mobile performance of their sites. And this is why, every year at Radware, we study the mobile performance of the top 100 ecommerce sites to see how they measure up to user expectations.
Our latest report — the 2014 State of the Union: Mobile Page Speed and Web Performance — is now available for download. Today, I want to share some of our key findings and takeaways…
Autumn is shaping up to be a very full season, so I’m taking advantage of the relative quiet to take a little R&R. I’ll see you back here in September. In the meantime, here’s a roundup of posts that Google Analytics tells me people liked. I hope you like them, too.
Last week, I shared slides for my Velocity talk (and the report upon which the talk was based) about the impact of slow performance on user engagement and long-term brand satisfaction. But slow pages are just one way to irritate people who visit your site via a mobile device. Here are six more.
Earlier today, I had the privilege of speaking at Velocity Santa Clara on a topic near and dear to my heart: the mobile user experience. I presented research we conducted at Radware that I’m really excited about.
By now, most of us have internalized the fact that slow pages hurt mobile user metrics — from bounce rate to online revenues to long-term user retention. At Radware, we wanted to understand the neuroscience behind this in order to get a 360-degree view of mobile performance, so we engaged in the first documented study of the neurological impact of poor performance on mobile users. Here’s how we did it, and what we learned.
My recent post about page growth (or page shrinkage, as the case may be) hit a nerve with a lot of people, so this week I thought I’d take my first dive into the Mobile HTTP Archive, the mobile counterpoint to the HTTP Archive I cited last week. The Mobile HTTP Archive tests the same list of URLs, but it does so using smartphones. This means that if a URL redirects to a mobile site, the Archive tests the mobile site.
Just like last week, I looked at the top 1,000 URLs. What I found won’t come as a surprise to anyone who’s been following this blog for a while. While there are many similarities between these findings and last week’s, there are also a number of insights that are unique to mobile devices.
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.
Yesterday on Twitter, I posted a link to this Internet Retailer article about the results of a recent Keynote mobile index report. The report found that only two out of the 30 sites in the index use responsive design, and both those sites took 17+ seconds to load on mobile devices.
My Twitter post (sorry, I just can’t say “tweet”) generated some discussion about the challenges of making fast responsive pages, with some folks taking the stance that RWD and performance don’t play well together. This isn’t a new opinion, and it’s sparked a lot of debate in the past. (See this post from Tim Kadlec and this one from Guy Podjarny for excellent examples.)
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.