Mobile is no longer on the sidelines. If you’re not already thinking mobile first, you should at least consider it. Let’s go over compelling data that demonstrate the importance of focusing on performance for mobile devices.

Business is Booming on the Mobile Web

Here are some figures showing the rapid growth of business on the mobile web.

55% of all time spent on retail sites takes place on mobile devices

This number comes from research by comScore for Shop.org1, released last fall. 44% of the time people spend on retail sites are on smartphones, and 11% on tablets.

This finding correlates to a statistic that was shared by UK-based online shoe retailer Schuh.com: Every month, 1% of their desktop traffic converts to mobile traffic2.

Mcommerce (mobile commerce) revenue is growing rapidly

Between 2011 and 2013, mobile revenues in the US more than tripled.

In 2013, mobile generated 16% of total ecommerce sales. By 2017, that number will increase to 26%.3 Think 26% sounds insignificant? It’s not — unless you think $113 billion is a trifling amount of revenue.

Mobile conversion rates lag behind desktop, but tablets are catching up

At the end of last year, the conversion rate for smartphone users was about a third the rate for desktop users.

Tablets, however, are catching up: at 2.59%, the conversion rate for tablets in the last quarter of 2013 had surpassed first quarter 2013 rate for desktop users.

Source: monetate.com

Most online shoppers “multi-screen” before they buy

More findings from comScore: In their February 2014 market review, they found that 57% of consumers access a company’s site from both their PC and mobile devices before buying.4 This puts a great deal of pressure on ecommerce developers to ensure a consistent user experience across all platforms.

Source: comscore.com

Mobile Sites Don’t Meet Users’ Expectations

Looking at all the stats we’ve just covered, there’s a clear disconnect between how much time people spend on retail mobile sites (55%) and how much money they spend during that time (16%)5.

There are a number of factors to explain the disconnect, but a critical one is page speed.

Slow pages are the number one issue that mobile users complain about, ranking even higher than site crashes.

Most mobile users expect pages to load at least as fast as (or faster than) they load on their PC

I need to stop being surprised when I talk to people who assume that mobile users will settle for sluggish load times, because that’s just the way the mobile world spins.

Those individuals couldn’t be more wrong: 85% of mobile users expect pages to load as fast as, or faster than, they load on the desktop.

Two out of three smartphone users say they expect pages to load in 4 seconds or less.6

Slow pages increase user frustration and decrease engagement during online transactions

Mobile users are affected at a neurological level by even small changes in a site’s speed.

In an Electroencephalography (EEG) study we ran last fall, we found that a 500ms delay in connection speed resulted in up to a 26% increase in peak frustration, and up to an 8% decrease in user engagement.7

Top sites aren’t meeting mobile users’ expectations for sub 4-second load times

Most users may expect wait times of 4 seconds or less, but our research8 shows that the majority of sites can’t deliver this kind of speed to mobile devices.

Last fall, we measured the load times of the top 100 ecommerce sites — both the full-site version and the m-dot version — on a variety of smartphones and tablets. We found that even m-dot sites, which are intended to deliver a faster experience, generally failed to meet users’ 4-second wait-time threshold.

Source: radware.com

Only 2% of the full-site versions loaded within 4 seconds, with the median load time being almost 8 seconds.

Source: radware.com

What Poor Mobile Web Performance Means for Business

The disconnect between user expectations and the reality of the current state of mobile web performance has a measurable impact on the bottom line.

Slow performance affects every business metric site owners care about, from shopping cart abandonment to brand perception.

The mobile shopping cart abandonment rate is 39% higher than the abandonment rate for desktop

The abandonment rate for mobile shopping carts is 97%, compared to 70% for desktop carts.9 This tells us that people are using their carts on mobile, which is good, but then they’re ditching them, which is obviously bad.

Slow performance is a critical factor, as is the pain of filling out long order forms.

Even a 1-second delay can hurt conversions

Even seemingly minor performance problems can have a major impact on mobile business metrics.

A while back, we did a split test over the course of 12 weeks, in which we segmented mobile traffic to an ecommerce into four groups: a fully-optimized control group, plus three groups that were subjected to 200ms, 500ms, and 1000ms HTML delays.

We measured the impact of these delays on:

  • bounce rate
  • conversions
  • cart size
  • page views

The 200ms delay yielded negligible results, but the negative impact was much stronger at 500ms and 1000ms.

The 1000ms delay resulted in a 3.5% decrease in conversions, which is huge hit.7

Slow pages drive mobile shoppers to your competitors

When their shopping experience goes wrong, not only do mobile consumers abandon their shopping carts, they also head to your competitors.

