When one client affects the others.
THE SITUATION
Your allocation's CPU and memory limits are shared. One heavy site degrades everyone.
IDENTIFYING IT
WHM shows resource usage per account.
Look for an account consistently consuming a disproportionate share.
THE COMMON CAUSES
No caching enabled A heavy or badly built plugin Bot and attack traffic Backups running at busy times Misconfigured cron Genuine traffic growth
WHAT TO DO FIRST
Enable caching. That resolves most cases outright.
Check for bot traffic, which on many small sites exceeds human traffic.
TALKING TO THE CLIENT
Frame it as improving their site, which it is. A faster site benefits them regardless.
If it is genuine growth, that is good news and warrants a larger plan.
WHEN TO MOVE THEM
A client whose legitimate usage exceeds what a shared allocation supports should have their own account.
Present that as their site outgrowing the plan rather than as a problem.
WHAT NOT TO DO
Absorb it indefinitely. Every other client pays for it in performance.