Users are now browsing the Web across smartphones, tablets and the desktop. Find out how performance differs for each screen and what to consider in order to deliver a great online experience.
6. DESKTOP SMARTPHONE TABLET
Source: Yankee Group and Keynote Systems, 2012
Verizon and AT&T wireless connections were used for the smartphone and tablet device measurements
7. Site performance across 3-screens varies… Dramatically
Desktop performance does not
carry over to smartphones and
tablets
No website was in the top 3
across all the different screens
Most websites send the same
content to smartphones and
tablets
Source: Yankee Group and Keynote Systems, 2012
Verizon and AT&T wireless connections were used for the smartphone and tablet device measurements
8. Site performance across 3-screens varies… Dramatically
Desktop performance does not
carry over to smartphones and
tablets
No website was in the top 3
across all the different screens
Most websites send the same
content to smartphones and
tablets
Source: Yankee Group and Keynote Systems, 2012
Verizon and AT&T wireless connections were used for the smartphone and tablet device measurements
9. Smartphones & tablets: Why so much difference?
Source: Yankee Group and Keynote Systems, 2012
10. 3-screen approach: Optimize with mobile in mind
Connection
- Assume 3G, not PC… even for tablets
Design
- Screen size and touch
Page Construction
- Minimize HTTP requests
- Data URIs
- Minimize redirects
- Manage third parties carefully
12. Be direct
Latency of mobile is 5X to 10X Web
- TCP connection 100MS -300MS
- First Packet 300MS to 700MS
- Each roundtrip really counts!
Avoid redirections whenever possible
(exception: HTTP to HTTPS)
Limit DNS lookup per page to 1
Always use HTTP Keep Alive
CVS improved their load time 13% by
eliminating 2 redirects
13. Keep it light
Try to limit number of
elements per page to <10
new HTTP requests
Audit image content for
appropriate resolution,
quality settings and
compression
Bytes downloaded 97 KB Bytes downloaded 2318 KB
Images 15 Images 32
Page elements 20 Page elements 57
14. Data URIs: Caution
Embedded content strategy
Good solution for reducing
HTTP requests/round-trips
Bad for content used in
subsequent pages
(not cached)
Results may vary! Test and
monitor.
Page “1” Page “2”
Data URIs improve performance …but subsequent page impacted
after change… due to images not cached
Keynote Performance Consulting case study
15. Watch third parties
More requests/round trips
Load after point of initial
render
Asynchronous loading
Limit to 1 – 2 calls per
page… at most
Audit continuously
16. Find your own path
There is NO one-size-fits-all solution
Commit to accurately & consistently
measure performance
- Baseline and compare
Optimize based on where you have
issues/latency
Acknowledge and work within your
technical constraints
Learn from the Hotels.com journey
Top of the World by Izzard, on Flickr