The Cartographer's Unfolded Map: On the Premature Delivery of a Preloaded Route

We are taught, as a first principle of performance, to anticipate the user. To know their next move before they make it. This wisdom manifests in the eager preloading of critical resources, a technique held as sacrosanct. We preload the hero image, the main font, the core JavaScript bundle. We are the cartographers, diligently unfolding the next section of the map so the traveler need not pause. But in our zeal to smooth the journey, we risk a subtle, yet profound, error: we preload the route itself.

The modern single-page application, with its client-side routing, is a marvel of perceived speed. A user clicks a link and the new content materializes almost instantly, unburdened by a full page refresh. The received wisdom dictates that we should preload the code for these subsequent routes. The logic is seductive: by the time the user hovers over a link, we should have already begun fetching the JavaScript necessary to render that page. We call this ‘predictive preloading’ and wear it as a badge of sophisticated optimization.

But this practice is a gamble, and the house always wins. We are betting precious network bandwidth and browser processing power on a user’s intention—an intention that is often fleeting, distracted, or entirely misread. In our quest to shave off milliseconds for the user who follows through, we actively penalize the user who does not. We have consumed their data, drained their battery, and contended with other critical network requests—all for a page they never asked to see.

This is the cartographer’s folly: unfolding a detailed map of a region the traveler only glanced at. It creates a quiet chaos under the surface. The browser’s carefully prioritized queue of tasks is jostled by speculative work. A user on a slow connection might experience a perceptible stutter as their device works to fetch and parse a large JavaScript bundle for a ‘maybe’ page, while the ‘now’ page waits. We have traded a potential delay later for a guaranteed inefficiency now.

The more elegant, and more respectful, craft lies not in prediction, but in reaction. It is the subtle art of loading on interaction. The moment a user presses down on a link—a clear, unambiguous signal of intent—is the moment to begin. This ‘instant’ is more than fast enough; it feels magical because it is in direct response to a human action. It is a conversation, not a monologue. It respects the user’s agency and their device’s resources, building only the path they explicitly choose to walk. Sometimes, the most performant choice is not to pre-empt the user, but to listen to them.

Notes & further reading

A few pages I came back to while writing this: