Chrome Sets Record Speedometer Score on M5 MacBook Pro

🚨 BREAKING

Chrome hitting record Speedometer 3.0 scores on M5 MacBook Pro hardware is a software optimization story dressed up as a benchmark story. The more interesting detail is what Google actually changed, not how high the number went.

Google tuned Chrome’s memory handling and background task scheduling specifically for the M5 chip, which suggests the gains are architectural rather than incidental. Speedometer 3.0 measures how quickly a browser can run simulated web app workloads, so a record score there has more practical relevance than older benchmarks that mostly tested raw JavaScript parsing. The gap between Chrome’s previous scores and these new ones is described as wide, though Google has not published the specific figures alongside a detailed technical breakdown.

What This Tells Us About the M5 Transition

Apple Silicon has consistently rewarded developers who write code that respects the chip’s unified memory architecture and efficiency cores. Safari has held a persistent benchmark advantage on Apple hardware partly because Apple tunes both the browser and the chip simultaneously. Chrome closing that gap, or surpassing Safari on certain tests, would be the more pointed result here, though the source material stops short of making that direct comparison.

The practical ceiling for these gains depends on how representative Speedometer 3.0 is of real workloads. It handles things like:

• DOM manipulation in framework-heavy apps
• Rendering updates across multiple UI components
• Garbage collection under sustained load

For users running Figma, Notion, or Google Docs in a browser tab all day, those categories map reasonably well to actual friction points.

Google has been steadily narrowing Safari’s efficiency advantages on Mac since Apple Silicon launched in late 2020. Each chip generation gives browser teams a new target to optimize against, and the M5 appears to have given Chrome engineers enough headroom to post numbers the platform hasn’t seen before. Whether battery life holds up under that performance profile is the question the benchmarks don’t answer.