SSL, DNS, or availability failures
Certificate errors, DNS resolution problems, and non-2xx responses pull down the uptime component of the score immediately.
A website health score condenses uptime, performance, stability, and errors into a single number you can track over time instead of several separate dashboards.
Start your 7-day trial — no credit card, free plan after.
Uptime monitoring, performance checks, error tracking, and stability checks each answer a narrow question on their own. Reviewing several separate views to answer "is the site healthy today" does not scale once you are watching more than a couple of pages.
Without a composite score, teams tend to notice degradation only after one specific check turns red — by which point response times may have already been drifting upward, or a journey may have already been failing intermittently for days.
Every NorthDuty project has a single health score from 0 to 100. It recalculates automatically each time a health check completes, so it always reflects the most recent evidence rather than a stale snapshot.
The score is a weighted composite of four components: uptime (weight 30), performance (25), errors (15), and stability (10), each weighted by how directly it affects whether a visitor can use the page. Security, accessibility, and SEO are scored separately and do not move the headline number, and user journeys are reported on their own rather than folded into the score.
If a check has not measured one of the components — for example, no performance timing was captured — that component is left out and the score is normalized over whatever was measured. The score never penalizes you for data it does not have, but it also will not tell you the full story until every component has been measured.
The score reacts to real evidence collected across every layer NorthDuty checks, not just a single ping.
Certificate errors, DNS resolution problems, and non-2xx responses pull down the uptime component of the score immediately.
A gradual increase in response time lowers the performance component even before the page becomes fully unavailable.
Script errors and failed first-party API calls on the page lower the errors component, even when the page itself loads.
A page that renders blank or shifts heavily as it loads lowers the stability component.
The score is most useful as a trend line and a triage signal, not a single point-in-time grade.
A health score is only useful if it is built from real, continuously collected evidence rather than a single check run once a day.
NorthDuty recalculates its 0-100 score from uptime, performance, errors, and stability every time a health check completes, giving teams one trustworthy number to watch alongside journey results and the detailed checks behind it.
Keep exploring the feature pages and commercial routes connected to this topic.
Feature
Learn how NorthDuty combines editable user journeys and website health checks in one website monitoring project.
Explore Website MonitoringFeature
Send NorthDuty alerts to email, Slack, Teams, Discord, Google Chat, webhooks, Telegram, WhatsApp, and SMS.
Explore AlertingFeature
Generate PDF reports covering website health and user journeys. Download on demand or schedule recurring email delivery.
Explore ReportsFeature
NorthDuty runs your checkout, signup, login and form flows in a real browser on a schedule and reports the exact step that failed, with a screenshot.
Explore User Journey MonitoringPricing
NorthDuty plans are sized by how many checkout, signup and login journeys you monitor: Free, $29 Starter, $79 Pro, $199 Business. 7-day trial, no card.
Compare pricing plansMore NorthDuty guides on related website monitoring topics.
Article
What a real website health check measures, why we don't launch a browser for every check, and why "not measured" must never look like "no errors". The code is open source.
Read How a Website Health Check WorksArticle
How to set up a public status page for your website: what to include, how to manage incidents, and how to schedule maintenance so customers stay informed.
Read How to Set Up a Public Status PageArticle
How to monitor website uptime properly: check intervals, locations, false alarms — and the failures that return HTTP 200 so uptime checks never see them.
Read How to Monitor Website UptimeShort answers that summarize the practical takeaways from this guide.
It's a weighted composite of four components: uptime (weight 30), performance (25), errors (15), and stability (10), normalized over whatever was measured. Security, accessibility, and SEO are separate scores, and journeys are reported separately rather than included in the score.
It recalculates automatically every time a health check completes for the project.
Yes. You can create an alert rule with a health-score threshold that notifies your configured email destinations when the score falls below it.
No. It is normalized over whatever has been measured, and journeys are reported alongside it rather than inside it.
Use NorthDuty's health score to see, at a glance, whether uptime, performance, errors, and stability are trending the right way — with journey results right alongside it.
7 days with Pro features and limits, no credit card — then keep one daily journey on the free plan.