SiteGround CPU Limit Suspension: The Upsell Machine and How to Escape

The actual CPU-second quotas (approximate)

These numbers are approximate — SiteGround doesn't publish them prominently and they adjust periodically. The point isn't the exact figure. It's that a single poorly-cached WordPress pageview burns 0.5–2 CPU-seconds, and one misbehaving plugin or one traffic spike blows through your month's quota in an afternoon.

What actually triggers the suspension

Anatomy of a typical SiteGround suspension (from forum reports and review sites):

1. Site runs fine for months.
2. Traffic grows or a plugin update makes something slightly less efficient.
3. CPU-usage warning email lands in your inbox — often filtered as spam.
4. A few days later: "Web Services on yourdomain is limited due to overage."
5. Site shows a "temporarily limited" or 503 error to visitors.
6. Two options in the dashboard: upgrade now, or wait for the quota reset at the start of next month.

The reviewers at OnlineMediaMasters and WebsiteRating both characterize this as a structural upsell mechanism rather than a resource-protection measure — the quotas are low enough that legitimate small-site growth trips them, and the suspension-vs-upgrade choice is engineered to convert.

The upgrade math (and why it's bad)

Typical SiteGround upgrade path over 2 years of a growing site:

• Year 1: StartUp at intro pricing ~$3/month = $36.
• Year 1 renewal: StartUp at renewal ~$15/month = $180.
• Year 2: Forced to GrowBig at renewal ~$25/month = $300.
• Year 2.5: GoGeek at renewal ~$40/month = $480/year.

That's $996 over ~2.5 years for what, infrastructure-wise, is a single WordPress site. The same workload runs on a $6/month VPS at DigitalOcean, Hetzner, or any offshore privacy-hosting provider — $150 over the same period.

The SiteGround value is ease-of-use, support quality, and the SG Optimizer plugin. Reasonable people can decide that's worth $800. But it's a choice, and the CPU-suspension mechanism is designed to make it feel mandatory when it isn't.

Fixing the quota issue without upgrading

Before you upgrade or move, rule out fixable causes:

1. SG Optimizer caching on full blast. Memcached, Dynamic Cache, CSS/JS minification. Cuts CPU dramatically.
2. Kill cron-heavy plugins. Broken Link Checker, anti-spam plugins with aggressive scanning, backup plugins running hourly.
3. Block bad bots. Cloudflare in front with bot fight mode + a WAF rule blocking AhrefsBot, SemrushBot, MJ12bot if you don't need them. These can consume 30–50% of a small site's CPU.
4. Fix wp-cron. Disable WP's internal cron and run a real server cron every 15 minutes. WP default fires cron on every pageview, which is terrible under traffic.
5. Database optimization. Purge post revisions, spam comments, expired transients. WP-Optimize or WP-Sweep.
6. Disable XML-RPC. It's a CPU magnet for brute-force attacks.

If after all of this you're still hitting the quota, the quota is genuinely too small for your traffic — and that's when upgrading or moving makes sense.

When moving is the right call

Move if any of these apply:

• You've already upgraded once and are being pushed to upgrade again.
• Your 2-year renewal cost exceeds $400.
• You're running any kind of custom app (not vanilla WordPress) — shared hosting is the wrong product.
• You want predictable cost rather than quota games.
• You're in the EU or care about GDPR specifically and SG's data-residency story doesn't fit.

Target destinations:

• Offshore privacy hosting (like LaunchPad Host) — fixed-price, no CPU quotas, crypto payment available. Our Starter plan is $6/mo with no execution quotas.
• Managed WordPress (Kinsta, Cloudways) — more expensive but genuinely managed.
• Hetzner or Netcup VPS — ~$4/month, European jurisdiction, excellent price/performance if you're comfortable with server admin.