Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Web hosting

Hosting CPU limits: what shared CPU means for a website

Published August 2026 · 2 min read · Updated 2026-09-05

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.

Next step

Understand CPU quotas, throttling, concurrency and noisy application work so a hosting CPU limit is interpreted from measurements instead of plan labels alone.

Explore DotMoose web hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Virtualmin vs cPanel: Which Control Panel Should You Choose?

Virtualmin vs cPanel compared on licensing cost, account and site management, email, DNS, backups and migration, so you can pick the control panel that fits how you host.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

More web hosting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move