Velocity 2012: The 90-Minute Mobile Optimization Life Cycle

The 90-Minute Mobile Optimization Life Cycle Velocity 2012 Hooman Beheshti VP Technology, Strangeloop hooman@strangeloopnetworks.com

Agenda•  Why is faster better?•  Measuring performance –  Tools –  Challenges•  Stepwise acceleration –  Pick a real site, and apply step by step performance optimizations•  Lessons from the field© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 2

Mobile Performance OptimizationWhy Should We Care?

Experiment•  Induce delay on HTML –  200msec, 500msec, 1000msec•  Apply to small percentage of traffic•  12 weeks•  Monitor impact on key business metrics© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 10

More Details•  http://www.webperformancetoday.com/ 2011/11/23/case-study-slow-page-load-mobile- business-metrics/•  http://velocityconf.com/velocityeu/public/ schedule/detail/21632© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 14

Performance MeasurementMeasuring Page Speed on Mobile Devices

Measurement•  Mobile measurement is still a challenge•  There are some tools out there –  Still pretty manual –  Less about performance and more about functionality –  Lots of simulation•  More complicated because of the number of different platforms and devices that we may need to cover•  Things are getting better© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 16

Chrome Remote Debugging (ICS)•  A USB connection lets us see activity of mobile chrome on desktop chrome•  https://developers.google.com/chrome/mobile/ docs/debugging© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 17

Weinre (Web Inspector Remote)•  Remote debugging from the desktop for what the phone is doing•  http://people.apache.org/~pmuellr/weinre/docs/ latest/Home.html© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 19

Mobile Perf Bookmarklet•  More focus on performance•  http://stevesouders.com/ mobileperf/mobileperfbkm.php•  Super bookmarklet with lots of tools built in© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 21

Real User Monitoring (RUM)•  RUM tools are increasing in availability –  Google Analytics –  New companies and solutions emerging•  Measurement on actual devices, for real users•  Need lots of data to draw conclusions –  And must have a way to deal with outliers•  Navigation Timing (only in Chrome for Android right now)© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 23

Webpagetest’s Mobile Agent•  Based on the recently open-sourced mobitest agent•  Interacts with the server just like a standard desktop agent•  Available for Android and iOS –  Still in the early stages, but key metrics are reported –  Some features (like scripting) don’t work –  Cold cache tests and videos are working fine –  For iOS, it uses UIWebView rather than Safari•  Even with the limitations, still the best tool for getting a feel for mobile performance© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 25

Visualizing Performance Back End: The time from when the request is made by the browser to last byte of the HTML response 0 6 12© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 30

Visualizing Performance Back End: The time from when the request is made by the browser to last byte of the HTML response Front End: Everything after the HTML arrives 0 6 12© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 31

Visualizing Performance Back End: The time from when the request is made by the browser to last byte of the HTML response Front End: Everything after the HTML arrives Important Timers: Start Render onLoad (Document Complete) 0 6 12© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 32

Stepwise AccelerationAccelerating a Real Site

Setup•  All testing done on 3G from Vancouver –  Nexus S with WPT agent –  Rogers Network•  Traffic flows through Strangeloop service –  We apply optimizations in the path –  Used host file entries since DNS overwrite isn’t available on the agent•  The phone does everything else© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 35

A Few Points of Clarification•  We’re only choosing oreilly.com for fun•  We’re using it only to show what some performance problems are – this doesn’t mean the site has these problems•  The real site is somewhere in the middle of this blue bar© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 40

Time to First Byte•  Every request is subjected to one round trip•  Concurrency of requests helps, as does pipelining – but it’s still a problem –  More on pipelining later•  A bigger problem when there are more objects© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 52

Too Many Round Trips•  Every request is still paying a penalty –  TTFB continues to be a problem•  The higher the latency, the bigger the problem•  Better concurrency on modern mobile browsers is helping, but not enough. This is still a huge problem© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 55

Performance Problems•  Too many connections•  Too many bytes•  No CDN•  Too many round trips•  Poor caching (more on this later)© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 56

Performance Problems•  Too many connections•  Too many bytes•  No CDN•  Too many round trips•  Poor caching (more on this later)•  3rd party calls (marketing tags, analytics, etc)© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 57

Performance Problems•  Too many connections•  Too many bytes•  No CDN•  Too many round trips•  Poor caching (more on this later)•  3rd party calls (marketing tags, analytics, etc)è Similar to desktop, but impact is different onmobile devices© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 61

