The Ghost in the Lighthouse: A Memory of Loading
I remember the lighthouse most clearly. It was a small, whitewashed tower on a distant, pixelated headland, rendered in a grainy JPEG on my grandmother’s dial-up connection. The rest of the webpage was a void, a blank white space where text and links were promised but had not yet arrived. For a long, humming minute, that lighthouse was the entire internet. It was a solitary, waiting sentinel.
I’d click a link and then there was nothing to do but watch. The top-down loading was a slow tide of information, each line of text a new wave revealing more of the shore. You learned patience. You learned the architecture of a page by the order in which it chose to introduce itself. The header image first, often, a banner of pixels coalescing from a blur. Then maybe a headline. Then, agonizingly, the body text, line by single line. You’d often read the first paragraph three times over as the rest of the article stubbornly refused to materialize below it.
This forced a kind of intimacy with the process. The web wasn’t a finished product presented on a platter; it was a performance, a construction happening in real-time before your eyes. You were aware of the fetch, the render, the layout. There was no concept of Cumulative Layout Shift because the layout itself was a slow, deliberate act of revelation. Elements didn’t jump; they emerged. It was unstable by our modern standards, but it was an honest instability. You knew what was happening.
Today, we’ve built lighthouses that are always on, blazing with instantaneous light. We preload, we prefetch, we lazy-load with such cunning that the user should never see the machinery. We obsess over LCP and CLS, chasing the ghost of that old white space, trying to banish it forever. And this is good. This is progress.
But sometimes, in our race to eliminate the wait, I wonder if we’ve lost the narrative of the load. That old, slow rendering told a story: content is coming, it is being assembled for you. The modern, sudden jank of a poorly optimized page tells a far worse story: one of carelessness, of a broken promise. It’s the difference between a craftsman slowly planing a piece of wood and a shelf collapsing off the wall.
I don’t miss the wait. But I remember the lesson of that lighthouse. Stability isn’t just about speed; it’s about respect. It’s about building a experience that doesn’t just arrive quickly, but arrives with intention, its layout a settled and thoughtful thing, not a frantic, last-minute scramble. We’re not just building faster pages; we’re building trust, pixel by stable pixel.
Notes & further reading
A few pages I came back to while writing this: