Performance · 4 min read
Measure the experience users see
A page can have a fast server response and still feel slow because its fonts shift, images arrive late, animations stutter or JavaScript blocks interaction. Review loading and interaction behavior on a midrange phone, an ordinary connection and the actual pages customers visit.
Use Core Web Vitals and browser performance traces to identify expensive work. Compare results before and after a change; component refactoring alone does not prove a performance improvement.
Keep static content on the server
Descriptions, service cards, article content, navigation labels and footer links rarely need browser-side state. In a Next.js application, rendering this content on the server avoids shipping unnecessary hydration work to the browser.
Reserve client components for real interaction: forms, menus, comparisons and other stateful controls. Load expensive capabilities only where they are useful.
Build motion that does not interrupt reading
Animate opacity and transforms rather than changing the size or position of the layout. Avoid animating large blurred surfaces on low-powered devices. Keep headings readable before hydration, and respect reduced-motion preferences.
Performance is a design constraint: every loading indicator, page transition and visual effect should support the user rather than delay them.