Key Metrics – Original Site Round trips to onload Bytes to onload (KB)100 100090 90080 80070 70060 60050 50040 40030 30020 20010 100 0 0 Start Render (sec) Doc Complete (sec) 9 25 8 20 7 6 15 5 4 10 3 2 5 1 0 0 © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 64

What Are We Going To Do?•  Stepwise acceleration –  We’ll accelerate the page in multiple steps –  We’ll add techniques at each step and evaluate the performance impact•  We’ll start with the easy stuff and get more advanced with each step•  Try to make the page as fast as possible© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 66

Step 1: Optimizations•  Add keep-alive connections –  Address the problem with too many connections –  Lessen the impact of TCP connection setup•  Add HTTP compression –  One way to reduce bytes, and an easy one –  We’ll compress text-based content (HTML, CSS, JS, etc)© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 68

Step 1: What Should We Expect•  Fewer total connections•  Fewer bytes•  Impact to performance metrics –  Fewer bytes to onload –  No change to roundtrips –  Better document complete time –  Better start render© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 71

Step 1: Improvements Round trips to onload Bytes to onload (KB)100 100090 90080 80070 70060 60050 50040 40030 30020 20010 100 0 0 Start Render (sec) Doc Complete (sec) 9 25 8 20 7 6 15 5 4 10 3 2 5 1 0 0 © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 75

Step 1: Improvements Round trips to onload Bytes to onload (KB)100 100090 900 94580 80070 218 70060 60050 500 23 % 72740 40030 30020 20010 100 0 0 Start Render (sec) Doc Complete (sec) 9 25 8 7.738 20.52 20 7 0.679 5.231 6 15 5 4 ~9% 7.059 10 25 % 15.289 3 2 5 1 0 0 © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 76

Pros and Cons•  Pros –  Really easy to do –  Usually a single configuration option on servers, proxies, or load balancers –  Great bang for the buck•  Cons –  It’s still slow! –  These are, by themselves, just not enough© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 78

CDN•  Static resources are served from locations near the requesting client (mobile or otherwise)•  Shorter distance between client and content means smaller TTFB© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 81

What Should We Expect•  Faster average time to first byte for the objects on the page•  Impact to performance metrics –  No change to round trips –  No change to byte count –  Better start render time –  Better document complete time© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 82

Step 2: Improvements Round trips to onload Bytes to onload (KB)100 100090 90080 80070 70060 60050 50040 40030 30020 20010 100 0 0 Start Render (sec) Doc Complete (sec) 9 25 8 7.059 15.289 20 7 0.814 1.552 6 15 5 4 12% 6.245 10 10 % 13.737 3 2 5 1 0 0 © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 88

Pros and Cons•  Pros –  CDNs are always good ways to reduce TTFB –  Physics! –  Well-established industry; lots and lots of vendors•  Cons –  Can sometimes be costly –  Why wasn’t it faster?© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 90

CDNs for Mobile•  We got faster, but we expected more of an improvement –  Before: we forced requests to go from west coast to east coast –  After: let the CDNs naturally select closest edge•  Wondering out loud… –  Is edge selection for mobile devices not as effective? –  3G more of a mystery than WiFi© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 91

CDN Edge Selection - Desktop Edge Cache Edge Cache DNS Resolver CDN DNS Brains Origin Origin Edge Cache Data Center Edge Cache© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 92

CDN Edge Selection – Mobile Network DNS Edge Cache Resolver Edge Cache ? CDN DNS Brains Origin Origin Edge Cache Data Center Edge Cache DNS Resolver© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 93

CDN Edge Selection – Mobile Networks•  I have no idea how the inside of the cell networks work!•  Test: –  From the phone (on 3G) ping 2 CDN names –  From the phone, ping the IP address the CDN resolved for my desktop© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 94

CDN Edge Selection – Mobile NetworksBoth pings from phone CDN 1 Ping cdn.domain.com Both pings from phone CDN 2 Ping IP that CDN picked for desktop © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 96

Important Questions To Ask•  Not making outrageous claims like “CDNs aren’t effective for mobile devices”!!•  CDNs almost surely deploy servers near cell network exit points. But, what if most of the latency is inside the cell network?•  Does the meaning for “closeness” change for mobile?•  More research is necessary…© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 98

Mobile FEO•  Consolidation of resources –  Images –  CSS –  JavaScript•  Image Compression•  Minification –  JavaScript –  CSS•  Optimal use of localStorage (more on this later)© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 100

