Upgrade when you're consistently hitting a resource ceiling, not when traffic merely spikes for a day. The signals that matter are disk space filling up, CPU or entry processes maxing out during normal hours, or your site slowing down under everyday load rather than a one-off surge. If you're seeing any of those repeatedly, Upgrade plan is available as a service action in the portal.
If you're not sure whether you're actually near a limit, check first. See Checking your hosting resource usage for exactly where to look.
Signals that mean it's time
- Disk usage near the cap. New uploads start failing, email delivery slows, backups can't complete. This is the clearest, least ambiguous signal.
- CPU or entry processes maxing out during normal traffic. If cPanel's Resource Usage tool shows you close to your plan's limits during ordinary hours, not just during a promotion or a bot crawl, you've outgrown the plan.
- Concurrent processes hitting the ceiling regularly. This usually shows up as intermittent 500 errors or a site that's slow for some visitors and fine for others.
- You've added sites. If you started on a plan sized for one site and now run several addon domains, each pulling from the same CPU and memory pool, the math changes even if no single site looks heavy. See Addon domains, aliases, and subdomains if you're not sure how your setup is structured.
- You're about to run a campaign, launch, or seasonal push. Upgrading a few days ahead of expected traffic is cheaper than firefighting during it.
Signals that don't mean it, yet
Not every slow page load is a resource problem. Before you upgrade, rule out the cheaper fixes:
- A single slow page. Often a plugin, an unoptimized database query, or missing caching, not a plan-wide shortage. Check WordPress plugin count and a caching layer before blaming the server.
- A one-time traffic spike that already passed. If your usage graphs show a single day's spike and then a return to normal, that's not a trend. Watch it for a week before acting.
- Large but rarely-accessed files. Big media libraries eat disk space but don't need more CPU. Offloading old files, or deleting unused backups you're keeping redundantly, can buy you time without a plan change.
- Bandwidth alone. Most plans have generous bandwidth, and a CDN layer absorbs a lot of the static asset delivery before it hits your origin server. Bandwidth caps are rarely the actual bottleneck.
How the upgrade itself works
Once you've confirmed it's a real ceiling, go to Services, click your hosting, and click Upgrade plan to pick a destination plan. Upgrades are prorated; for full mechanics, see Upgrading your hosting plan.
When upgrading isn't the right move
Two situations where you want a different product, not a bigger tier of the same one:
- You're already on the top shared-hosting tier. If you're maxed out there and still hitting ceilings, the next step is usually a VPS, which is a different product with dedicated resources, not a shared-plan upgrade.
- You want to isolate one heavy site. If one WooCommerce store or high-traffic app is dragging down other sites on the same account, moving it to its own service is usually a better fix than raising the ceiling for everything.
If you're not sure
If your usage graphs are ambiguous, or you want a second opinion on whether an upgrade or a different service type fits your situation better, open a ticket from the portal. Support is real people who can help you weigh the options before you commit to a plan change.