V8's Explicit Compile Hints Slash JavaScript Startup Time by Over 600ms

Breaking: Chrome 136 Ships Feature to Drastically Speed Up Web Page Loading

Google has announced a major performance boost for JavaScript-heavy websites with the release of Chrome 136. The new Explicit Compile Hints feature allows developers to mark critical JavaScript files for immediate compilation, cutting average foreground parse and compile times by 630 milliseconds.

In an experiment with 20 popular websites, 17 showed measurable improvements. The feature targets the bottleneck of JavaScript parsing and compilation during page startup, a common drag on responsiveness.

How It Works

“When processing a script from the network, V8 must decide for each function: compile it eagerly or defer,” explained a V8 engineer. Without hints, functions called during page load are often compiled too late, blocking the main thread.

Eager compilation allows work to happen on a background thread, interleaved with network loading. The new feature uses a magic comment //# allFunctionsCalledOnLoad at the top of a file to signal that all functions should be compiled immediately.

Background: The JavaScript Startup Problem

JavaScript parsing is inherently complex. “Finding the end of a function requires full syntax parsing — there are no shortcuts,” the engineer noted. Lightweight parsing first, then actual parsing later results in duplicate work, wasting time during critical startup.

V8’s traditional lazy compilation defers compilation until a function is called, but that’s too late for parallelism. Explicit Compile Hints solve this by telling V8 which files matter most, enabling background compilation from the start.

What This Means for Developers

“This is particularly useful if you have a core file that contains your most important logic,” said a Chrome performance team member. You can even move code between files to create such a core file.

However, the team warns: “Use this feature sparingly. Compiling too much will consume time and memory and can backfire.” Selective application is key to realizing the 600+ ms savings.

See It in Action

Developers can test the feature by logging V8 function events. Create two script files: script1.js (without hint) and script2.js (with //# allFunctionsCalledOnLoad) and run Chrome with a clean user data directory. The improvement is visible in the console.

Example:
script1.js: function testfunc1() { console.log('testfunc1 called!'); } testfunc1();
script2.js (with hint): //# allFunctionsCalledOnLoad function testfunc2() { console.log('testfunc2 called!'); } testfunc2();

For more technical details, see Google’s V8 blog on the parsing and compilation internals.

Immediate Impact

Chrome 136 is rolling out now. Early adopters report up to 630 ms faster visible page loads. Web performance experts urge developers to identify one or two core files and apply the hint judiciously.

The feature is a step toward making complex web applications as fast as native apps, with zero runtime overhead beyond the initial compile.