Chrome scored 61 on the Speedometer 3.1 benchmark on an M5 MacBook Pro, a 5% jump from the year‑ago result. That headline number alone caught my eye, but the story behind it shows how Google’s browser team is inching performance forward on Apple silicon.
Key Takeaways
- Speedometer 3.1 reached a record 61 on the M5 MacBook Pro, up 5% YoY.
- JetStream 3 posted 469 points on the same hardware, a 10% improvement.
- Both benchmarks run on macOS 26.0.1, highlighting software‑hardware synergy.
- Google claims the gains translate into a faster user experience.
- These results follow a previous set of scores on an M4 MacBook Pro using Chrome 128‑139 dev.
Historical Context
Google’s Chromium team has been publishing benchmark data for several years, using the same suite of tests to gauge progress across hardware generations. The most recent predecessor to today’s numbers was a June release that ran on an M4 MacBook Pro with macOS 15. That run captured Chrome dev builds from version 128 through 139, and it set the baseline that the current M5 results are measured against.
That baseline mattered because it established a clear “before” picture: Speedometer 3.1 sat in the high‑50s and JetStream 3 hovered around the mid‑400s. When the M5 hardware arrived, Chrome developers targeted the same test harness, keeping every other variable constant. By doing so, they could isolate the effect of the new silicon and the software tweaks that landed in the browser between the two testing windows.
Over the past year, the Chromium blog has highlighted a series of incremental improvements to Blink, V8, and the WebAssembly runtime. Those updates were bundled into regular dev‑channel releases, and they accumulated into the performance jump we see today. The pattern of yearly releases, followed by a fresh round of benchmark runs on the newest Apple silicon, has become a predictable rhythm for the community.
Chrome benchmark Mac sets new record on M5 MacBook Pro
When you look at the raw numbers, the 61 Speedometer score feels modest, but the 5% lift matters because it proves Chrome’s engine is still optimizing for Apple’s latest silicon. The test ran on a brand‑new M5 MacBook Pro with macOS 26.0.1, which Google says is the same configuration it used for the JetStream 3 run.
We’ve seen browsers chase raw numbers for years, yet the jump from the previous year’s benchmark isn’t just a vanity metric. It reflects a series of under‑the‑hood tweaks to Blink, V8, and the WebAssembly runtime that Google detailed in its Chromium blog post. Those tweaks aren’t visible to end users, but they shrink latency on interactive sites, which is what Speedometer measures.
What the Speedometer 3.1 Score Means
Speedometer 3.1 is built in collaboration with other browser vendors and stresses the Blink rendering engine across a range of workloads – HTML parsing, JavaScript and JSON processing, and pixel rendering. By hitting 61, Chrome’s latest dev build beats the previous record set on an M4 MacBook Pro that ran macOS 15. That earlier run, published last June, covered Chrome 128 through 139 dev releases.
Because the benchmark mimics real‑world web apps, a higher score suggests web pages will feel snappier on the M5 hardware. Google’s own wording frames the result as a “meaningfully faster experience for our users.”
“These results directly translate into a meaningfully faster experience for our users.” – Google
JetStream 3 Gains Explained
JetStream 3 is a different beast. It focuses on JavaScript and WebAssembly performance, and it’s a collaborative effort involving engineers from Apple, Google, Mozilla, and others. Chrome’s 469‑point score on the M5 MacBook Pro translates to a 10% gain over a test performed earlier this year.
That improvement isn’t just a number; it shows the V8 engine’s optimizations are paying off in the WebAssembly space, which many modern web apps rely on for heavy computation. The 10% lift is measured against the same hardware, so it isolates software improvements from hardware changes.
Why Apple Silicon Matters
Apple’s silicon line, now at the M5 generation, packs more cores and higher memory bandwidth than the M4. Chrome’s ability to tap that extra horsepower without sacrificing battery life is crucial for developers targeting macOS users. The benchmarks ran on macOS 26.0.1, which means the OS itself also supports the latest performance features.
Developers should note that the gains are coming from both the browser and the OS, not just raw CPU speed. That synergy is what makes the 5% and 10% jumps feel tangible.
How Google Measures Browser Speed
Google’s Chromium team publishes detailed breakdowns of each benchmark run. For Speedometer, they look at HTML parsing times, JavaScript execution latency, JSON handling, and pixel rendering frames. For JetStream, they parse JavaScript and WebAssembly workloads that mimic complex web applications.
- Speedometer 3.1 – 61 points (5% YoY increase)
- JetStream 3 – 469 points (10% increase from early‑year test)
- Hardware – M5 MacBook Pro, macOS 26.0.1
- Previous baseline – M4 MacBook Pro, macOS 15 (June benchmark)
Those numbers give developers a concrete target: if your app runs under Chrome on an M5 Mac, you can expect it to feel faster than it did on the previous generation, assuming you’re using modern web standards.
Implications for Developers
If you’re building a web app that leans heavily on JavaScript or WebAssembly, the JetStream 3 score is a good indicator that Chrome’s runtime is now more efficient on Apple silicon. That could let you push heavier workloads without hurting responsiveness.
On the other hand, Speedometer’s focus on UI responsiveness means UI‑heavy apps – think dashboards or collaborative editors – will likely see smoother interactions. The real win is that these gains come without a major overhaul of the codebase; they’re baked into the browser.
What This Means For You
For developers, the takeaway is simple: keep an eye on Chrome’s release notes and benchmark updates, because they can directly affect perceived performance. If you’re testing on older Mac hardware, you might not see the same gains, so it’s worth adding an M5 MacBook Pro to your QA pool.
Builders should also consider that Chrome’s performance improvements could shift the balance when choosing a primary browser for testing. If your app’s performance metrics are borderline, the newer Chrome could tip the scales in your favor, especially for users on the latest macOS.
As Apple continues to iterate on its silicon, we’ll likely see browsers scrambling to extract every ounce of speed. That competition benefits developers and end users alike, but it also means staying current with benchmark data is more important than ever.
Real‑World Scenarios
Imagine a SaaS analytics dashboard that refreshes charts every few seconds. Speedometer’s UI‑focused workload mirrors that pattern, so the 5% boost can translate into noticeably quicker chart redraws. Users who previously felt a half‑second lag might now experience a smooth transition, simply because the browser processes DOM updates faster.
Consider a browser‑based game that relies on WebAssembly for physics calculations. JetStream’s emphasis on that runtime means the 10% lift could reduce frame‑time spikes during intense moments. The result is smoother gameplay without the developer having to rewrite the game’s core logic.
A news site that pulls JSON feeds and renders articles with rich media also benefits. Faster JSON parsing and HTML rendering mean articles appear sooner after a click, keeping readers engaged. Those improvements happen under the hood, so content teams won’t need to adjust their publishing workflow.
Technical Architecture Deep Dive
The Blink rendering engine handles everything from layout to paint. Recent under‑the‑hood tweaks, as described in the Chromium blog, focused on reducing the number of paint passes required for complex UI components. Fewer passes mean less work for the GPU, which directly impacts the Speedometer score.
V8, Chrome’s JavaScript engine, gained new optimizations for the Apple‑silicon instruction set. Those changes improve the way the engine generates machine code for hot functions, shaving milliseconds off execution time. JetStream’s JavaScript‑heavy tests capture that improvement, which is why the benchmark reflects a 10% jump.
The WebAssembly runtime also received targeted enhancements. By aligning its memory‑access patterns with the M5’s higher bandwidth, the runtime can feed data to compiled modules more efficiently. That alignment is precisely what JetStream measures when it runs its suite of compute‑intensive tasks.
macOS 26.0.1 contributes its own set of performance hooks. The operating system’s scheduler now better distinguishes between foreground rendering threads and background compute threads. When Chrome’s Blink and V8 engines request CPU time, the OS can prioritize those requests without starving other processes, preserving battery life while still delivering speed.
Key Questions Remaining
- Will the performance gains persist across future macOS updates, or will new OS features reset the baseline?
- How do these Chrome improvements compare with similar updates from competing browsers that also target Apple silicon?
- Can developers reliably predict the impact of a 5% Speedometer lift on user‑perceived latency, or does the effect vary wildly by application type?
- What additional optimizations might the Chromium team roll out before the next hardware generation, and how will those shape the benchmark landscape?
Sources: 9to5Mac, Chromium blog
