The Cartographer's First Perfect Map: On the Friction of an Impossibly Fast Journey
We are, all of us, obsessed with speed. The gospel of web performance preaches a singular truth: faster is better. Shave off milliseconds, compress another kilobyte, preload, prefetch, pre-render. The goal is a frictionless, instantaneous arrival. It’s the digital equivalent of a teleportation device, whisking a user from intention to information with zero resistance. But I’ve started to wonder if, in our zeal for the instant, we are building journeys so fast they feel like destinations, and in doing so, erasing the very experience of travel that gives a place—or a webpage—its meaning.
Our modern performance advice often treats the user’s path as a problem to be solved, a nuisance to be eliminated. We aim for the ideal of a page that loads ‘in the blink of an eye’. But consider the physical world. The most memorable journeys are rarely the fastest. They are the ones where you feel the terrain change underfoot, where you catch a glimpse of something unexpected from a train window, where the gradual approach to a landmark builds a sense of anticipation that makes the final arrival momentous. This subtle friction is not an enemy of a good experience; it is often its architect.
This is the paradox of the instant page. When a user arrives at a complex piece of writing or a detailed application interface with the abruptness of a jump cut, they are given no time to orient themselves. There is no gradual rendering of the layout, no sequential painting of elements that allows the eye to find its footing. It simply *is*. This can be disorienting. The milliseconds of a traditional load—the brief appearance of a skeleton screen, the progressive rendering of a font, even the slight delay before an image snaps into place—act as a cognitive ramp. They provide a spatial and conceptual context, a gentle onboarding process for the user’s brain.
The tyranny of the speed metric has led us to declare any loading indicator a failure. But what if a well-designed loading state is not a sign of sloth, but of craft? It is a cartographer’s legend, a small key that teaches you how to read the map you are about to see. It sets expectations and assures the user that something is indeed happening. An instant load, by contrast, offers no such assurance. It can feel abrupt, even jarring, leaving the user to question whether they clicked the right link or if the content is fully present. The lack of any perceivable process can create a different, more insidious kind of friction: the friction of disorientation.
Beyond the Stopwatch
I am not, of course, arguing for slow websites. Sluggishness born of bloat is a genuine affliction. But our pursuit of performance must become more nuanced than a simple race to zero. The goal should not be the elimination of time, but the thoughtful choreography of it. We must ask ourselves not just ‘How fast can we make it?’ but ‘What is the right speed for *this* experience?’ A sprawling news article might benefit from a slightly more deliberate reveal, allowing the reader to settle in. A simple search result, however, might rightly aim for pure immediacy.
The craft lies in designing the journey, not just the destination. It’s the difference between a cartographer who simply prints names on a page and one who understands how the contours of the land and the flow of a river tell a story. Sometimes, the most respectful thing we can do for a user is to honor the time it takes to meaningfully engage with our work. By fetishizing speed above all else, we risk building exquisitely fast pages that feel strangely hollow, like arriving at a breathtaking vista by teleporter, having missed the climb that makes the view mean something.
Notes & further reading
A few pages I came back to while writing this: