Most Site Health warnings are not emergencies. WordPress flags anything that deviates from its defaults, even when the deviation is intentional or already handled at the server level. Before you chase a warning, check whether it's actually a problem on Flashcloud hosting: PHP version, object cache, and HTTPS warnings are usually already covered by the stack. Focus your time on the ones that flag real plugin, theme, or security issues.
Open wp-admin → Tools → Site Health to see your list. It splits into "Critical issues" and "Recommended improvements." Critical issues deserve attention. Recommended improvements are a mixed bag, some genuinely useful, some noise.
Warnings our stack already handles
A handful of common warnings don't apply to you, or resolve themselves once you check one setting.
"Your site does not have a persistent object cache"
WordPress recommends Redis or Memcached for object caching. Flashcloud provisions a Redis object cache automatically on WordPress hosting. If Site Health still flags this, it usually means the object cache isn't connected on your install yet, not that it's unavailable. Confirm LiteSpeed Cache is active (wp-admin → Plugins), since object cache integration on our stack runs through it. Once it's active and connected, this warning clears.
"PHP update recommended" or version warnings
We support PHP 7.4 through 8.3, with 8.3 as the default for new installs. If Site Health flags an old PHP version, the fix is a setting change, not a migration: open the PHP Version tile for your domain in the portal and switch versions. Test on staging first if the site relies on an older plugin, since jumping several major versions can break compatibility. See My WordPress site is slow for the broader performance picture; PHP version is one input among several.
"HTTPS status" / "Your site does not use HTTPS"
This shouldn't appear on a Flashcloud-hosted site with SSL issued. Free Let's Encrypt SSL is auto-issued about 5 minutes after your domain's DNS points to us, and it auto-renews. If this warning shows up, check that DNS is actually pointed at Flashcloud and that the SSL certificate issued successfully rather than assuming you need to configure HTTPS manually.
Warnings worth fixing
These reflect real gaps, not stack quirks.
Outdated plugins, themes, or WordPress core
This is the most important warning on the page. Outdated software is the number one way WordPress sites get compromised; see Securing your WordPress site for why. Update promptly, but not blindly: back up first (server-level backups run daily with 30-day retention, see Backing up your WordPress site), and if you run a store or anything with checkout flows, test the update on staging before pushing to production. WooCommerce sites in particular should follow the staging-first workflow in Running a WooCommerce store, since a broken update on a live store costs you sales, not just an afternoon.
"You should remove inactive plugins and themes"
This one is correct and easy to ignore. A deactivated plugin still has its code sitting on disk, and an unpatched vulnerability in that code is exploitable whether the plugin is active or not. Delete anything you're not using instead of merely deactivating it.
REST API or loopback request failures
These can indicate a security plugin or firewall rule blocking WordPress's internal requests to itself, which breaks scheduled tasks, some plugin updates, and certain editor features. Check whether a recently installed security plugin is the cause before assuming it's a server issue.
"Background updates are not working"
WordPress runs minor core updates automatically by default. If this is broken, it's usually a file permissions issue or a security plugin blocking the update mechanism, not something wrong with hosting. Rule out a conflicting plugin first.
Warnings you can usually ignore
A few Site Health items are informational rather than actionable:
- "Your site could not complete a loopback test" immediately after installing a new security plugin, often resolves itself or needs a plugin-side allowlist entry, not a server change.
- Debug mode / display errors notices when you've intentionally enabled
WP_DEBUGfor troubleshooting, expected and temporary. - Scheduled event delays of a few minutes, WP-Cron runs on page visits, not a strict clock, so small delays are normal on lower-traffic sites.
When to open a ticket
If a Site Health warning points at something server-side, HTTPS not issuing, PHP version switching not taking effect, object cache not connecting after LiteSpeed Cache is active and configured, open a ticket from Support → New ticket in the portal. That reaches a real person, not a bot, and you can attach the specific Site Health output so support isn't guessing at what you're seeing.