What Is a Website Health Score, and Does It Actually Matter?

A website health score is a summary of automated technical checks, not a grade on how well your website works for customers.

• WordPress runs about two dozen automated checks on your site and sorts the results into critical issues, recommended improvements, and passed tests.
• WordPress itself no longer shows a percentage. Numeric scores come from site management tools that summarize the same underlying checks.
• The checks cover software versions, server configuration, and security basics. They say nothing about design, content, or whether the site generates leads.
• A perfect score is not always the goal, and not every flagged item is worth fixing.
• The score is most useful as a trend over time, not as a number to compare against another business.

A website health score is a summary of automated technical checks that run against your website, usually expressed as a number out of 100 or as a simple status like “good” or “should be improved.” In WordPress, those checks look at whether your software is current, whether your server is configured sensibly, and whether basic security and performance settings are in place. The score is a maintenance indicator. It tells you whether the machinery under your website is in good working order. It does not tell you whether your website is any good at bringing you customers, and those are genuinely different questions.

Here is what is worth understanding:

• What WordPress actually tests
• Where the number itself comes from
• What the score cannot tell you
• Whether you should try to reach 100
• What you can reasonably check yourself

What does WordPress check when it measures site health?

WordPress has included a built-in Site Health tool since 2019. You can find it in your admin area under Tools, then Site Health. It runs roughly two dozen automated tests and groups the results into three buckets: critical issues, recommended improvements, and passed tests.

The tests fall into a few practical categories:

• Software currency. Is WordPress itself up to date? Are your plugins and themes current, and are any of them abandoned by their developers?
• Server environment. Is your host running a supported version of PHP, the programming language WordPress is built on? Is the database software current? Is there enough disk space to install updates safely?
• Security basics. Is the site served over a secure connection? Is debugging mode accidentally left switched on? Can anyone register an account with elevated permissions?
• Background processes. Can the site reach the outside internet to fetch updates? Are its scheduled tasks running? Is caching in place so pages load quickly?
• Visibility settings. Is the site accidentally telling search engines not to index it, a setting that is useful during development and damaging afterward?

That last one is a good illustration of why these checks matter. A single forgotten checkbox can keep a perfectly good website out of Google entirely, and nothing about the site’s appearance would tell you.

Where does the number in my report come from?

This part surprises people, so it is worth being precise about it. Early versions of the WordPress Site Health tool did show a percentage. WordPress removed it in late 2019, partly because site owners were fixating on reaching 100 percent when the number was never meant to be a measure of quality. Today, core WordPress shows you two states: “Good” or “Should be improved.” No number.

So when you see a health score of 92 or 100 in a maintenance report, that number is coming from the tool used to manage the site, not from WordPress itself. Those tools read the same underlying WordPress test results and convert them into a score, weighting critical issues more heavily than recommended ones. The tests are WordPress. The arithmetic is the reporting tool.

One practical consequence: these scores are not comparable between websites. Plugins are allowed to add their own tests to Site Health, so two sites in identical condition can produce different scores simply because they run different software. A score is meaningful compared against itself over time. It is not meaningful compared against another business.

What a health score does not tell you

This is the part I would most want a business owner to take away. A health score measures whether your website is well maintained. It says nothing about whether your website works.

A site can score a perfect 100 and still have a homepage that fails to explain what the business does, a contact form nobody can find, copy written for the owner rather than the customer, and not a single lead to show for the month. Every automated test passes because every automated test is asking a different question. None of them ask whether a stranger landing on the page understands what you offer or knows what to do next.

The reverse is also true. A site with a couple of recommended improvements outstanding can perform beautifully for its owner. If the flagged item is a caching recommendation on a small brochure site that already loads fast, fixing it changes nothing a customer would notice.

So treat the score the way you would treat a clean inspection on a work vehicle. It means the van will start, the brakes work, and nothing is about to fail. It does not mean anyone is calling you to book a job. If your site is technically healthy and still not producing inquiries, the problem is somewhere else, and the honest answer is that a healthy website and a website that generates leads are two separate pieces of work.

Should you try to get to 100?

Not necessarily, and chasing it can waste money.

Critical issues are worth acting on promptly. An out-of-date WordPress installation, an unsupported PHP version, or a broken secure connection are real risks with real consequences, and they tend to be straightforward to resolve.

Recommended improvements deserve judgment. Some are genuinely valuable. Others flag deliberate decisions. A site might not have a persistent object cache because the hosting plan does not offer one and the site does not need one. A test might flag a missing PHP module that nothing on your site uses. Resolving those items to clear a warning is effort spent on the report rather than on the website.

What I care about more than the number is the direction. A score that drifts downward month after month usually means updates are being skipped or the hosting environment is falling behind, and both compound quietly. A stable score with the occasional recommended item outstanding is a normal, well-maintained website.

What can you handle in-house?

More than you might expect, and you do not need any additional software to do it.

• Look at the screen yourself. Log into your WordPress admin area, go to Tools, then Site Health. Anything under critical issues is worth understanding, and WordPress explains each item in plain language with a description of why it matters.
• Check the search engine visibility setting. Under Settings, then Reading, confirm that discouraging search engines is not enabled. This is a two-second check that occasionally saves a business months of invisibility.
• Keep updates from piling up. If you are comfortable applying WordPress and plugin updates, doing so regularly resolves a good portion of what Site Health flags. Make sure a recent backup exists first.
• Ask your host about the environment. PHP and database versions are usually the host’s responsibility, and a support request is often all it takes.

Where this gets harder is judgment and consequence. Knowing which recommended items to ignore takes experience. Applying updates on a site running a page builder and a dozen plugins carries some risk of something breaking, which is why the sequence matters: verified backup first, update second, check the site afterward. If your website is central to how customers reach you, having someone accountable for that sequence, whether that is you on a calendar reminder or a managed service, matters more than the score itself.

The useful way to read your health score

Read it as a maintenance signal, not a performance review. A good score means the technical foundation is sound, updates are current, and nothing is quietly broken. That is genuinely worth having, because the failures it prevents are the expensive kind: a site down for two days, a security problem in software nobody updated, a search engine setting that kept you invisible.

What it will not do is tell you whether your website is earning its keep. That question is answered by whether visitors understand what you do, trust you, and can easily get in touch. If your technical foundation is solid and the phone still is not ringing, that is the more useful place to look, and it is worth reading about why a website might not be generating leads and how to build trust with the people who find you.