When faced with a negative mobile shopping experience, up to 33% of mobile shoppers will go to a competitor’s site next.

To make things even worse, up to 30% will never return to your site.10

Slow pages undermine overall brand health

In the same study I cited earlier, we asked all the participants in our mobile EEG study for their impressions of the sites after the tests were done. We then fed all the descriptors in the interviews into a word cloud generator.

This is the word cloud that was generated by test participants after using Tesco.com at normal speed:

And this is the word cloud that was generated by participants after experiencing the same site with a 500ms network delay:

Bear in mind that none of our test subjects were aware that they’d been involved in a study about page speed. They thought they were simply testing each site’s overall functionality.

It’s fascinating to see that the word cloud for the slower site contains almost three times more negative adjectives than the faster site.

While some participants clearly picked up on the slight deterioration in performance (“slow” and “sluggish”), participants also developed negative perceptions of areas that are unrelated to speed.

Slower pages affected people’s perception of three important aspects of the site that are completely unrelated to load time:

  • Content (“boring”)
  • Visual design (“tacky” and “confusing”)
  • Ease of navigation (“frustrating” and “hard-to-navigate”)

Why the Mobile Web is Slow

Aside from the obvious known limitations of mobile devices — smaller CPUs, slower network download speeds — there are two other limiting factors:

  1. page size
  2. latency

While responsively designed pages can be fast, most aren’t (even on the desktop)

Responsive web design is a great way to ensure that your pages have a consistent look across multiple platforms, but it’s not necessarily a great way to ensure that your pages are consistently fast across platforms.

I recently tested the start render and load times of 60 pages that have been included on various “best of RWD” lists. Only 3 of them loaded in 4 seconds or less — on desktop no less — meaning that they’re likely to load even more slowly on mobile devices.

The culprit: massive payloads.

Of the 60 responsively designed pages I looked at, many were 3 or 4 or even 5 MB in size.11

One thing the fastest sites all had in common was the fact that they were all under 1 MB.

Never underestimate the performance-killing power of latency

In performance terms, latency is the amount of time it takes for the host server to receive and process a request for a page object.

The amount of latency depends largely on how far away the user is from the server.

Mobile latency is consistent only in its inconsistency, even when measured at the same location. This is due to a number of variables beyond the amount of data passing through the tower. Factors such as the weather, and even the direction the user is facing, can have a significant impact.

Source: igvita.com

3G latency can reach 350ms or more per page resource.  And a typical page can easily contain 100 or more resources, so all this latency adds up fast.

This is why Google performance expert Ilya Grigorik has stated12 that if you’re designing for mobile, it’s safe to assume you’re going to incur 2000ms of 3G latency.

What can you do to give your mobile audience the user experience they demand?

There are a number of techniques for optimizing mobile performance.

Some of these techniques — such as compressing and consolidating resources — can help with both mobile and desktop issues.

Others — such as leveraging localStorage as a workaround for smaller mobile browser caches — are specifically focused on improving the mobile experience.

If you’re interested in taking a deeper dive into these techniques, check out this postI wrote for ACMQueue.

Note from the Editor (Jacob Gube)
If you’re curious to learn more about Tammy Evert’s theories on web performance and mobile, be sure to attend her sessions at O’Reilly’s Velocity Conferences this year.

Velocity is, in my opinion, one of the conferences all developers should go to. A lot of data, best practices, and techniques related to web performance are born at this conference.

Use code SIXREVISIONS20 when getting your ticket to save 20%.

Tammy will be in Santa Clara on June 24-26 and New York on September 15-17. These are her topics and additional information about the sessions:

References

    1. comScore and Shop.org Mobile Retail Boot Camp (summit13.shop.org)
    2. Conversion Conference – Schuh’s journey to RWD (slideshare.net)
    3. Mobile Devices to Boost US Holiday Ecommerce Sales Growth (emarketer.com)
    4. UK Digital Market Overview February 2014 (comscore.com)
    5. Keynote 2012 Mobile User Survey (keynote.com)
    6. Mobile stress: Slower web pages lead to increased user frustration and lower engagement (webperformancetoday.com)
    7. REPORT: 2013 State of the Union for Mobile Ecommerce Performance
    8. Google Aims To Simplify Mobile Shopping With ‘Instant Buy’ (webpronews.com)
    9. Case study: The impact of HTML delay on mobile business metrics(webperformancetoday.com)
    10. 88% of Americans Who Shop on Their Smartphones Experience Negative Issues…(marketwatch.com)
    11. 12 websites that prove RWD and performance CAN play well together(webperformancetoday.com)
    12. Latency: The New Web Performance Bottleneck (igvita.com)

