WebXPRT 4 has been available to testers since
the end of December, and we’re excited to see that the benchmark is already
gaining significant traction in the tech press and testing communities. Several
tech publications have already published reviews that feature WebXPRT results,
and the number of WebXPRT 4 runs is growing by about fifty percent each month, more
than twice the rate of growth for WebXPRT 3 after launch.
As WebXPRT 4 use continues to grow,
and more tech publications and OEM labs add WebXPRT 4 to their benchmark
suites, we encourage you to keep an eye on the WebXPRT 4 results viewer.
The viewer currently has about 120 test results, and we’ll continue to populate
the viewer with the latest PT-curated WebXPRT 4
results each week.
You don’t have to be a tech
journalist to publish a WebXPRT 4 result, however. We publish any results—including
individual user submissions—that meet our evaluation criteria. To submit a result
for publication consideration, simply follow the straightforward submission instructions
after the test completes. Scores must be consistent with general expectations and
must include enough detailed system information that we can determine whether
the score makes sense. If you’ve tested with WebXPRT 4 on a new device, or any
device or device configuration that’s not already present in the results
viewer, we encourage you to send in the result. We want to hear from you!
From time to time, we like to run a series of in-house WebXPRT comparison tests to see if recent updates have changed the performance rankings of popular web browsers. We published our most recent comparison last October, when we used WebXPRT 3 to compare Windows 10 and Windows 11 browser performance on the same system. Now that WebXPRT 4 is live, it’s time to update our comparison series with the newest member of the XPRT family.
For this round of tests, we used a Dell
XPS 13 7930, which features an Intel Core i3-10110U processor and 4 GB of RAM, running
Windows 11 Home updated to version 21H2 (22000.593). We installed all current
Windows updates and tested on a clean system image. After the update process
completed, we turned off updates to prevent them from interfering with test
runs. We ran WebXPRT 4 three times each across five browsers: Brave, Google
Chrome, Microsoft Edge, Mozilla Firefox, and Opera. The posted score for each
browser is the median of the three test runs.
In our previous round of tests with WebXPRT 3, Google Chrome narrowly beat out Firefox in Windows 10 and Windows 11 testing, but the scores among three of the Chromium-based browsers (Chrome, Edge, and Opera) were close enough that most users performing common daily tasks would be unlikely to notice a difference. Brave performance lagged by about 7 percent, a difference that may be noticeable to most users. This time, when testing updated versions of the browsers with WebXPRT 4 on Windows 11, the rankings changed. Edge was the clear winner, with a 2.2 percent performance advantage over Chrome. Firefox came in last, about 3 percent slower than Opera, which was in the middle of the pack. Performance from Brave improved to the point that it was no longer lagging the other Chromium-based browsers.
Do these results mean that Microsoft
Edge will always provide you with a speedier web experience? A device with a
higher WebXPRT score will probably feel faster during daily use than one with a
lower score. For comparisons on the same system, however, the answer depends in
part on the types of things you do on the web, how the extensions you’ve
installed affect performance, how frequently the browsers issue updates and
incorporate new web technologies, and how accurately each browser’s default
installation settings reflect how you would set up that browser for your daily
In addition, browser speed can
increase or decrease significantly after an update, only to swing back in the
other direction shortly thereafter. OS-specific optimizations can also affect
performance, such as with Edge on Windows 11 and Chrome on Chrome OS. All these
variables are important to keep in mind when considering how WebXPRT results
translate to your everyday experience.
Do you have insights you’d like to share from using WebXPRT to compare browser performance? Let us know!
We’re excited to announce that WebXPRT 4 is now available! Testers can access the benchmark at WebXPRT.com. If you’ve already been using the WebXPRT 4 Preview, your Preview test results will be comparable with results from the current official build.
Longtime WebXPRT users will notice that WebXPRT 4 has a new, but familiar, UI. The general process for kicking off both manual and automated tests is the same as with WebXPRT 3, so the transition from WebXPRT 3 to WebXPRT 4 testing should be straightforward. We will continue to make WebXPRT 3 available for legacy testing.
If you missed
earlier XPRT blog posts
about WebXPRT 4, here is a quick overview of the differences between WebXPRT 3
and WebXPRT 4:
We’ve updated the aesthetics of the WebXPRT UI to make WebXPRT 4 visually distinct from older versions. We did not significantly change the flow of the UI.
We’ve updated content in some of the workloads to reflect changes in everyday technology, such as upgrading most of the photos in the photo processing workloads to higher resolutions.
We’ve updated the base calibration system for score calculations, and adjusted the scoring scale. WebXPRT 4 scores should not be compared to scores from previous versions of WebXPRT.
Photo Enhancement. We increased the efficiency of the workload’s Canvas object creation function, and replaced the existing photos with new, higher-resolution photos.
Organize Album Using AI. We replaced ConvNetJS with WebAssembly (WASM) based OpenCV.js for both the face detection and image classification tasks. We changed the images for the image classification tasks to images from the ImageNet dataset.
Stock Option Pricing. We updated the dygraph.js library.
Sales Graphs. We made no changes to this workload.
Encrypt Notes and OCR Scan. We replaced ASM.js with WASM for the Notes task and updated the WASM-based Tesseract version for the OCR task.
Online Homework. In addition to the existing scenario which uses four Web Workers, we have added a scenario with two Web Workers. The workload now covers a wider range of Web Worker performance, and we calculate the score by using the combined run time of both scenarios. We also updated the typo.js library.
thankful for all of the feedback we received during the WebXPRT 4 development
process, and we look forward to seeing your WebXPRT 4 results!
the last pieces in place for the WebXPRT 4 GA, and expect to take the final
build live by this time next week! When we released the WebXPRT 4 Preview and encouraged testers to submit
and publish results, we said we’d try to limit any changes to things that would
not affect test scores. We’re happy to report that we’ve achieved that goal,
and Preview testing results are comparable with GA build results.
If you missed the blog post about the differences between WebXPRT 3 and WebXPRT 4, we
encourage you to check it out. Everything we mentioned about the general and
workload-specific changes in the Preview build holds true for the upcoming GA.
Keep an eye on the blog and WebXPRT.com for more information in the coming week. We look forward to seeing your test results!
some recent internal WebXPRT 4 Preview
testing, we discovered that the WebXPRT 4 Preview does not run in Internet
Explorer (IE) 11. In fact, before the first workload begins in IE, the WebXPRT
4 built-in WebAssembly (WASM) check fails and produces an error message.
reason we haven’t tested WebXPRT 4 on IE 11 before now is that Internet
Explorer is currently in its end-of-life phase. Microsoft has been removing
support for IE 11 in Microsoft 365 and other apps for some time, they did not
include the desktop version of IE 11 in Windows 11, and they are removing support for IE 11
in Windows 10 on June 15, 2022. Among Windows users, the most popular browsers
are now Microsoft Edge, Google Chrome, and Mozilla Firefox.
proud that WebXPRT has historically had broad, cross-platform compatibility in
almost any browser. However, the modern web is rapidly incorporating powerful
tools such as WASM that do not work in older legacy browsers. To maintain the
benchmark’s relevance in future years, we need to deprioritize some level of
legacy compatibility, and this begins with WebXPRT 4 release.
the WebXPRT testers who wish to continue testing with IE 11, WebXPRT 3 will remain
on our site for the foreseeable future. Barring any further changes from
Microsoft, the benchmark should continue to run in existing instances of the Internet
Explorer desktop app.
The official WebXPRT 4 launch is approaching, and we hope to announce the release date within the next few weeks! Until that time, we will continue to share the latest updates here in the blog. If you have any questions or comments about WebXPRT 4 or compatibility with legacy browsers, please feel free to contact us!
to announce that the WebXPRT 4 Preview is now available! Testers can access the
Preview at www.WebXPRT4.com or through a link on WebXPRT.com. The Preview is available to everyone, and testers can now
publish scores from Preview build testing. We may still tweak a few things, but
will limit any changes that we make between the Preview and the final release
to the UI and features we do not expect to affect test scores.
WebXPRT users will notice that the WebXPRT 4 Preview has a new, but familiar,
UI. The general process for kicking off both manual and automated tests is the
same as with WebXPRT 3, so the transition from WebXPRT 3 to WebXPRT 4 testing
should be straightforward. We encourage everyone to visit the XPRT blog for more details about what’s new in this Preview release.
In addition, keep
your eye on the blog for more details about the all-new WebXPRT
4 results viewer, which we expect to publish in the very near future. We think
WebXPRT testers will enjoy using the viewer to explore our WebXPRT 4 test data!