Monitoring the 340 Trillion Trillion Trillion: Keynote and IPv6

The Keynote Systems’ Startup Shootout Index provides some insight into the three-screen challenge now facing anyone with a web presence. It shows a website's weekly average load time and download success rate (availability) on desktops, smartphones, and tablets. Let's take a look at mobile gaming, but the lessons here apply to any web sites optimizing – or not optimizing – for three screens.

The growth of mobile games is inevitable with the growth of mobile devices that enable them including feature phones, smartphones, tablets and even e-Readers. Adverse to many websites, mobile is a main focus for mobile gaming companies like Rovio.

While their desktop load speed leaves something to be desired, Rovio is the fastest social gaming site on the iPad and second fastest on the iPhone (with a speed of seven seconds). Rovio improved their site by redirecting iPad and iPhone users to a lighter, mobile optimized site. 

Papaya Mobile is another mobile gaming site, loading at a blazing 2.58 seconds on the iPhone, leveraging best practices and simply requiring a login screen as the first step to access the site. The login screen loads very quickly because of its simplicity, a great way to get your gamers on the site efficiently with minimal wait.

While most mobile gaming sites focus on their mobile speed and reliability to retain their loyal customers. Crowdsart has managed to integrate the best of mobile and desktop performance and reliability.

Crowdstar has arguably the best overall performance in the July Startup Shootout for mobile games, with a better than average desktop load speeds and 6.97 seconds to load on the smartphone. What is remarkable about the smartphone loading time is that Crowdstar brings the entire site to iPhone users, rather than offering bits of content to speed mobile interaction. If they optimized their site even further for mobile, they have the ability to achieve even faster speeds. The response time for iPad users is better than average and may end up being tolerable when connected over Wi-Fi instead of the 3G network.

Although Rovio and Papaya charge forward for quick mobile speeds to target their main demographics, leveraging best practices and monitoring slight changes in website development can give many developers the ability to optimize a better overall experience over all three screens.


Related Articles:


A Three-Screen Perspective From The World’s Largest Retailer

Magazines on smartphones: convenient but not quick

Effectively Monitor The Impact Of Third-Party Performance

How third-party content can impact Web site performance and why effective targeted monitoring of third-party content and add-ons is vital to IT, Web operations managers, and business stakeholders to ensure optimal Web site performance and a good user experience.

A slick-looking Web site is ultimately of limited effectiveness if all of the its bells and whistles are an impediment to system performance. Hence, the monitoring of system performance at the end-user/UI level is extremely important to ensuring a consistently excellent user experience.

By using the proper web performance tools in a targeted manner, both business managers and developers can effectively monitor the impact of third-party performance both on the individual component level and in the aggregate.

Read More on The Benefits of Third-Party Content Monitoring and Website Monitoring Service

Improving Website Responsiveness Involves Tradeoffs

It is easy for a measurement tool to sit on a server and measure all requests for service—and this kind of measurement has its uses, especially when load testing or investigating bottlenecks. But because of the variety of implementation possibilities, a common problem when measuring RIAs is that related requests may appear to originate from separate units of work on the client.

Correlating seemingly separate measurements with a particular application activity, task, or phase is tricky. The more complex the client/server relationship, especially when it involves concurrent interactions, the harder it becomes for measurement and analysis tools to perform that correlation properly.

Having more design and implementation options also creates new opportunities for developers to make performance-related mistakes. Accidentally or deliberately, developers can implement “chatty” client/server communication styles that perform extremely slowly under some workload conditions. Even with thorough testing, some of these problems may remain undiscovered until after the application is deployed unless applications are subjected to a systematic SLM process that includes measurement
activities to identify, investigate, and fix them.

Read More