The Carpenter's Glimpse: On the Necessary Incompleteness of the First Frame
We spend our days chasing the ideal page load. We measure, we defer, we lazy-load, we split. The gospel is clear: nothing should move, nothing should render, until it can render perfectly and stably. We preach the virtue of the complete first frame, a pristine painting that snaps into place, free of the sin of layout shift. This obsession, I've come to believe, might be costing us the very soul of a fast-feeling experience.
The counterintuitive truth is this: a deliberately incomplete first render is often a profound act of user kindness. Our dogma against Cumulative Layout Shift (CLS) has mutated into a fear of showing anything at all until every last detail is calculated. We hold the user in a blank stare—sometimes for seconds—while JavaScript reconciles, fonts load, and images resolve their aspect ratios. We deliver stability, yes, but we deliver it after an eternity of nothingness. In our quest to prevent a janky 10-millisecond adjustment of a headline, we've mandated a 1000-millisecond void where the user questions if the link even worked.
The Value of a Working Draft
Consider the carpenter, not at the final unveiling, but mid-project. You see the frame of the bookshelf: the uprights are in place, the broad shape is clear, a few shelves are temporarily tacked. It's not finished, but you can already understand its function, its scale, its promise. This is what a skilled first glimpse can be. A headline in a fallback font. A block of text, even if the image beside it is still a grey rectangle of the correct dimensions. The primary button, in place and clickable, even if a decorative icon hasn't yet arrived.
This isn't about excusing sloppy layout. It's about a strategic prioritization of communicative scaffolding over visual polish. The human brain is an exceptional pattern-recognition engine, desperate for anchors. A skeleton of meaning, stable in its core but awaiting its final skin, provides those anchors instantly. It tells the user: "You are in the right place. Content is coming. Interaction is possible." The subsequent settling of fonts, the fading in of images, the final tightening of the layout—these become confirmations, not disruptions.
Our tools often fight us on this. The relentless pursuit of a 100 Lighthouse score can become a recipe for emptiness. `content-visibility: auto` can hide content until it's perfectly ready, but should it? Sometimes, showing the un-optimized image at low quality, right now, is the better service. Sometimes, letting a headline reflow once when its preferred web font loads is a worthy trade for having words to read immediately. We've conflated the metric—CLS—with the feeling. The feeling we should hunt is not "nothing ever moved," but "I was never left wondering."
The craft, then, lies not in building a perfect, static diorama that appears magically whole, but in engineering a graceful and informative progression from glimpse, to sketch, to finished work. It requires thinking in stages of usefulness, not just states of completion. It asks us to be okay with the first frame being a working draft, signed by the carpenter in pencil, because a draft in hand is infinitely more valuable than a promise of a perfect blueprint, still loading.
Notes & further reading
A few pages I came back to while writing this:
- El Paso, TX
- The Cartographer's Errant North: On the Drifting Baseline of a Core Web Vital
- Miramar, FL
- The Mason's False Line: On the Unbreaking Vow of a CSS Containment
- a useful directory
- The Archivist's Glove: On the Protective Grace of a Non-Touching Listener
- a practical rundown
- a local resource
- a regional guide
- one area's overview
- a helpful reference
- a place-by-place guide
- a nearby resource