Google says Chrome 91 has 23% faster performance thanks to Sparkplug, a new non-optimizing compiler for its V8 JavaScript engine
a non-optimizing JavaScript compiler Maria Deutscher / SiliconANGLE : Google details code optimization tech behind Chrome's latest 23% speed boost Michael Perrigo / Chrome Unboxed : Chrome 91 has up to 23% faster performance as a result of its new JavaScript compiler Christopher Baugh / iPhone in Canada Blog : Google Says Chrome Is Now 23% Faster Sergiu Gatlan / BleepingComputer : Google Chrome now 23% faster after JavaScript engine improvements Thomas Nattestad / Chromium Blog : Chrome is up to 23% faster in M91 and saves over 17 years of CPU time daily Imran Hussain / iThinkDifferent : Google Chrome 91 is 23% faster due to new Sparkplug compiler and short builtin calls Prakhar Khanna / Pocketnow : Google makes its Chrome browser 23% faster Michael Larabel / Phoronix : Chrome 91 Benchmarks On Linux Showing Off Even Better Performance Pranob Mehrotra / XDA Developers : Chrome 91 offers up to 23% faster performance thanks to these changes Bogdan Popa / Softpedia News : Google Says Google Chrome Is Now 23% Faster JC Torres / SlashGear : Chrome 91 is boasted to be 23% faster thanks to JavaScript improvements Kareem Anderson / OnMSFT.com : Chrome 91 brings a 23 percent speed improvement through new JavaScript compiler Paul Hill / Neowin : Chrome 91 includes 23% speed boost with new Sparkplug compiler Tweets: Lance Ulanoff / @lanceulanoff : Faster is good. Eating fewer system resources would be even better https://www.zdnet.com/... Jochen Eisinger / @jochen_e : Exciting news from our V8 team! Especially on M1 CPUs, you'll see large perf gains in Chrome 91 https://twitter.com/... Katelyn Gadd / @antumbral : everything old is new again: a non-optimizing js compiler was v8's original solution for fast startup, and now they're doing it again but also with an interpreter https://twitter.com/... @v8js : ⚡ The more the merrier: we've added Sparkplug - a new non-optimizing JS compiler - in V8 v9.1 to improve performance on real-world pages by 5-15%. Let @leszekswirski take you on a tour: https://v8.dev/... Ted Mielczarek / @tedmielczarek : “We improved performance by not optimizing as much” is a real thing. https://twitter.com/... Robert O'Callahan / @rocallahan : I would really appreciate a deep dive comparing the architectures of V8, JSCore and Spidermonkey at this point. They look very similar to me (parser to AST, bytecode generator, bytecode interpreter, non-optimizing baseline compiler, IR-based optimizing compiler). https://twitter.com/... Damian Gryski / @dgryski : “non-optimizing compiler” https://twitter.com/... Eric Lawrence / @ericlaw : The V8 team decided that they will not leave the Cloudflare team the unchallenged champions of awesome blogging. https://twitter.com/... https://twitter.com/... Leszek Swirski / @leszekswirski : I'm very proud to be announcing Sparkplug, our new mid-tier, non-optimising compiler; there's a lot of beauty in its simplicity, and how that simplicity directly translates to performance. Also: stack frames 😀 https://twitter.com/... Matthew Prince / @eastdakota : Side effect of this: @Cloudflare Workers just got even faster. https://v8.dev/...
Context & Ripple Effects
Chrome 91 extends a recurring Google effort to improve browser efficiency: Chrome 45’s load-time and memory improvements were followed by Chrome 85’s faster page loads. Sparkplug puts that work inside V8’s compilation path, making performance an engine-level product change rather than a standalone browser feature.
The reporting also sits in a browser-performance arc that rejects score-chasing: Google had retired Octane after developers optimized for benchmark results over real-world performance. That makes a claimed speed gain meaningful chiefly insofar as it improves ordinary JavaScript execution.
First-order effects
- Chrome 91 users receive faster JavaScript execution through Sparkplug, while Google changes V8’s compilation pipeline with a non-optimizing compiler.
- Web developers and services whose pages rely heavily on JavaScript have a faster execution baseline in Chrome 91 without changing their own code.
Second-order effects
- Safari and other browser engines face renewed pressure to demonstrate comparable real-world JavaScript responsiveness as Chrome turns compiler work into a user-facing performance claim.
- Chrome’s performance work strengthens the value of optimizing web applications for V8, while Google’s later faster Sheets calculations in Chrome and Edge shows how browser execution gains can surface in productivity software.
Third-order effects
- If successive Chrome releases keep improving execution and load performance, browser competition shifts further toward engine and runtime efficiency rather than visible interface features alone.
- The retirement of Octane points to a durable constraint on that competition: browser makers will need to justify performance gains with workloads that reflect use, not only benchmark scores.
The trend: Browsers are increasingly differentiating through low-level JavaScript-engine improvements that translate into faster everyday web applications.