13 Reasons Why You Should Pay Attention to Mobile Web Performance的更多相关文章

  1. Diode -- Pay Attention to Parallel Connection

    The above circuit is right. The two same resistors are integral. Because every diode is different, t ...

  2. Pay attention to "Changing"

    data l_ct_imseg type vsep_t_imseg. refresh l_ct_imseg. append lines of ct_imseg to l_ct_imseg. call ...

  3. hbase官方文档(转)

    FROM:http://www.just4e.com/hbase.html Apache HBase™ 参考指南  HBase 官方文档中文版 Copyright © 2012 Apache Soft ...

  4. HBase官方文档

    HBase官方文档 目录 序 1. 入门 1.1. 介绍 1.2. 快速开始 2. Apache HBase (TM)配置 2.1. 基础条件 2.2. HBase 运行模式: 独立和分布式 2.3. ...

  5. 课程五(Sequence Models),第三周(Sequence models & Attention mechanism) —— 1.Programming assignments:Neural Machine Translation with Attention

    Neural Machine Translation Welcome to your first programming assignment for this week! You will buil ...

  6. (zhuan) Attention in Long Short-Term Memory Recurrent Neural Networks

    Attention in Long Short-Term Memory Recurrent Neural Networks by Jason Brownlee on June 30, 2017 in  ...

  7. Hdu1896 Stones(优先队列) 2017-01-17 13:07 40人阅读 评论(0) 收藏

    Stones Time Limit : 5000/3000ms (Java/Other)   Memory Limit : 65535/32768K (Java/Other) Total Submis ...

  8. Unsupervised learning, attention, and other mysteries

    Unsupervised learning, attention, and other mysteries Get notified when our free report “Future of M ...

  9. hdu 4770 13 杭州 现场 A - Lights Against Dudely 暴力 bfs 状态压缩DP 难度:1

    Description Harry: "But Hagrid. How am I going to pay for all of this? I haven't any money.&quo ...

随机推荐

  1. 利用Python爬取电影网站

    #!/usr/bin/env python #coding = utf-8 ''' 本爬虫是用来爬取6V电影网站上的电影资源的一个小脚本程序,爬取到的电影链接会通过网页的形式显示出来 ''' impo ...

  2. P4382 [八省联考2018]劈配

    题目链接 题意分析 受到了\(olinr\ \ julao\)的影响 写了匈牙利算法 首先 我们对于每一个人 从高到低枚举志愿 如果当前志愿的老师有剩余的话 那么我们就选 否则的话 我们看看谁的那个志 ...

  3. 常用的PHP超全局变量$_SERVER 收集整理

    传送带:https://www.cnblogs.com/rendd/p/6182918.html

  4. 常见的http错误提示

    1xx(临时响应)表示临时响应并需要请求者继续执行操作的状态代码. 代码 说明100 (继续) 请求者应当继续提出请求.服务器返回此代码表示已收到请求的第一部分,正在等待其余部分. 101 (切换协议 ...

  5. 安卓手机移动端Web开发调试之Chrome远程调试(Remote Debugging)

    一.让安卓打debug模式的apk包 二.将电脑中的chrome升级到最新版本,在chrome浏览器地址栏中输入chrome://inspect/#devices: 在智能手机还未普及时,移动设备的调 ...

  6. DA14580_583_DK_II开发板入门笔记

    本文链接:http://www.cnblogs.com/obarong/p/8521893.html 1.介绍 开发板资料 参考文件: DA1458XDK蓝牙开发板用户须知1.3.pdf DA1458 ...

  7. Gradle学习系列(三)

    上一篇我们已经学习了 Gradle 打包,那么这一节 就开始讲讲本章的第二版块:打包及使用Gradle过程中的常见错误问题. 有时候我们需要编辑一个开源项目之类的,希望把它导入了我们自己的IDE工具中 ...

  8. linux inotifywait 下监控是否有IO

    帮助: JDU:/host-001e67a8d50b /log/today # inotifywait -h inotifywait 3.14 Wait for a particular event ...

  9. MySQL 连接注意事项

    外连接 A LEFT JOIN B join_condition 数据表B的结果集依赖数据表A 数据表A的结果集根据左连接条件依赖所有数据表 B表除外). 左外连接条件决定如何检索数据表B(在没有指定 ...

  10. 【Guava】PreConditions来校验参数

    前置条件:让方法调用的前置条件判断更简单. 在我们的日常开发中,经常要对入参进行一定的参数校验,比如是否为空,参数的取值范围是否符合要求等等.这种参数校验如果我们单独进行校验的话,代码的重复率比较高, ...