Performance and quality
Measure route behavior, bundle cost, images, client boundaries, motion, and runtime work without sacrificing source fidelity.
Performance and quality
Render on the server by default
Use client components only for stateful interaction or browser APIs. Keep large dependencies out of shared layouts and load expensive functionality at the point of use.
Images
Provide explicit dimensions or a constrained fill container, responsive sizes, appropriate priority, and accurate alternative text. Do not optimize protected logo bytes.
Motion
Motion should clarify state or continuity, use transform or opacity, remain interruptible, and respect reduced motion. Decorative continuous effects are not a quality substitute.
Verification
Run a production build, inspect browser errors, spot-check all routes, test keyboard behavior, and review desktop and mobile layouts in the source and alternate themes.