Learn how to use WordPress’s built?in Site Health tool to quickly spot and fix basic performance and security issues before they become real problems.
Why the WordPress Site Health Tool Matters on Day One
Before you install lots of plugins or send traffic to your new site, it’s worth learning the basics of the built-in WordPress Site Health tool. It gives you a simple, color-coded overview of common configuration, performance, and security issues so you can fix problems early instead of chasing mysterious bugs later.
Site Health is part of WordPress core, so you don’t need to install anything. You’ll find it in your dashboard and can safely run it as often as you like. WordPress groups results into critical issues, recommended improvements, and passed tests, so you always know what to focus on first.Source
Where to Find the Site Health Screen
To open Site Health in a current WordPress install:
- Go to Dashboard ? Tools ? Site Health.
- Wait a few seconds while WordPress runs its checks.
If you don’t see Site Health under Tools, your site may be running an older version of WordPress (it was introduced in WordPress 5.2), or your user role may not have permission to access it.Source
What You Should See
On the Site Health screen you’ll see:
- A status summary at the top (for example, “Good” or “Should be improved”).
- A list of Critical issues and Recommended improvements.
- A separate tab labeled Info with detailed technical data about your site.
Understanding the Status Tab
The Status tab is where you’ll spend most of your time as a site owner. It shows:
- Critical issues – items that may affect security or cause serious problems.
- Recommended improvements – configuration tweaks that can improve performance, reliability, or best practices.
- Passed tests – checks that are already in good shape.
Each item expands to show a plain-language explanation and, usually, a direct link or suggestion for how to fix it.Source
Common Messages You’ll See (and What to Do)
Here are a few examples of messages new site owners often see, and simple next steps:
- “You should use a persistent object cache” – This is a performance recommendation. For a small brochure site, you can usually leave this for later. For a busier site, ask your host if they provide Redis or Memcached, or use a reputable caching plugin.
- “Your site is not using HTTPS” – This is important. Make sure your hosting plan includes an SSL certificate and follow your host’s instructions to enable HTTPS, then update your WordPress and Site Address URLs to use
https://. - “Background updates are not working as expected” – This can affect security updates. Check that your hosting account email is correct and that automatic updates are allowed, or talk to your developer about a managed update process.
- “A scheduled event has failed” – This usually relates to WordPress’s internal task scheduler (cron). If it persists, your developer or host can review logs and fix the underlying cause.
Using the Info Tab as a Simple Site Snapshot
The Info tab doesn’t change settings; it simply lists technical details about your WordPress installation, server, database, themes, and plugins. It’s especially helpful when you’re working with support or a developer, because you can copy everything with one click and paste it into a support ticket.Source
Key Sections to Know
As a non-technical site owner, you don’t need to understand every line. Focus on these sections:
- WordPress – Shows your WordPress version, site language, and whether debug mode is enabled.
- Directories and Sizes – Helpful for understanding how big your uploads and database are.
- Active Theme – Confirms which theme your site is actually using (useful if you’re working with a designer).
- Plugins – Lists all active and inactive plugins, which is useful for troubleshooting.
- Server – Shows PHP version and other server details your host may ask for.
A Simple First-Week Site Health Checklist
During your first week with a new WordPress site, you can use Site Health as a basic launch checklist:
- Run Site Health from Dashboard ? Tools ? Site Health.
- Resolve any critical issues first, especially anything related to updates, HTTPS, or file permissions.
- Review recommended improvements and decide which ones to handle now versus later.
- Capture a snapshot from the Info tab using the “Copy site info to clipboard” button and save it in your project documentation.
- Schedule a recurring reminder (monthly or quarterly) to re-check Site Health.
What You Should See After Fixes
Once you’ve addressed the most important items, the Status tab should show:
- A green “Good” or similar message at the top.
- Zero critical issues.
- Only a small number of low-priority recommendations, if any.
How Site Health Connects to Security Basics
Site Health is not a full security scanner, but it does highlight several configuration issues that map to common web security risks, such as outdated software and insecure settings. The broader security community, including the OWASP Top 10 project, consistently emphasizes keeping software updated, using secure defaults, and monitoring for misconfigurations as core defenses against attacks.Source
When Site Health warns you about missing updates, disabled automatic updates, or questionable configuration choices, it’s effectively nudging you toward these best practices before they become real vulnerabilities.Source
Working with Your Host or Developer
Some Site Health items are easy for you to fix directly (like removing inactive plugins), while others are better handled by your hosting provider or developer (like adjusting PHP settings or server-level caching).
When you need help, you can:
- Copy the full Site Health Info report and paste it into your support ticket or email.
- Include a screenshot of the Status tab showing any critical issues.
- Mention any recent changes (new plugins, theme switch, major content imports) that happened before the issue appeared.
This kind of basic documentation makes troubleshooting faster and reduces back-and-forth questions.
How Often Should You Check Site Health?
For most business sites, a simple schedule works well:
- Before launch – Run Site Health and fix all critical issues.
- After major changes – Re-check after installing new plugins, changing themes, or migrating hosts.
- Ongoing – Review monthly or quarterly as part of your regular maintenance routine.
Pairing Site Health with a basic security and maintenance checklist (updates, backups, user access review) gives you a strong foundation without requiring deep technical knowledge.Source
Next Steps After You’re Comfortable with Site Health
Once you’re comfortable reading Site Health results and resolving basic issues, you can take a few next steps to strengthen your site:
- Enable automatic updates for minor WordPress core releases and security updates.
- Work with your host to ensure HTTPS is fully enabled and forced for all visitors.
- Install a reputable security plugin to add firewall rules, malware scanning, and login protection (in addition to, not instead of, Site Health).
- Create a simple internal document that records your Site Health status, hosting details, and key contacts.
From there, you’ll be in a much better position to collaborate with designers, developers, and marketing teams, because you’ll already understand the basic “health” of the system you’re all working on.
