As we promised in the blog post The newest member of the family, we made the WebXPRT 2013 community preview available this week. It has already been used in a review! The AnandTech review of the Acer Iconia W510 includes results from the WebXPRT 2013 community preview for that device and for the Microsoft Surface RT and the Apple iPad 4. The review has results from the TouchXPRT 2013 community preview for the Acer Iconia W510, Microsoft Surface RT, and the ASUS VivoTab RT as well.
Obviously, we’ve been doing some testing ourselves. Here’s a sampling of the devices on which we’ve successfully run WebXPRT:
Device | Processor | Operating system | Browser | Score | Confidence interval |
HP Envy 2 | 1.8 GHz Intel Atom Z2760 | Windows 8 | Internet Explorer 10.0.92 | 201 | +/- 6 |
Asus VivoTab RT | 1.2 GHz Tegra 3 T30L | Windows RT | Internet Explorer 10.0.92 | 160 | +/- 5 |
Kindle Fire | 1.2 GHz ARM Cortex-A9 | Android OS 2.3 (customized: 6.3.1_user_4107720) | Safari 5 | 92 | +/- 2 |
ASUS-made Google Nexus 7 | 1.2 GHz Tegra 3 T30L | Android 4.2 | Chrome 18 | 201 | +/- 4 |
Motorola DroidX phone | 1 GHz TI OMAP3630-1000 | Android 4.5.621 | Browser version 2.3.4 | 26 | +/- 1 |
iPhone 5 | 1.3 GHz Apple A6 | iOS 6.0.2 | Safari 6 | 168 | +/- 2 |
iPad mini | 1GHz Apple A5 | iOS 6.0.2 | Safari 6 | 110 | +/- 1 |
iPad 4 | 1.4 GHz Apple A6X | iOS 6.0.1 | Safari 6 | 180 | +/- 2 |
As the results above show, WebXPRT can run on a wide range of devices. We are working to get results on lots of different devices and would like your help. We’ll set up a forum thread for results that starts with these. We’ll then add additional ones we produce. Please respond in the thread with results you get.
In addition to performance results, the WebXPRT 2013 community preview also provides a report on the HTML 5 capabilities of your device. For those who want to know more about the capabilities of HTML 5, there’s more good news. The W3C community released the feature-complete spec for HTML 5 and Canvas 2D this week.
You can find an explanation of scenarios in the WebXPRT 2013 community preview, and an explanation of how it calculates its results in the WebXPRT 2013 CP1 Overview. Let us know what you think. There’s still time to help us shape the final version of both WebXPRT 2013 and TouchXPRT 2013.
Eric