What Should We Expect•  Fewer round trips will mean the TTFB problem should get a lot better•  Fewer bytes will mean better performance –  Images (from image compression) –  CSS/JS (from minification)•  Impact to performance metrics –  Reduction in round trips –  Reduction in byte count (on top of HTTP Compression) –  Better start render time –  Better document complete time© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 102

Step 3: Improvements Round trips to onload Bytes to onload (KB)100 100090 90080 800 72770 92 70060 600 310 6450 50040 40030 300 417 2820 20010 70 % 100 43% 0 0 Start Render (sec) Doc Complete (sec) 9 25 8 20 7 6.245 13.737 6 2.589 15 4.260 5 4 10 3 3.656 9.477 2 5 1 41% 31 % 0 0 © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 107

Pros and Cons•  Pros –  Noticeable and significant benefit over easier techniques –  The mobile form factor lets us be more aggressive with some of the techniques –  Smart use of localStorage•  Cons –  It’s not easy! –  Techniques must survive site changes (regression)© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 109

What Should We Expect•  Deferral of round trips to after onload•  Impact to performance metrics –  Fewer round trips to onload –  Fewer bytes to onload –  Better start render time –  Better document complete time© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 114

Step 4: Improvements Round trips to onload Bytes to onload (KB)100 100090 64 % 900 34 %80 80070 70060 60050 500 28 41740 40030 18 300 14220 20010 100 10 275 0 0 Start Render (sec) Doc Complete (sec) 9 25 8 41% 41 % 20 7 6 15 5 4 3.656 9.477 10 3 3.92 1.493 2 5 1 2.163 5.557 0 0 © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 121

Pros and Cons•  Pros –  Gives you the control that your marketing team may have given away! –  Solves a very difficult problem, resulting in improvements to all key metrics –  Much better visual experience•  Cons –  Again, not easy! –  Must understand what the purpose of each 3rd party call is© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 123

Overall Improvements Round trips to onload Bytes to onload (KB)100 100090 90080 89 % 71 % 80070 70060 60050 93 500 94540 40030 83 670 30020 20010 100 10 275 0 0 Start Render (sec) Doc Complete (sec) 9 25 72 % 8 7 20 73 % 6 15 5 7.738 20.52 4 10 3 5.575 14.963 2 5 1 2.163 5.557 0 0 © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 126

Mobile Caching•  The primary issues with mobile caching: –  where to put the objects –  the size of the cache•  Some good reading –  Device Cache Sizes •  Wink toolkit study: http://www.winktoolkit.org/blog/204/ •  YUI study: http://www.yuiblog.com/blog/2010/06/28/mobile-browser-cache-limits/ •  Blaze study: http://www.guypo.com/mobile/understanding-mobile-cache-sizes/ –  Individual Files •  Steve Souders: http://www.stevesouders.com/blog/2010/07/12/mobile-cache-file-sizes/ •  More from YUI: http://www.yuiblog.com/blog/2010/07/12/mobile-browser-cache-limits- revisited/© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 133

Mobile Cache Sizes•  Cache sizes are much smaller than desktop –  Android (2.x) about 5-7MB –  iOS is larger (>50MB)•  We need to think about: –  Total cache size limit –  Individual object size limit –  HTML pages•  User behavior may affect what’s served from cache•  Things are getting better, but not at the pace we want© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 134

Some More Findings•  Android: –  Firefox and Opera (Gingerbread): ~10MB –  Stock browser in ICS: 25MB –  Chrome on ICS: much larger and based on amount of space available •  http://gent.ilcore.com/2012/02/chrome-fast-for-android.html•  Android and iOS –  When there’s room available, saw aggressive caching behavior© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 135

Comparison to Desktop•  IE –  http://blogs.msdn.com/b/ie/archive/2011/03/17/internet- explorer-9-network-performance-improvements.aspx –  Defaults •  IE 6/7/8 à 1/32 of disk, cap of 50MB •  IE9 à 1/256 of disk (bigger disks), cap of 250MB•  Chrome –  Spot checked: >300MB•  Firefox –  Spot checked: >700MB•  From Steve: http://stevesouders.com/cache.php© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 136

HTML5 localStorage•  W3C’s Web Storage Spec: –  http://dev.w3.org/html5/webstorage/•  Per domain storage –  Key/value pairs –  ~2.5MB –  Test it: http://dev-test.nemikor.com/web-storage/support- test/•  Programmable –  It can be used for whatever you want –  This includes acting as a programmable object cache!© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 137

