Google says the latest version of Chrome for Mac has posted new benchmark highs on Apple’s newest hardware, with fresh results on an M5 MacBook Pro showing record scores in both Speedometer 3.1 and JetStream 3. The figures come from a new Chromium blog post that compares Chrome’s performance gains over recent releases and frames the improvements as user-facing speed upgrades for web browsing and web apps.
Chrome posts a new Speedometer 3.1 record on M5 MacBook Pro
In its latest update, Google highlighted a Speedometer 3.1 score of 61 on an M5 MacBook Pro running macOS 26.0.1. The company said that result represents a 5% increase from the year-ago benchmark results. Google previously published a similar performance post last June, when it showed Chrome’s Speedometer 3.1 scores improving across browser releases from Chrome 128 to Chrome 139 dev on an M4 MacBook Pro running macOS 15.
Speedometer 3.1 is designed to measure web application responsiveness. Google describes it as a benchmark “created in open collaboration with other browsers” and says it tests workloads that cover a wide range of areas inside Chrome’s Blink rendering engine. Those areas include HTML parsing, JavaScript and JSON processing, and pixel rendering, among others. In other words, it is intended to reflect how quickly a browser can respond to realistic web activity rather than only synthetic or isolated tasks.
The new benchmark result is notable because Google is not simply comparing Chrome with an older browser build on the same system. It is also comparing performance on Apple’s latest MacBook Pro hardware platform, the M5 model, which gives the company a fresh baseline for measuring gains in Chrome’s engine and rendering work.
JetStream 3 adds another performance milestone
Google also shared a new JetStream 3 result. On the same M5 MacBook Pro running macOS 26.0.1, Chrome scored 469 points in JetStream 3. Google said that figure amounts to a 10% improvement from another test performed “just the start of this year.”
JetStream 3 is a JavaScript and WebAssembly benchmark suite focused on advanced web applications, according to BrowserBench. The benchmark was announced in March and, like Speedometer 3.1, it was developed as a collaborative project involving engineers working on major JavaScript and WebAssembly engines. BrowserBench says contributors include Apple, Google, Mozilla, and other companies.
By sharing both Speedometer and JetStream results, Google is pointing to progress across multiple parts of the browser stack. Speedometer emphasizes responsiveness in typical web app workloads, while JetStream is centered on more advanced JavaScript and WebAssembly execution. Together, the two scores suggest gains not just in page rendering but also in code execution and application-heavy browsing tasks.
What Google says changed
Google’s Chromium post goes beyond the headline benchmark numbers and breaks down the improvements behind the scenes. The company says the latest gains come from work across JavaScript, WebAssembly, and its rendering engine. While the post does not reduce those changes to a single tweak or feature, Google says the results “directly translate into a meaningfully faster experience for our users.”
That is the core message in the benchmark update: the company is using measured improvements to argue that browser engineering work has a practical effect on how Chrome feels day to day. Faster JavaScript execution can help with interactive sites and web apps, WebAssembly improvements can benefit more demanding workloads, and rendering engine refinements can improve the speed of page display and responsiveness.
Google’s earlier benchmark post from last year followed a similar pattern. At the time, the company compared Chrome 128 through Chrome 139 dev on an M4 MacBook Pro running macOS 15 and showed a steady progression in Speedometer 3.1. The new post suggests that the trend has continued on newer Apple hardware and with additional engine work since then.
Why these benchmark results matter
Benchmark scores are not the same as real-world usage, but they are one of the clearest ways to track browser performance over time. For a product like Chrome, which runs on a wide variety of hardware and handles everything from simple pages to complex web apps, benchmarks help illustrate whether changes in the browser engine are producing measurable gains.
In this case, Google is emphasizing both the numbers and the context. The Speedometer 3.1 score of 61 and the JetStream 3 score of 469 were both achieved on an M5 MacBook Pro with macOS 26.0.1, giving the company fresh proof points for recent optimization work. Google also ties the results to a specific promise: that the performance improvements should be felt by users in actual browsing.
It is also worth noting that both benchmarks were designed in collaboration with multiple browser vendors and engine teams. That makes them more useful as industry-wide reference points than as scores owned by any one company. Google’s latest results therefore sit within a broader effort to measure browser progress in a way that is more comparable across platforms and products.
Benchmarks Google highlighted
- Speedometer 3.1: Chrome reached a score of 61 on an M5 MacBook Pro running macOS 26.0.1.
- Year-over-year change: Google said the Speedometer result reflects a 5% increase from benchmark results published a year earlier.
- JetStream 3: Chrome scored 469 points on the same M5 MacBook Pro and macOS version.
- Recent improvement: Google described the JetStream result as a 10% gain from a test conducted “just the start of this year.”
The broader Chrome performance push
Google has been publicly tracking Chrome performance more aggressively over the past year, using Chromium blog posts to show progress in standard browser benchmarks. Last year’s M4 MacBook Pro comparison set the stage for this week’s update by showing how Chrome’s Speedometer 3.1 score improved across multiple releases. Now the company is extending that story onto Apple’s newest MacBook Pro generation.
The latest post is also a reminder that browser performance work is continuous. Changes to JavaScript, WebAssembly, and rendering code may not always be visible to users in obvious ways, but they can add up to a smoother experience over time. By publishing benchmark records, Google is making its case that those incremental engineering changes have produced measurable improvements on a current Mac platform.
For Mac users, the takeaway is straightforward: Chrome is now posting its strongest benchmark numbers yet on the latest MacBook Pro hardware, at least in the tests Google chose to highlight. For Google, the message is equally clear: browser speed remains a competitive priority, and the company wants benchmark charts to show that work translating into better performance.
Source: Original report
Was this helpful?
Last Modified: July 7, 2026 at 9:32 pm
7 views
