Pages you come back to run their scripts sooner
A speed release for the engine. Code a site ran before is now kept and reused on the next visit instead of being read and compiled again, and the engine's own start-up code is kept after the first page. Busy pages also do less style and layout work. On eleven recorded real pages, script, style and layout time fell by 6% against 0.1.419, and no page got slower.
Coming back to a page costs less
The first time a page runs a script, the engine reads it and turns it into code it can run. When the same site runs the same script again, that code is now taken from a cache instead of being made again. The cache is kept per site, so one site never learns what another ran, and an entry that does not check out is compiled afresh. By the third visit, script time is lower than in 0.1.419 on every page we measured.
The engine starts each page sooner
Before a page's own scripts run, the engine runs about seventy-seven of its own to build the web's interfaces. Those used to be compiled for every page. They are now kept after the first page and reused by every page after it.
Busy pages do less style and layout work
When a page adds a style sheet or changes a class, only the elements the change can reach are styled again, including rules with :has(), :is() and sibling selectors. A full layout keeps the parts of the page that did not change. Every recorded page renders pixel for pixel the same.