Performance ✦ 02 Oct 2026 ✦ 7 min read
The cost of a re-render
A frame budget is a design constraint, not a number you hit at the end.
We shipped a page that felt instant and a page that felt like it was thinking. The difference was not the bundle, the images or the framework — it was how many times the same component was told to draw itself.
The profiler made it obvious. On every scroll tick, a list of project cards re-rendered because their parent held a new object identity, and the object was passed straight into a memo boundary that could not tell it apart from the last one.
The fastest component is the one that never had to render. Everything else is a negotiation with the browser.
What the profiler said
Nothing looked wrong in the code review. Nothing looked wrong on the screen either, unless you watched the frame timings: the list was fine, the images were fine, and the whole page was still doing a full pass of layout work on every tick of the scroll wheel.
The expensive part turned out not to be the render itself but the layout it forced. A card that changes width invalidates the text inside it, and the browser has to re-shape and re-raster every glyph it draws.
The fix
The fix was not clever. It was to stop handing components things they did not need. A list of items took an array of primitives instead of an array of objects, the card took the fields it used instead of the whole record, and the state that changed on hover lived in the card rather than in a page three levels up.
Avoiding the re-render was cheap. Avoiding the reflow was the win — and that one needed no library at all, only the decision to keep the card's box the same size.
The rule
The rule I keep coming back to is dull and useful: measure the thing you are about to change, and change the smallest thing that can carry it.
Everything else is a story about the past — about the shape the component had when somebody wrote it, and the shape it has now.
Next note