localStorage as a Cache•  It gives us new space, not shared, to use for caching•  It’s programmable and scriptable, something we’ve never had with HTTP object caches•  Typically good for caching CSS and JavaScript, especially those used site-wide•  Could also be used for small images –  Using DataURI format for images© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 139

A Little Bonus!Maybe there’s another site we can accelerate…

Functional Acceleration•  Most images are not in the immediate viewport•  Lots of round trips blocking start render•  This time, we’ll accelerate with an eye towards: –  Improving start render time –  Making the page available quicker© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 146

Deferral•  Let’s defer: –  3rd party calls (like before) –  Images not in the viewport•  Also basic Mobile FEO –  Image compression and minification –  Some consolidation of CSS and JavaScript•  What should we expect –  Better start render time –  Better document complete time –  Better visual response – snappier page© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 148

Defer less images•  Let’s not defer one scroll of images –  User can scroll faster and still have the next screen’s images available•  If the visual response is just as fast, then this is a good option if we expect people to scroll on our site right away© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 157

It’s Not Always About Every Metric!•  Visually, we’re about the same as full image deferral, but 4 images are available 2 seconds earlier•  Some of this can be done programmatically – dynamic decisions made by the browser –  Figure out coordinates for image; choose to download now or later© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 162

Cache the HTML•  Cache the HTML base page itself –  Somewhere in front of the server, before the browser –  In this case, it’s a feature of the service•  Eliminate server processing time –  Serve the HTML faster –  Improve TTFB of the page and all other performance metrics© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 168

HTML Caching•  HTML is typically dynamic –  It can be static for short periods of time (the velocity home page is a good example) –  Some technologies allow fragmentation of the page into static and dynamic portions•  HTML can be user-agent specific –  For velocity’s home page, the same URL generates different pages depending on the browser•  With HTML Caching, we need extra smarts: –  Granular expiration –  Browser aware –  Careful with personalized content© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 174

We Covered Everything, right?Not Quite…

Not Done Yet•  We may have made these 2 pages faster, but there’s a lot more to mobile optimization•  Performance is not only about pages –  We should always think about the site•  Optimizations should include operational improvements specific to mobile devices© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 176

More Performance Optimizations•  Converting click events to touch events –  Can save up to 500msec per event•  Smart use of localStorage –  Versioning –  Dynamic decisions based on state of localStorage•  Redirect suppression –  Sites that initially redirect to mobile version incur a costly roundtrip•  3G vs WiFi –  navigator.connection.type – Android only for now© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 178

Operational and Other Optimizations•  Hiding the URL bar•  Smart image loading for pinch to zoom –  Automatically detect pinch and grab higher resolution image•  Viewport optimizations –  E.g. Automatic detection of viewport•  Mobile meta tags•  Great presentation from Max Firtman: –  http://velocityconf.com/velocity2011/public/schedule/ detail/19976© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 179

Lessons Learned From The FieldThings you should know about mobile devices

Mobile Cache Behavior User With Last-Modified Device No Cache Headers* With Last-Modified* With max-age* Action and max-age* Android (Nexus S, v2.3.7) All from cache All from cache All from cache All from cache New window or tab iOS (iPhone 3GS, v5.1.1) None from cache All from cache All from cache All from cacheExit browser, Android (Nexus S, v2.3.7) All from cache All from cache All from cache All from cache lock phone,unlock phone,open browser iOS (iPhone 3GS, v5.1.1) None from cache All from cache All from cache All from cache Android (Nexus S, v2.3.7) All from cache All from cache All from cache All from cache Kill browser,launch browser iOS (iPhone 3GS, v5.1.1) None from cache All from cache All from cache All from cache Android (Nexus S, v2.3.7) All from cache All from cache All from cache All from cacheReboot phone iOS (iPhone 3GS, v5.1.1) None from cache All from cache All from cache All from cache After page If-Modified-Since and If-Modified-Since and Android (Nexus S, v2.3.7) All from cache All from cache loads, click Cache-Control:max-age=0 Cache-Control:max-age=0 URL and hit enter iOS (iPhone 3GS, v5.1.1) None from cache All from cache All from cache All from cache Android (Nexus S, v2.3.7) Cache-Control:no-cache Cache-Control:no-cache Cache-Control:no-cache Cache-Control:no-cache Refresh after page loads If-Modified-Since and If-Modified-Since and iOS (iPhone 3GS, v5.1.1) Cache-Control:max-age=0 Cache-Control:max-age=0 Cache-Control:max-age=0 Cache-Control:max-age=0 *Images only: filled cache through a page that referenced ~2MB of images, all with some or no caching headers; then performed user action © 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 182

