A flexible CMS should never make the public website feel sluggish. The key is keeping data fetching and browser JavaScript proportional to what each route actually needs.
Start with the friction
- Use Server Components for editorial copy that does not require browser state.
- Keep content schemas structured so editors cannot accidentally break page hierarchy.
- Optimize media delivery and revalidate only the routes affected by an edit.
Make the next revision useful
Test the full path from editing in the dashboard to viewing on a mobile phone. Editorial convenience and public speed belong to the same system.
The goal is not to add more activity. It is to make the next decision clearer, then verify whether the change helped.