Split the Editor Out of the Critical Path

Decide what you would build from the brief alone. Everything below it is available, but the exercise stops working if you open it first.

The brief you were given

A rich-text editor is imported at the app entry and is a large share of the main bundle. It is used on one page by a minority of users. Split it out.

The trap — the wrong fix that looks right

Prefetching the editor chunk on page load so the interaction is instant. The main bundle is smaller, the analyser shows the win, and clicking Edit is immediate. The bytes are still being downloaded by every user on every visit, now competing with the resources the first screen actually needs — so the loading measurement gets worse for the majority who never edit anything, in exchange for a faster interaction for the minority who do. It is a split that moved the download later in the waterfall without removing it from anyone.