Keep class composition understandable
Tailwind itself is designed to generate only the styles required by detected classes, but application maintainability still depends on how you structure components and tokens.
Common performance wins
Keep source detection focused, avoid unnecessarily scanning dependency trees, use the production build, optimize images and fonts separately, and avoid generating enormous sets of arbitrary dynamic classes.
Refactor repetition
When a class string is repeated because the UI is actually one component, create the component. Do not create abstractions solely to shorten a class list.