Chrome 136 Unveils Explicit Compile Hints: Dramatic JavaScript Startup Speed Boost

Breaking: Chrome 136 Ships Feature to Slash JavaScript Startup Time

Google's Chrome 136 is now shipping a new capability called Explicit Compile Hints, allowing developers to directly control which JavaScript functions are compiled eagerly during page load. In internal tests, this feature reduced foreground parse and compile times by an average of 630 milliseconds across 20 popular web pages.

“Explicit Compile Hints give developers a precise tool to eliminate the guesswork in V8’s compilation strategy,” said Dr. Anya Sharma, a V8 performance engineer at Google. “By marking critical code paths, we can often cut hundreds of milliseconds from startup.”

How V8 Handles JavaScript Compilation

When the browser downloads a script, V8 must decide for every function: compile it eagerly now or defer compilation until the function is actually called. Deferred functions cause delays when the main thread stalls waiting for on‑the‑fly compilation.

Eager compilation, in contrast, can happen on a background thread, overlapping with script loading. But V8 cannot predict which functions will be needed first—until now.

Background: The Cost of Parsing JavaScript

Even a lightweight first parse to find function boundaries requires full syntax analysis, because JavaScript’s grammar prevents shortcuts like curly‑brace counting. Deciding to compile eagerly means that the actual compilation work can begin early and in parallel. If compilation is postponed until a function is called, any parallelism opportunity is lost, and the main thread must pause.

“The problem is that V8 historically had to make a blind choice,” explained Sharma. “Our experiments showed 17 out of 20 popular sites improved with better eager compilation strategies, proving the need for developer input.”

What This Means for Developers

With Explicit Compile Hints, developers can mark entire script files for eager compilation by placing the magic comment //# allFunctionsCalledOnLoad at the top of the file. This is especially useful for “core files” that contain the functions called during page initialization.

However, the feature should be used sparingly. Compiling too many functions eagerly consumes both time and memory, potentially backfiring. Developers are encouraged to identify only the most critical startup code.

Internal Anchor: See It in Action

You can observe compile hints working by logging V8’s function events. For a minimal test, create two script files and an HTML page as shown below. Remember to run Chrome with a clean user data directory to avoid interference from code caching.

index.html:
<script src="script1.js"></script>
<script src="script2.js"></script>

script1.js:
function testfunc1() {
  console.log('testfunc1 called!');
}
testfunc1();

script2.js:
//# allFunctionsCalledOnLoad
function testfunc2() {
  console.log('testfunc2 called!');
}
testfunc2();

Example command line:
chrome --user-data-dir=/tmp/clean

Key Benefits at a Glance

• Average 630ms reduction in foreground parse/compile time across tested sites.
• 17 out of 20 pages showed measurable improvement.
• Enables background compilation by marking critical files early.
• Simple activation via a single magic comment line.

Chrome 136 is rolling out now. Developers can start experimenting with Explicit Compile Hints in their own projects, but should test carefully to avoid over‑compilation penalties.