Web hosting
Hosting CPU limits: what shared CPU means for a website
Shared-hosting CPU limits keep one account from monopolizing a multi-tenant server. Hitting a CPU/resource boundary can come from uncached dynamic traffic, cron, imports, malware, inefficient plugins/queries, image processing, or a workload that genuinely needs a VPS.
Correlate CPU events with requests/jobs
Review hosting resource metrics and logs around the limit event. Identify PHP processes, cron jobs, database work, admin actions, bots, backups, or scheduled imports at the same time.
A traffic spike served from static/cache may use little CPU while one expensive admin import uses a lot.
Reduce avoidable dynamic work
Enable safe page caching, optimize slow database queries/plugins, move long maintenance jobs to quieter windows, disable abusive bots/endpoints where appropriate, and fix loops or malware.
Do not hide a compromised site by simply buying more CPU.
Check other shared limits too
Process/concurrent connection, memory, I/O, inode, and database limits can produce similar symptoms. A CPU graph alone may not explain request queueing or 5xx errors.
Measure PHP worker occupancy and request duration when available.
Move to VPS when control/isolation is the requirement
If the healthy application persistently needs more CPU/concurrency, custom services, root access, or predictable resource ownership, a self-managed VPS is the clearer boundary. Capture a final shared-hosting baseline before moving so the VPS can be sized from real demand and the migration has measurable success criteria.
- Map events to workload.
- Optimize repeated dynamic work.
- Check other resource ceilings.
- Upgrade for sustained legitimate demand.