One of the biggest surprises the Blaze team found was that
Apple iOS 4.3 release and Google Android 2.3 releases, these
improvement made no measurable improvement on the actual page load
times of the sites tested.”
There is a good reason for this. According to Blaze’s own
documentation the “measurement itself was done using the custom
apps which use the platform’s embedded browser. This means
WebView (based on Chrome) for Android, and UIWebView (based on
Safari) for iPhone.”
That’s not to say it isn’t interesting that Android’s WebView for apps is faster than iOS’s UIWebView for apps, but it just isn’t true that these results are indicative of anything regarding Mobile Safari’s performance. It’s easy to see that Mobile Safari is faster than UIWebView — just run something like the SunSpider benchmark twice, once in Mobile Safari and once in any app from the App Store with a web content view. On my iPhone 4, Mobile Safari runs SunSpider almost three times as fast as an app using UIWebView.
These Blaze guys are either incompetent or dishonest attention seekers, given that they claim this, in an update to their report:
our measurements. We’re still investigating this issue, as the
report was completed before it was made known. So far we’ve seen
indications in both directions, so we can’t say for sure it’s
only accounts for a small percentage of the total load time, about
15% on average. This implies that even if Nitro is not in use, it
likely can only slightly narrow the gap. We’ll follow up with
any additional info.
Because the thing is, Nitro isn’t the only difference between Mobile Safari’s rendering and UIWebView’s rendering. Mobile Safari has better caching and asynchronous multithreading, too.
★ Thursday, 17 March 2011