Mobile Rage - What causes it & how to fix it.
summary
Mobile pages drive measurable rage: mobile load expectations jump from 58% to 71% and mobile bounce after five seconds rises from 20% to 74%, while ~23% curse, 11% scream and 4% throw phones. Fixes are concrete: swap heavy jQuery for micro frameworks like Zepto, compress images and CSS, use the Rails asset pipeline or upgrade pre‑3.1 apps, load JS at the bottom to show progressive render, and use proper input types (use the email input type and numeric keyboards, disable autocomplete/capitalize) to cut sign‑up churn.
AI-written summary · about
chapters (49)
- 0:00Introduction
- 1:19Mobile Gadgets
- 2:22What is Mobile Rage
- 3:05Who experiences Mobile Rage
- 4:50Why are things so bad
- 7:41Responsive design
- 8:20Mobile rage problem areas
- 9:13Landing
- 9:36Slow
- 10:43Rage
- 12:10JavaScript
- 14:20Bloated CSS
- 15:15Images
- 15:40CSS Images
- 15:58Upgrading Apps
- 17:05Flash
- 17:43Gary Treats
- 18:05Blank Screen
- 18:45Dont insult your customers
- 19:03Choose laughter
- 19:57Full site
- 20:55Forestry Direct
- 21:56Mobile Walled Garden
- 22:26Limited Function
- 22:38Mobile Detection Fail
- 23:44Mobile Apps
- 24:42Default App
- 24:58Advertising
- 25:48Popovers
- 26:40Lightbox
- 27:43Redirect
- 28:34Navigation
- 29:03Size Matters
- 29:53iPad Example
- 31:23Apple Guidelines
- 31:50Foam Finger
- 32:54Forums
- 34:21Wordpress
- 34:43Apple
- 35:11Fix it
- 35:29Sign up forms
- 35:48I Drive Pro
- 37:13You Win
- 37:40Autocomplete
- 38:06Profile
- 38:23Twitter
- 38:41Numbers
- 39:02Rage is growing
- 39:17More and more mobile users
related talks
53mPerformance Checklist for the Mobile Web
37mAdapting to the Mobile Web F̶u̶t̶u̶r̶e̶ Present
43mThe Mobile Web: MIA
13mMobile Web Performance and User Experience
48mDigital Spit Fire Interface Rage How to Calm the Savage User
46mThink Fast!
57mFrustrating Design Patterns in 2021, And How To Fix Them
19mBuilding Forms Mobile Users Will Love