Signals you can measure
| Signal | Where to see it | Usually outgrown or fixable? |
|---|---|---|
| CPU seconds near the plan threshold | SiteGround: Client Area, Services, Settings, Statistics, CPU Seconds, per hour or day and per website | Fixable first if bots or polling widgets drive it; outgrown if it tracks real student activity after caching |
| Host warning emails or limited access | SiteGround's fair use policy describes early warnings, then possible access limits for extreme or repeated over-usage | Outgrown if it recurs after optimisation |
| Public pages fast, logged-in pages slow | Time a lesson page while logged in at a quiet hour | Often an application issue first: queries, object cache, heavy plugins |
| Drip emails and reminders run late | Compare scheduled and actual send times | WP-Cron only runs on page loads; fixable with a real cron if the host allows it |
| Scheduled scripts need to run often | SiteGround asks for at least 30 minutes between scheduled script executions | Outgrown if your jobs need tighter intervals |
| File count or database size limits | SiteGround inode limits (files, folders and email messages): StartUp 200,000, GrowBig 400,000, GoGeek 600,000; each database up to 1,000 MB | Fixable by cleaning old backups, logs and email; outgrown if real course data drives it |
Fix these before you pay more
SiteGround's own advice for high executions is a useful checklist for any shared host: find the source in traffic data, block or slow aggressive bots, disable chat or calendar modules that constantly refresh, protect the login page, add a CAPTCHA to comments, enable dynamic page caching, use the latest available PHP version, and delete unused plugins. SiteGround's fair use article says approaching the limits means the site has either outgrown its plan or needs optimisation, so rule out the second before buying the first.
WordPress's own scheduling also explains a common false alarm. The developer handbook says WP-Cron checks for due tasks on every page load and does not run constantly, so a task scheduled for 2:00 PM may not run until the next visit. A drip email that arrives hours late on a quiet site is a scheduling issue, not proof the server is too small.
Worked example: reading a CPU graph
Suppose a course site on SiteGround GrowBig, which has a threshold of 2,000 CPU seconds per hour, shows 1,700 in the evening hours for two weeks. These numbers are hypothetical. The owner finds a crawler hitting the course catalogue and a live chat widget polling every few seconds. After blocking the crawler, removing the widget and enabling dynamic cache, the evening peak falls to 900. That site has not outgrown shared hosting.
Now suppose the peak stays around 1,800 and lines up with the weekly live lesson, when 200 students log in, mark lessons complete and submit quizzes. Those requests cannot be page-cached. That is real growth, and the next step is more capacity, whether GoGeek's 4,000 per hour threshold or a different kind of hosting.
Next steps by budget
| Option | Published price | What you gain | What you take on |
|---|---|---|---|
| SiteGround GrowBig to GoGeek | GrowBig $4.99 intro, $29.99 renewal; GoGeek $7.99 intro, $44.99 renewal per month, prepaid 12 months | Double the hourly CPU-second threshold (2,000 to 4,000) | Still shared hosting with fair-use enforcement |
| DigitalOcean Basic Droplet | $12 per month for 1 vCPU and 2 GiB; $24 for 2 vCPU and 4 GiB; backups add 20% weekly or 30% daily | A fixed CPU and RAM size you choose, root access, system cron | You manage the operating system, security, backups and the WordPress stack |
| Kinsta managed WordPress | Single 35k plan $35 per month; overages $0.50 per 1,000 visits | Managed WordPress hosting; sites keep running over the visit limit, with alerts at 80% and 100% | Billing by visits or bandwidth; Multisite needs a higher plan |
| KnownHost managed VPS | Basic VPS from $43.25 per month: 4 cores, 6 GB RAM, 100 GB NVMe, 3 TB bandwidth | Daily maintenance, OS and control panel updates, firewall configuration, support | Backups are an add-on (JetBackup $8.95 per month); you still own the application |
| SiteGround Cloud | Price not verified for this guide | Autoscale at 75% of the last CPU or RAM unit, with a monthly cap you set | Higher base cost than shared; set the cap to control spend |
Questions that decide between the options
- Who will patch the server and restore it at 2 AM? If nobody, prefer managed hosting.
- Is the load steady or a weekly spike? Spiky load favours autoscaling or visit-billed plans; steady load favours fixed capacity.
- Do you need system cron, SSH or custom server software? That points to a VPS or Droplet.
- Have logged-in pages been profiled? If not, an upgrade may move the same slow query to a bigger server.
- What does the renewal price look like? Intro prices on shared plans rise sharply at renewal.
Questions before you decide
SiteGround says unlimited traffic. Can I still outgrow it?
Yes. The plan pages list unlimited traffic, but the fair use policy sets CPU-second thresholds per hour, day and month and says access may be limited for extreme or repeated over-usage.
Will a bigger plan fix late drip emails?
Not by itself. WP-Cron only runs when pages load, so the fix is a scheduled real cron job, which some shared hosts restrict. A VPS or Droplet gives you the system scheduler, but you still have to configure it.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- SiteGround: Fair use of hosting services Accessed 29 Oct 2026
- SiteGround: CPU resource usage graph explained Accessed 29 Oct 2026
- SiteGround: Reduce the number of executions Accessed 29 Oct 2026
- SiteGround: WordPress hosting plans Accessed 29 Oct 2026
- SiteGround: Cloud server autoscale Accessed 29 Oct 2026
- WordPress Developer Resources: Cron Accessed 29 Oct 2026
- Kinsta: Pricing Accessed 29 Oct 2026
- Kinsta: WordPress hosting overages Accessed 29 Oct 2026
- KnownHost: Managed VPS Accessed 29 Oct 2026
- DigitalOcean: Droplet pricing Accessed 29 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.