If your hosting account is hitting CPU limits, the fix is almost never "upgrade first." Start by finding what's actually burning cycles: a runaway plugin, a cron job running too often, a bot crawling your site aggressively, or an unoptimized database query that runs on every page load. Cut the source, and usage drops without spending anything.
Check your service detail page first for the current picture, then open cPanel's Resource Usage tool (under Metrics) to see your current CPU, memory, and process usage against your plan limits. That's where you'll see whether it's a sustained high baseline or repeated short spikes, which points to different causes.
Find what's causing it
Sustained high CPU usually means something is running constantly: a WordPress plugin polling an external API, a poorly written theme function, or a cron job scheduled too frequently. Spiky usage that correlates with traffic often means a specific page or query is expensive, or that a bot is hammering your site.
- Cron Jobs: open the Cron Jobs tile and check the schedule column. A job set to run every minute that only needs to run hourly is a common, easy fix. If you don't recognize a job, it may have come with a script installer or a plugin.
- WordPress plugins: deactivate plugins one at a time (or use a plugin like Query Monitor) to isolate the offender. Backup and revision plugins, security scanners, and anything doing real-time syncing are frequent culprits.
- Database queries: an unindexed table or a plugin running a heavy query on every page load will show up as CPU load tied to traffic. A query-monitoring plugin can point to the offending query; phpMyAdmin (a one-click login tile on your service page) can help you inspect and optimize it once found.
- Bots and scrapers: check Awstats or Raw Access in cPanel for unusual request patterns from a single IP range or user agent. Aggressive AI crawlers and content scrapers are increasingly common causes of CPU spikes that have nothing to do with real visitors.
Fixes that actually reduce load
Once you've found the source, the fix is usually one of these:
- Cache well. WordPress installs on Flashcloud get the LiteSpeed Cache plugin pre-configured with Redis object cache. Confirm it's active and not disabled by another caching plugin fighting for the same job. Page caching turns a database hit per visitor into a served-from-memory response, which is one of the biggest CPU reductions most sites can make.
- Reduce cron frequency. If a job doesn't need to run every minute, don't run it every minute. Move it to hourly or daily wherever the task allows.
- Remove or replace heavy plugins. Plugins that do image processing, live backups, or real-time analytics on every request add up fast, especially stacked together.
- Block bad bots at the edge. If Cloudflare CDN is enabled on your domain, the AI Crawlers panel lets you set AI assistant and model-training bots to Allow, block on ad pages, or block outright, stopping the request before it reaches your account's CPU.
- Set Cloudflare's security level appropriately. Turning it up from the default toward "I'm under attack" during a spike filters out more automated traffic before it hits your server.
When PHP settings are the actual limit
CPU usage is separate from PHP resource limits like memory_limit or max_execution_time. If a script is timing out or hitting a memory ceiling rather than driving sustained CPU load, that's a MultiPHP INI Editor adjustment, not a caching fix. Don't conflate the two: a script that runs slowly because of inefficient code will keep using CPU even after you raise its execution time limit. Raising the limit gives it more room to run, not less work to do.
When to contact support
If you've checked Resource Usage, ruled out an obvious plugin or cron cause, and usage is still climbing, open a ticket from Support in the portal. Include the time window from Resource Usage where usage spiked. Support can dig into details a customer-facing panel doesn't expose, which is often the fastest way to identify a process that's misbehaving outside of WordPress entirely.