Packet Drop Penalty•  Now, a packet dropped could mean multiple HTTP requests got dropped•  Good reading: –  http://www.guypo.com/ mobile/http-pipelining-big-in- mobile/•  Things to know –  Make sure everything in the middle supports pipelining –  Be aware of HOL blocking© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 188

TCP’s Initial Congestion Window (init_cwnd) SYN! SYN/ACK! ACK! GET /!TI Client ServerM 200 STATUS OK (+Data)! (init_cwnd =6)E Data! Data! Data! Data! Data!© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 190

TCP Windows•  Increasing init_cwnd is a common performance recommendation –  Google recommends 10 –  Most high performance proxies and load balancers have init_cwnd of much higher than the default 2 or 3 segments –  Nice study on CDN init_cwnd values: •  http://www.cdnplanet.com/blog/initcwnd-settings-major-cdn- providers/•  cwnd during the rest of the connection depends on slow start and congestion avoidance stages of the connection© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 191

TCP Windows•  Actual send window calculation is a bit more complicated –  Congestion avoidance –  The other side’s receive window•  The simplified formula: Min(cwnd, receive_window)! Sender (internal calculation) Receiver (internal calculation and advertised in each segment)© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 192

Small Receive Window SYN (Win=2920)! SYN/ACK (Win=xxx)! ACK (Win=2920)! GET / (Win=2920)!TI Client ServerM 200 STATUS OK (+Data)! (init_cwnd =6)E Data! Wait for ACK!© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 193

Rx Windows•  It’s still very much a good idea to have larger init_cwnd sizes•  We should be aware of how data is sent to mobile devices•  Android’s move to 14600 (10 x max MSS) in ICS is great!•  Great reading: –  http://www.cdnplanet.com/blog/tune-tcp-initcwnd- for-optimum-performance/© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 198

Connection To Cell towers•  Radios disconnect from the tower after idle time (to conserve power) and take 1-2 seconds to reconnect•  Excellent reading from Steve: •  http://www.stevesouders.com/blog/2011/09/21/making-a- mobile-connection/ •  Test it: http://stevesouders.com/ms/© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 200

The 2 Second Radio Thing•  Not much we can do about it•  Good lesson learned•  Need to keep this in mind as we do more testing•  Optimization opportunity –  You can have small keep-alive requests flow between the phone and the site, as a user navigates through your pages –  Use this carefully à battery and data usage© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 203

Final Thoughts(This is slide 204!!!)

Summary•  Performance matters!•  Measurement tools can be somewhat frustrating, but they’re heading in the right direction•  Mobile performance optimization is a huge area of opportunity –  Lots of room for acceleration of mobile sites –  New considerations for form factor and operational functionality•  For those of us used to testing desktop browsers, there are new gotchas and fun lessons to learn!© 2010 Strangeloop Networks Strangeloop. Faster Websites. Automatically. 205

http://econsultancy.com	3089
http://www.strangeloopnetworks.com	1533
http://lanyrd.com	46
http://marketing-digital.wsimarketingeninternet.com	34
https://twimg0-a.akamaihd.net	23
https://si0.twimg.com	21
http://eventifier.co	20
http://apps.synaptive.net	18
http://translate.googleusercontent.com	10
http://www.hanrss.com	6
http://core.traackr.com	4
http://www.encarolina.com	3
http://stage.strangeloopnetworks.com	3
http://bottlenose.com	2
http://strangeloopnetwork.net	2
http://www.newsblur.com	2
http://www.strangeloopnetwork.com	2
http://ebulletin.collected.info	2
http://76.77.72.158	2
http://www.diffbot.com&_=1356882912088 HTTP	1
http://www.diffbot.com&_=1356882942721 HTTP	1
http://131.253.14.250	1
http://electrosmart.com	1
http://cms.strangeloopnetworks.com	1
http://www.diffbot.com&_=1356882926544 HTTP	1

Velocity 2012: The 90-Minute Mobile Optimization Life Cycle

by Strangeloop on Jun 25, 2012

Accessibility

Categories

Upload Details

Usage Rights

25 Embeds 4,828

Statistics

Velocity 2012: The 90-Minute Mobile Optimization Life Cycle Presentation Transcript