Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Mobile Performance Testing - Testing the Server


Published on

  • Be the first to comment

Mobile Performance Testing - Testing the Server

  1. 1. Mobile Performance Testing - Part 2 – Testing the Server
  2. 2. Assumptions, Target Audience• This webinar will cover the role of the server in mobile performance, how to test for it, and what can be done.• Focus on mobile website performance• Performance testing of the mobile app/device was covered in a previous webinar.• Performance testing emphasizing the network will be covered in a future webinar – March 14 at 10 AM EST 2013• Target audience – managers, developers, testers
  3. 3. Agenda• Introduction: The Mobile Challenge• Differences between Mobile and Desktop usage• Know what is going on behind the scenes – 1st Step, a Simple Comparison Test – 2nd Step, a Simple Performance Test – 3rd Step, a Simple Load Test• Optimization Strategies• Conclusion
  4. 4. Introduction: The Mobile Challenge• Mobile Internet usage is projected to pass desktop Internet usage in 2014• Google found that a .5-1 second increase in page load time resulted in a 20% decrease in traffic and revenue.• Akamai found that the number of users who abandon a page after 3 seconds was 57%.• We expect the online experience to be as fast as our desktop experience, but it isn’t, and that is a problem.• Mobile is slower, but it doesn’t have to be.
  5. 5. 2013 State of Mobile Testing SurveyDifferences Between Desktop and Mobile QA processes• 30% of mobile developers believe that the differences between mobile and desktop are significant enough to have different processes for development and QA.• An additional 25% don’t have different processes for mobile, but think that different processes for mobile are necessary. - 2013 State of Mobile Testing, XBOSoft• Report of the survey findings can be found at from March 2013
  6. 6. What are theDifferences betweenMobile and Desktop?
  7. 7. Differences between Mobile and DesktopFat vs. Thin data pipe: Fat, high speed, Broadband data pipe The Cloud Thin, slow, 2.5G or 3G data pipe
  8. 8. Differences between Mobile and DesktopMany Tower connections:• Jumping from tower to tower can slow down your connection by an order of magnitude.
  9. 9. Differences between Mobile and DesktopSmaller, less powerful device: Your mobile device has a less powerful CPU, less RAM and a smaller screen resolution. The server needs to take this into account.Navigation: Your finger is used to navigate so touches have to be translated into clicks.
  10. 10. Differences between Mobile and DesktopDownloading Strategies:• Some websites preload all the next level pages. – This can greatly speed up the user experience for the desktop, but for the mobile device, it takes up valuable bandwidth and can be costly.• Some anticipate what you might click on next and preloads those pages.Charging for Data Usage:• In many countries, data usage can be expensive.
  11. 11. vs. apps vs. full websiteThree approaches to making you website accessible to mobile devices1. – the most common approach + designed for mobile makes it faster and easier to read – two versions of your website – features missing or accessed differently cause user discontent2. Mobile app – resides on mobile device + Highly optimized for that mobile device – User may not download app or keep it up to date3. Mobile Accessible of full website + One version of website, common user experience – can compromise main website, harder to program
  12. 12. Know what you are testingProxy Servers: What are they? GPRS Website Server InternetTwo Examples : Proxy• Nokia devices and Server• Opera mini browsers
  13. 13. Know what you are testingProxy Servers: How do they affect your testing?• Nokia devices and Opera mini browsers• Can reduce by up to 90% the amount of data transferred.• Speed and Cost savings can be considerable• most users will NOT access your servers through a proxy server• make sure you are testing in non-proxy server environments
  14. 14. 1st Step, a Simple Comparison TestSimple load performance test on XBOSoft’s main pageand several of its key pages. Not thorough, but a quickcheck. Of course an automated smoke test is preferred,but this is a quick fist step for those starting.Compare XBOSoft’s1. full version website,, from the desktop.2., from the mobile device.3., from the mobile device.
  15. 15. 1st Step, a Simple Comparison Test1. full version website, 2., on 3.,, on the the mobile on the mobile desktop device device
  16. 16. 1st Step, a Simple Comparison Test• Download speed was reduced by 40% on the first download from the full website to the m. website.• However for a repeat download, the reduction in time was only 7%.
  17. 17. Tools• Webpagetest – – Quick and easy to start – Offers connection analysis, page loading waterfall analysis, first view and repeat view analysis, a report card and much more• Akamai has a simple test for your mobile device - – Doesn’t differentiate between first run and repeat runs with caching. – Very simple, but good for getting started• – Quick and easy• Plus many, many more
  18. 18. 2nd Step, a Simple Performance Test• Test with WiFi, take the network out of the equation.• The Network part of the equation will be discuss in Mobile Performance Testing Part 3: the Network• Goal is to make phone as fast as desktop without having network involved
  19. 19. 2nd Step, a Simple Performance TestTest with• It is free.• Run by WPO Foundation whose goal is to “support Web Performance Movement”.• A quick way to identify areas that are causing performance problems.• Mainly for desktop testing, but it good for a quick test for iOS or Android 2.3
  20. 20. 2nd Step, a Simple Performance provides• A summary.• The load times, for both first and repeat downloads.• Connection analysis.• Detailed look at each component downloaded.• Plus much more.
  21. 21. 2nd Step, a Simple Performance Test
  22. 22. 2nd Step, a Simple Performance TestGo to and enter• Website url• Test location – choose from almost any where in the world• Browser/deviceFor this Simple Performance Test, we chose• Website url – and• Test location – Dulles VA• Browser/device - iPhone 4 iOS 5.1This will analyze the performance of your website, from this specified location and this specified device/browser.
  23. 23. 2nd Step, a Simple Performance Test• First Byte Time – time for receiving first byte for the page.• Keep Alive Enabled – connection socket is kept open so that many objects can use it.• Compress Transfer – compress object types “JavaScript” or “text”.• Compress Images – compress object types “image”.• Cache Static Content – controls expiration of objects in cache.• CDN Detected – Content Delivery Network, Is a distributed system of servers being used? – to be discussed in detail in next webinar
  24. 24. 2nd Step, a Simple Performance Testwebpagetest.orgGives the same information as our ‘Simple Comparison Test’, butwith an automated tools.
  25. 25. First View for xbosoft.comTen connection sockets were opened, manystayed open to retrieve many objects, whichincreases performance.
  26. 26. First View – Waterfall of Objects • The number of objects requested is a lot for a mobile device. • To speed up the first download, many of the objects need to be combined. • The repeat download was so much faster because most of these objects were cached.
  27. 27. Repeat View for Dramatic decrease in connections and objects which resulted in dramatic decrease in response time.
  28. 28. First View for • The number of objects was cut from 50 to 20 • The number of connections was cut from 10 to 3
  29. 29. Repeat View for • Caching cut the number of bojects in half.
  30. 30. 3rd Step, a Simple Load TestAt a minimum, Simple Load Test should be done• start with a server that has been load tested for the desktop.• simulate the 500 desktop users.• add one mobile user at a time and monitor the effect on the server. Simulate 500 users Add mobile user 1 at a time
  31. 31. Optimization Strategies• 80% of the time it takes for a web page to load is on the client side• The server has to change what it delivers to make the client’s job easier.Two main Strategies1. Reduce transmissions2. Reduce payload
  32. 32. 1) Reducing the number of HTTP RequestsWhy will this help?- Round trip with a broadband connection can be 1-30 milliseconds- Round trip for a 2.5G or 3G network is usually 300-400 milliseconds (and it can be a lot worse).- Round trip for a 4G network is typically 200+.What can be done?– Consolidating Resources– Embed resources in html for first-time use– HTML5 Web Storage– Uni-directional server update
  33. 33. 2) Reduce PayloadsWhy will this help?– Less data transferred, less time spent– If over device hw capacities, reducing payload can mean the difference between loading a page and a page failureWhat can be done?– Compress– Resize– Simplify
  34. 34. Future Solution?Those that favor ‘making your full website more mobile friendly’ is the future solution because of1) Moore’s Law for computer power and storage, and2) Nielsen’s Law for Internet bandwidth.
  35. 35. Conclusion• Test early, test often.• Best way to solve mobile performance problems is to prevent them. Don’t wait until after deployment to start worrying about performance issues.• You don’t need complicated, expensive tools to get started, a lot can be done simply.• No server performance testing will lead to disaster!
  36. 36. Q&AFollow us on twitter: