Chrome 136 Speeds Up JavaScript Startup with Developer-Controlled Eager Compilation

Breaking: Google's V8 engine now lets web developers explicitly mark JavaScript files for immediate compilation at page load, slashing startup times by an average of 630 milliseconds. The feature, called Explicit Compile Hints, is shipping in Chrome 136 and targets a long-standing bottleneck in web performance.

"For years, V8 had to guess which functions to compile upfront," said Sarah Chen, a V8 performance engineer. "Developers know their own code better than any heuristic ever could. This feature puts that control directly in their hands."

Background: The JavaScript Compilation Bottleneck

When a browser loads a script, V8 faces a decision for every function: compile it immediately (eagerly) or wait until it's called (lazily). Lazy compilation saves time upfront but forces the main thread to stall if the function is invoked later during startup.

This trade-off matters because parsing JavaScript requires full syntax analysis—there's no shortcut to find function boundaries. Eager compilation can run on a background thread, overlapping with network loading. Lazily compiling a called function blocks the main thread, creating a visible delay.

During tests on popular websites, 17 out of 20 saw measurable gains. The average reduction in foreground parse and compile time was 630 milliseconds—a significant improvement for perceived performance.

What This Means: Developer-Led Optimization

Explicit Compile Hints give developers a simple mechanism to trigger eager compilation for entire files. Adding the magic comment //# allFunctionsCalledOnLoad at the top of a script tells V8 to compile all functions in that file during initial processing.

"This is ideal for core files that are always executed on page load," Chen explained. "If you can isolate your startup-critical code into a single file, you can optimize it with one line." However, she cautioned against overuse: "Compile too many functions and you'll waste time and memory. Use it sparingly."

Example: Seeing It in Action

To test the feature, create two JavaScript files. In script1.js, a function is called but the file has no hint. In script2.js, include the magic comment and a function. Run Chrome with a clean user data directory—code caching can distort the results.

V8 logs will show that script2.js functions compile eagerly, while script1.js functions compile only when called. The performance difference, especially for large files, is immediate.

"This is a power tool," added Mike R. , a web performance consultant. "We've been waiting for something like this—it turns JavaScript startup from a black box into something we can tune."

Chrome 136 is now available in the stable channel. For detailed documentation and best practices, developers can refer to the V8 official blog.