The Potter's First Ungrooved Clay: On the False Economy of a Perfectly Centered, Yet Unkeyed, Carousel

We are taught, with the fervor of doctrine, that motion is waste. That every pixel shifting on the screen is a tax on the user’s device, a drain on their battery, a sin against the gospel of Core Web Vitals. The common advice is a mantra of reduction: eliminate, remove, and, above all, stop. The ultimate goal, it seems, is a digital still life—a page so static and inert it could be printed and framed. But in our zeal to freeze the interface, we risk building a beautiful, high-performance prison for our content.

The most frequent casualty of this crusade is the humble carousel. It has become the poster child for poor performance, a whipping boy for every layout shift and janky scroll. The consensus is to axe it. Tear it out. Replace it with a static image or a grid of links. And on a spreadsheet of metrics, this looks like a win. The Largest Contentful Paint improves, Cumulative Layout Shift drops to zero. We have achieved a perfect, motionless score.

But what have we truly optimized for? Not for the user, but for the machine. We’ve traded a moment of potential friction for a guaranteed moment of cognitive load. By removing the carousel, we often force a choice onto the user that the carousel itself was designed to mediate. We present five promotions of equal visual weight and say, “You figure it out.” We collapse a narrative sequence into a chaotic grid. The page becomes faster, yes, but also more demanding, less guided, and arguably less effective at its primary job: communication.

The Performance of Communication

This is the counterintuitive heart of it: sometimes, a well-built, performant animation is not a wasteful extravagance, but the most efficient form of communication available. A smooth, purposeful transition can explain a relationship between elements far more quickly and intuitively than text ever could. It can focus attention, establish hierarchy, and provide spatial context. It is UI that speaks the language of gesture, not just instruction.

The problem was never motion itself; it was always poor execution. The janky, unoptimized carousel that loads assets haphazardly and causes the page to jump is indeed a failure. But the answer isn’t to ban all conveyances; it’s to build better roads. It’s to use `preload` for critical images, to set explicit dimensions, to leverage `transform` and `opacity` for silky-smooth compositor-only animations, and to provide accessible controls. It’s to treat the animation not as decorative fluff, but as a core component of the interface that deserves a performance budget and thoughtful implementation.

In our quest for perfect stability, we must not confuse a quiet engine for a successful journey. A page that is perfectly fast but fails to guide, to explain, or to engage has optimized for a metric, not for a human being. True front-end craft lies not in the blanket elimination of tools, but in the skilled and performant application of them. It is the potter knowing that a simple groove cut into two pieces of clay—a key—is what allows them to fit together perfectly, to hold under pressure, and to form something far stronger than two separate, perfectly centered, yet ultimately disconnected, lumps.

Notes & further reading

A few pages I came back to while writing this: