Most speed problems come down to four things: your pages aren't cached, your PHP or database is doing more work than it needs to, your images are too heavy, and static assets aren't served from somewhere close to the visitor. Fix those four and you've covered the majority of what actually shows up in PageSpeed and real-world load times.
On Flashcloud, LiteSpeed Web Server with LSCache runs on every shared and WordPress plan, and WordPress installs come with the LiteSpeed Cache plugin pre-configured plus Redis object cache. That means page caching and object caching are already working before you touch anything. Your job is mostly to avoid undoing that setup and to handle the parts caching can't fix: image weight, unused plugins, and database bloat.
Check caching is actually active
If a site feels slow, confirm caching first before chasing anything else. In WordPress, open the LiteSpeed Cache plugin settings and confirm page cache is enabled. A common cause of "caching is on but the site is still slow" is a caching-related plugin conflict, usually a second cache plugin fighting LSCache, or an aggressive minification setting mangling JavaScript. Run only one caching layer. If you installed WP Super Cache, W3 Total Cache, or similar before moving to Flashcloud, deactivate it, LSCache replaces that function entirely.
Object caching (Redis) speeds up database queries specifically, it won't help with image weight or render-blocking scripts. Both layers matter but they solve different problems.
Trim what PHP and the database have to do
Every plugin, widget, and tracking script adds PHP execution time and often extra database queries on each page load. Deactivate and delete plugins you're not using, don't just deactivate them, unused code sitting on disk is a security surface even if it isn't running. Check your PHP version too: newer PHP versions are meaningfully faster at the same workload. You can switch a domain's PHP version from the PHP Version tile in the portal, versions 7.4 through 8.3 are available, and the platform default is 8.2. If a plugin needs a specific PHP version, check its requirements before switching.
If you're getting upload or memory-limit errors that point to PHP resource limits (not the version itself), those are adjusted separately in cPanel under Software → MultiPHP INI Editor.
On the database side, a WordPress site that's been running for years often has thousands of stale rows: post revisions, expired transients, spam comments. Clean those out periodically with a plugin like WP-Optimize or via WP-CLI, and make sure whatever you use isn't itself adding overhead by running on every page load.
Compress and right-size images
Images are usually the single biggest chunk of page weight. Two separate problems tend to get lumped together: file size (compression) and display size (dimensions). A 4000px-wide photo displayed in a 600px-wide container wastes bandwidth no matter how well it's compressed. Resize images to the largest size they'll actually be displayed at before uploading, then run them through a compression tool or plugin. Modern formats (WebP, AVIF) produce noticeably smaller files than JPEG or PNG at the same visual quality, most image optimization plugins can serve these automatically to browsers that support them while falling back for older browsers.
Lazy-loading, deferring offscreen images until the visitor scrolls to them, is worth enabling too, either through your caching plugin's lazy-load setting or a dedicated plugin.
Put a CDN in front of static assets
A CDN serves your images, CSS, and JavaScript from servers close to the visitor instead of routing every request back to your origin server. This cuts latency and takes load off your hosting account during traffic spikes. Flashcloud includes Cloudflare CDN as a sidebar tool in the portal: proxy and caching toggles per domain, SSL/TLS mode control, and a cache purge button for when you've just pushed changes and need visitors to see the new version. Proxy and caching are on by default for hosted domains, so this is often already working without configuration.
If you publish new CSS or JS and don't see the change reflected, purge the Cloudflare cache rather than assuming the deploy failed, stale cached assets are a common false alarm.
Keep an eye on ongoing bandwidth and resource use
Once the above is in place, periodically check bandwidth, resource usage, and visitors in cPanel (or the equivalent dashboard cards if you're using the Meridian theme) so you catch a runaway plugin or traffic spike before it becomes a performance problem rather than after.
When to contact support
If you've enabled caching, optimized images, and confirmed a CDN is active but a specific page is still consistently slow, or you're not sure whether a plugin conflict is the cause, open a ticket from the portal. Support is real humans who can look at server-side logs and resource usage that aren't visible from the front end.