One health score for every WordPress site you watch
VigilDeck combines update backlog, known vulnerabilities, PageSpeed, and PHP errors into a single health score per site, so a team can tell at a glance which site needs attention first.
At a glance
- One health score per site, rolled from four real signals
- Update backlog, known vulnerabilities, PageSpeed, and PHP errors
- Scores normalized for complexity so big stores are judged fairly
- A versioned algorithm so numbers never shift silently
- Health trends charted over time across every site
The problem with judging site health by feel
When you look after a lot of WordPress sites, the hard question is never "is everything perfect." It is "which site should I deal with first." VigilDeck answers that with a single health score per site that pulls together the things that actually put a site at risk: a backlog of pending updates, installed versions with known vulnerabilities, weak PageSpeed performance, and PHP errors piling up in the background.
The score is a prioritization signal, a fast read on where the risk is, not a control panel for changing anything. VigilDeck tells you which site is drifting and why, so you can point your time at the site that needs it instead of guessing or checking each one by hand.
Most teams track health in their heads or across a scatter of separate tools. Updates live in one place, a security scanner in another, performance in a third, error logs somewhere on the server. Nothing adds up to a single answer, so the site that is quietly rotting looks the same as the one that is fine until something breaks.
Raw counts also mislead. A large WooCommerce store with forty plugins will always show more pending updates and more moving parts than a five-page brochure site, but that does not make it less healthy. Judge the two by raw numbers and you punish the complex site for being complex, and you waste attention on the wrong one.
And when a number does move, you need to trust that the site changed, not the scoring. If the formula behind a health score can shift quietly under you, a score that drops from 90 to 78 tells you nothing, because you cannot tell whether the site got worse or the math did. Without a stable, transparent basis, the number stops being useful.
A health score you can actually trust
Each site's score is built from real risk signals, normalized so the comparison between sites is fair.
Update backlog
Core, plugin, and theme versions that have fallen behind feed into the score. A growing backlog is one of the clearest signs a site is being neglected, and it shows here before it becomes a problem.
Known vulnerabilities
Installed versions are cross-referenced against published advisories, so a plugin or theme running a version with a known security issue pulls the score down and gets flagged for attention.
PageSpeed performance
The site's Google PageSpeed results feed straight into health, so slow performance counts as the risk to rankings and conversions that it really is.
PHP errors
PHP errors accumulating in the background are a quiet signal of a site heading for trouble. VigilDeck factors them in so silent breakage shows up in the score.
Fair normalization
Scores are normalized for site complexity and site count, so a busy WooCommerce store is not unfairly punished next to a simple blog. The comparison across your portfolio stays honest.
Versioned scoring
The scoring algorithm is versioned, so the numbers do not silently shift underneath you. When a score changes, it is because the site changed, and you can trust the trend.
How the health score works
Connect your sites
Install the free VigilDeck connector plugin on each WordPress site and link it to your account. VigilDeck starts gathering the signals right away.
Signals get collected
Update status, installed versions, PageSpeed results, and PHP errors are streamed off-site and kept in one place per site.
A fair score is calculated
VigilDeck rolls the signals into one number, normalized for how complex and how many sites you run, using a versioned formula so the basis stays stable.
Prioritize from the dashboard
Open the <a href="/features/multi-site-dashboard">cross-site dashboard</a>, sort by health, and go straight to the site that needs you most, with the trend showing whether it is getting better or worse.
Why a rolled-up health score helps
Know what to fix first
Instead of scanning four tools per site, you read one score per site and sort. The site drifting toward trouble rises to the top, and your time goes where the risk actually is.
Fair across your whole portfolio
Because scores are normalized for complexity and site count, a big store and a small blog are judged on comparable terms. You trust the ranking because it is not skewed by size.
Numbers that stay stable
A versioned algorithm means a change in the score reflects a change in the site. You can watch the trend and act on it without wondering whether the scoring moved.
A reputation signal for clients
A clear, defensible health number is something you can show a client to prove their site is being looked after, and to justify the work when it is not where it should be.
Who uses website health monitoring
-
Agencies
Triage a whole book of client sites in seconds, send the team at the lowest-scoring sites first, and back up retainers with a health trend you can show.
-
Freelancers
Keep every site you maintain above a line you set, and catch the one quietly falling behind before it turns into an emergency call.
-
In-house teams
Give stakeholders one honest number per property that reflects real risk, so health is a shared, comparable metric rather than a gut feeling.
Related monitoring features
Website Health: frequently asked questions
What goes into the health score?
Four signals: pending update backlog across core, plugins, and themes; known vulnerabilities from cross-referencing installed versions against advisories; PageSpeed performance; and PHP errors. They roll into one score per site.
Is a complex store unfairly penalized?
No. Scores are normalized for site complexity and site count, so a large WooCommerce store is not punished simply for having more plugins and more moving parts than a simple blog.
Will the score change even if my site does not?
No. The scoring algorithm is versioned, so the numbers do not silently shift. A change in the score means the site changed, which is what makes the trend worth watching.
Is this a tool for updating or fixing my sites?
No. VigilDeck is a monitoring and prioritization platform. The health score tells you which site needs attention and why. You do the fixing in your own workflow.
How does health relate to PageSpeed monitoring?
PageSpeed is one of the four inputs to the health score. You can also view performance on its own through PageSpeed monitoring for the detail behind that part of the number.
Can I see health over time?
Yes. Health is charted over time per site, so you can see whether a site is steadily improving, holding, or drifting, with history depth set by your plan.
See which WordPress site needs you first
Connect your sites and let VigilDeck turn updates, vulnerabilities, performance, and errors into one health score per site.
Free for up to 3 sites · No credit card required · Cancel anytime