“Overusing 'use client'” is a high priority code quality issue that shows up in Next.js projects. It is one of the 125+ checks NexusBro runs on every audit — the kind of problem that is easy to miss in code review yet cheap to fix once you know exactly what to look for.
Left unaddressed, it makes the codebase harder to maintain and more likely to regress on the next change. The good news: this is a well-understood pattern with a deterministic check and a concrete fix, both of which are below. You can verify it by hand using the command shown, or let an automated scan find every instance of it across your whole site in one pass.
NexusBro checks for this automatically during a Next.js audit. To verify it yourself, run the check below and apply the fix it describes:
Check for 'use client' overuse: grep -rn "'use client'" src/ --include="*.tsx" | wc -l. If >60% of components are client components, flag as architecture issue. Server components should be the default.
Code-quality issues rarely break anything today, but they are where tomorrow’s bugs come from. Catching them early keeps the codebase fast to change and cheap to maintain as it grows.
NexusBro audits your whole site for this check and 120+ others across performance, SEO, accessibility, and security, then hands you a copy-paste fix prompt for your AI coding tool. Free for your first scan, no signup required.
Run a free audit →Explore more: All fixes · Next.js audit report · Run a free scan · Pro plans