Chrome on macOS hits new benchmark records

Chrome sets – Google says Chrome has reached new performance highs in JetStream 3 and Speedometer 3.1 after a year of targeted engine work. The latest numbers—measured on an M5 MacBook Pro with macOS 26.0.1—arrive just days before Apple’s WWDC keynote.

Chrome on macOS just scored new highs in industry benchmarks, and the details read like a checklist of what web developers have been chasing for years: faster JavaScript, tighter rendering, and less wasted work across the browser stack.

In a Chromium blog post dated June 4, Google said its Chrome optimizations have pushed the browser to new records in benchmark runs that it describes as spanning all browsers. The latest measurements were taken on an M5 MacBook Pro running macOS 26.0.1.

In the JetStream 3 benchmark, Chrome posted a score of 469—described as a new record and a 10% improvement from the start of 2026. In Speedometer 3.1, it reached 61, another benchmark record with a 5% year-over-year jump.

Those numbers are tied to three clear areas of engineering work. On the JavaScript side. Google says it adjusted an optimizing compiler to inline “fast paths. ” the common routes that are hit regularly enough to benefit from skipping time-consuming steps. The company also points to inlining async operations such as microtask dispatch and await resolution. Separately, it says it improved heuristics for deciding which JavaScript code to optimize, and added missing optimizations for BigInt handling.

For WebAssembly, the work focused on how V8 manages internal data structures. Google says code generation optimizations improved performance for AI, cryptography, and interpreter use cases. It also says the compiler was made more efficient by reusing temporary memory. and that overhead was reduced for function calls from JavaScript to WebAssembly.

Rendering work landed in Blink, Google’s rendering engine for the web. The changes target style resolution and DOM operations through smarter caching and fewer redundant DOM lookups. Google also describes a fast bailout path to reduce checks for element attribute tracking, minimizing style recalculation delays. It says CCSS selector caching was simplified as well.

Beyond those engine layers, the post discusses foundational improvements for page-loading and text processing. Google says string copying was made more efficient. and that it identified critical performance bottlenecks in typography and vector graphics rendering. The team also completed Apple Advanced Typography shaping optimizations and fixed font fallback issues. At the same time. it eliminated heap allocations for glyph width calculations and added a cache to speed up SVG processing for graphics.

The timing of the June 4 post is hard to miss. Apple’s WWDC is set to begin on June 8. with the keynote address happening on the first day and expected to focus on software changes arriving in Apple’s operating systems—almost certainly including improvements to Safari at some point. For some observers. that creates an awkward sense of rivalry: a developer-focused Chrome performance article landing right before Apple takes the stage.

But for the people who actually feel the results—web developers running real apps and testing performance-sensitive sites—the work described in the benchmarks is the part that matters most. The company didn’t ask for patience with vague promises. It published numbers from a specific machine—an M5 MacBook Pro on macOS 26.0.1—and tied them to concrete engine changes across JavaScript. WebAssembly. and rendering.

Chrome macOS benchmark JetStream 3 Speedometer 3.1 M5 MacBook Pro macOS 26.0.1 Blink V8 WebAssembly performance