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.)
Google Instant is going to fundamentally change how people search. Eventually, page 2 search results are going to be irrelevant. Page 1 will be the new bar. The companies that hit that bar will be the companies that are ready to squeeze every last ounce of performance from their sites.
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.
VIDEO: O’Reilly’s Mac Slocum interviewed me at Velocity, and we covered a few topics: mobile web performance, the difficulties of data gathering, site speed and SEO, and easy ways that every “mortal company” (aka a company that’s not Google, Microsoft or Amazon) can optimize their site.