Google Chrome Sets New Benchmark Records on M5 MacBook Pro

Google has reported that its Chrome browser has achieved record-breaking performance scores on industry-standard benchmarking tools when running on the latest M5 MacBook Pro [2]. The browser recorded a score of 61 on the Speedometer 3.1 test and 469 on the JetStream 3 benchmark, representing performance gains of 5% and 10% respectively [1, 3].

Key takeaways

• Chrome achieved a record score of 61 on the Speedometer 3.1 benchmark and 469 on the JetStream 3 suite [2, 4].
• The testing was conducted on an M5 MacBook Pro running macOS 26.0.1 [1, 2].
• Google attributes these gains to optimizations in JavaScript handling, WebAssembly workloads, and the Blink rendering engine [3, 4].
• While Google claims these results represent a record across all browsers, independent attempts to replicate these specific figures have been unsuccessful due to differing test conditions [1, 3].

Technical Optimizations Behind the Performance

Google’s performance gains are the result of targeted engineering efforts across several core browser components. In the realm of JavaScript, the team implemented "fast paths" that allow the engine to bypass unnecessary execution steps [1]. Developers also optimized the handling of asynchronous operations, such as microtask dispatch and await resolution, and improved the processing of BigInt data [1, 4].

Beyond JavaScript, Google focused on the Blink rendering engine and WebAssembly. The company introduced smarter caching for style resolution and reduced redundant DOM lookups to streamline page rendering [4]. For WebAssembly, engineers optimized internal data structures within the V8 engine and reduced the overhead of function calls between JavaScript and WebAssembly [4]. Additional refinements were made to typography and vector graphics, including the implementation of Apple Advanced Typography shaping and new caches for SVG processing [4].

Why it matters

Google states that these benchmarking improvements translate into a "meaningfully faster" experience for users, particularly as web content grows increasingly complex [1, 3]. However, the report did not define the specific test bed used, and at least one independent tester was unable to replicate Google’s results [1].

The timing of the announcement, released just days before Apple’s Worldwide Developers Conference (WWDC), has led to speculation regarding the competitive landscape between Chrome and Safari. While some observers suggest the move is an attempt to challenge Apple’s browser dominance ahead of potential software announcements, others note that the technical nature of the blog post is primarily aimed at web developers rather than the general consumer market [4].