Understanding and Improving Health Score: A Guide for Website Managers
Understanding and Improving Health Score: A Guide for Website Managers
When you manage 20, 50, or 200 websites, you need a quick way to check website health. Not clicking through every website individually, not manually checking each SSL expiration date, not verifying response times in a separate tool. You need one number that instantly tells you: this website is healthy. Or: something's wrong here.
That's exactly what the website health score in pingport delivers. A rating from 0 to 100, automatically calculated, combining six different quality metrics. This guide explains how the score works, what each metric means, and how you can improve your website score.
What Is the Health Score?
The health score is a single number between 0 and 100 that describes the overall condition of a website. It's automatically calculated by the HealthScoreService and cached for one hour per website.
Where Do You See the Score?
- Dashboard: The portfolio score shows the average across all active websites
- Website list: Every website has a health score column
- Website detail page: Overview tab with score gauge and breakdown of all metrics
Score Ranges
| Score | Meaning | Color |
|---|---|---|
| 80-100 | Healthy — everything is fine | Green |
| 50-79 | Needs attention — at least one issue | Yellow |
| 0-49 | Critical — immediate action needed | Red |
A score of 80+ doesn't mean everything is perfect. It means no single factor is bad enough to pull the overall score below the threshold. A score below 50, on the other hand, means at least one metric is costing massive points — and you should check immediately what's going on.
The 6 Metrics in Detail
The health score consists of six weighted metrics. Each metric produces a partial score from 0 to 100, which is multiplied by its weight.
1. Uptime 24h (30% Weight)
The most important metric. Based on the uptime percentage over the last 24 hours, calculated from uptime checks.
How the partial score is calculated:
- 100% uptime = 100 points (full partial score)
- 99% uptime = proportionally reduced
- Each percentage point below 100% reduces the partial score
What this means in practice:
- 100% uptime in 24h: 30 out of 30 points
- 99.5% uptime (~7 minutes downtime): ~29.85 out of 30 points
- 95% uptime (~72 minutes downtime): ~28.5 out of 30 points
- 90% uptime (~144 minutes downtime): ~27 out of 30 points
Brief outages cost little score. But if a website was offline for hours, it shows up significantly.
Data source: UptimeService — uses raw data from the last 24 hours.
2. SSL Certificate (20% Weight)
Based on how long the current SSL certificate remains valid.
Score levels:
- More than 30 days valid = full score (100 points)
- 14-30 days = reduced but still acceptable
- 7-14 days = significantly reduced
- Under 7 days = critically low
- Expired = 0 points
What this means:
An SSL certificate expiring in 60 days costs you no points. One expiring in 5 days pulls the score down massively. And an expired certificate gives zero points for this metric — that alone costs you 20 points in the overall score.
Data source: currentSslCertificate — the currently active certificate for the website.
3. Domain Expiration (15% Weight)
Based on how long the primary domain is still registered.
Score levels:
- More than 90 days = full score
- 60-90 days = slightly reduced
- 30-60 days = noticeably reduced
- 14-30 days = critical
- Under 14 days = very critical
Why this matters:
An expired domain is worse than an SSL error. The website is completely gone, someone else might register the domain, and SEO damage can last months. That's why domain expiration contributes 15% to the score.
Data source: primaryDomain — the website's main domain with WHOIS data.
4. Response Time (15% Weight)
Based on the average response time of the website.
Score levels:
- Under 500ms = excellent (full score)
- 500-1000ms = good, slightly reduced
- 1000-2000ms = acceptable, noticeable reduction
- 2000-3000ms = slow, significant reduction
- Over 3000ms = critically slow
What this means in practice:
A website with 300ms response time gets full marks. One with 2500ms loses noticeable points. This motivates addressing performance issues — slow websites cost not just user experience but also health score.
Data source: Average response time from uptime checks.
5. Open Alerts (10% Weight)
Based on the number of unresolved alerts for the website.
Score levels:
- 0 open alerts = full score
- Each additional alert reduces the score
Which alerts count:
All unresolved alerts: downtime, SSL expiry warnings, domain expiry warnings, slow response alerts. Once an alert is resolved (manually or automatically on recovery), it drops out of the calculation.
Why this matters:
Open alerts are a sign that something is wrong and nobody is dealing with it. The health score penalizes this — not to be annoying, but to make sure problems don't sit around unaddressed.
Data source: alerts — unresolved alerts for the website.
6. Monitoring Status (10% Weight)
Based on whether monitoring is enabled and the website has an active status.
Score logic:
- Monitoring enabled + status active = full score (100 points)
- Monitoring disabled = 0 points
- Status paused or archived = reduced
Why this is a metric:
A website without monitoring is a website you know nothing about. No uptime checks, no SSL checks, no alerts. That's by definition not a good state. That's why monitoring status is its own metric — it motivates keeping monitoring active for all websites.
Score Calculation: A Concrete Example
Let's take a website with these values:
| Metric | Value | Partial Score (0-100) | Weight | Contribution |
|---|---|---|---|---|
| Uptime 24h | 99.8% | 99.8 | 30% | 29.94 |
| SSL | 45 days valid | 100 | 20% | 20.00 |
| Domain | 120 days valid | 100 | 15% | 15.00 |
| Response Time | 850ms | 80 | 15% | 12.00 |
| Alerts | 1 open alert | 60 | 10% | 6.00 |
| Monitoring | Active | 100 | 10% | 10.00 |
| Total | 92.94 |
Score: 93 (rounded). Green, healthy. The open alert and slightly slower response time cost a few points, but overall things look good.
Now the opposite:
| Metric | Value | Partial Score (0-100) | Weight | Contribution |
|---|---|---|---|---|
| Uptime 24h | 92% | 92 | 30% | 27.60 |
| SSL | Expired | 0 | 20% | 0.00 |
| Domain | 10 days valid | 20 | 15% | 3.00 |
| Response Time | 4200ms | 10 | 15% | 1.50 |
| Alerts | 3 open alerts | 20 | 10% | 2.00 |
| Monitoring | Active | 100 | 10% | 10.00 |
| Total | 44.10 |
Score: 44. Red, critical. The expired SSL alone costs 20 points. The domain is about to expire, the site is slow, and three alerts are sitting unaddressed. Immediate action needed.
Common Reasons for Bad Scores — and How to Fix Them
Expired SSL Certificate
Score impact: Up to -20 points Fix: Renew the SSL certificate. For Let's Encrypt, check the auto-renewal configuration. Ask your hosting provider whether automatic renewal is active. pingport warns you at 30, 14, 7, and 1 day before expiry — use these warnings.
Slow Hosting
Score impact: Up to -15 points Fix: Find the cause. Shared hosting overloaded? Server resources too tight? No caching? Sometimes switching from 5 EUR shared hosting to a 15 EUR VPS drops response time from 3000ms to 400ms.
Monitoring Disabled
Score impact: -10 points (plus indirectly more because no uptime data is available) Fix: Turn monitoring on. There's no good reason to keep monitoring disabled permanently (for planned maintenance, use maintenance windows instead).
Unresolved Alerts
Score impact: Up to -10 points Fix: Go through your alerts and address them. Either fix the underlying problem (the alert resolves automatically) or manually mark the alert as resolved if it's no longer relevant.
Domain Expiring Soon
Score impact: Up to -15 points Fix: Renew the domain. Enable auto-renew at your registrar. pingport warns you at 90, 60, 30, and 14 days before expiry.
Frequent Brief Outages
Score impact: Variable, depends on duration Fix: Investigate the cause. Is it the server, the DNS provider, a firewall, DDoS protection? Uptime checks in pingport show you exact times and HTTP status codes.
Quick Wins: The 5 Actions with the Biggest Score Impact
If you want fast results, focus on these five actions:
1. Enable Monitoring (+10 Points)
The easiest action: make sure monitoring is turned on for all active websites. Without monitoring, no uptime score, no response time score, no alerts. This alone can add 10 points.
2. Renew SSL Certificate (+Up to 20 Points)
An expired or soon-to-expire SSL certificate is the single biggest score killer. Renew it, and you get up to 20 points back. Enable auto-renewal so it doesn't happen again.
3. Resolve Open Alerts (+Up to 10 Points)
Go through your alerts. Every resolved alert improves the score. This is also a good exercise for team hygiene: alerts that have been open for weeks point to a process problem.
4. Upgrade Slow Hosting (+Up to 15 Points)
If a website consistently has over 2000ms response time, it costs points. A hosting upgrade or server optimization (caching, CDN, PHP version) can drastically improve response time.
5. Renew Domains Early (+Up to 15 Points)
Domains expiring in less than 30 days cost score. Renew them early and enable auto-renew. This keeps the domain metric permanently at its maximum.
Portfolio Score: Keeping Track of Overall Website Health
Beyond individual website scores, pingport shows a portfolio score on the dashboard. This is the average of all active websites.
What the Portfolio Score Tells You
- Portfolio score 85+: Your portfolio is in good shape. Individual websites may have minor issues, but everything is running well overall.
- Portfolio score 60-84: Some websites need attention. Look at the yellow and red scores.
- Portfolio score below 60: Multiple websites have serious problems. Prioritize the websites with the lowest scores.
Portfolio Score Trends
The portfolio score is a good indicator of the overall quality of your website management. If it drops over weeks, problems are being systematically ignored. If it rises, you're consistently working on quality.
Weekly Check Workflow for Agency Teams
The health score reaches its full potential when you build it into a regular workflow. Here's a proven approach for teams:
Monday Morning Routine (15 Minutes)
- Open dashboard: Check the portfolio score. Is it stable, up, or down?
- Identify red websites: Which websites have a score below 50? These are the priority.
- Scan yellow websites: Which websites are between 50 and 79? Is there a pattern (same host, same client)?
- Review alerts: Go through open alerts. Which can be resolved immediately?
- Create todos: For each critical website, create a todo, assign it to the responsible team member, set a deadline.
During the Week
- Work through todos: renew SSL, check hosting, optimize performance
- Keep an eye on alerts: check new alerts immediately, don't wait until Monday
- Check off completed tasks: the score improves as soon as problems are fixed
Friday Afternoon (5 Minutes)
- Quick check: Are the Monday todos done? Has the portfolio score improved?
- Document open items: What's left for next week?
This workflow takes 20 minutes per week. In return, you have the certainty that no problem goes unnoticed.
Frequently Asked Questions About Health Score
How Often Is the Score Updated?
The score is calculated on access and cached for 1 hour. After an hour, pingport recalculates it with the latest data. So you always see a score that's at most 60 minutes old.
Can I Manually Influence the Score?
Not directly. The score is based exclusively on measured metrics. You can only improve it by fixing the underlying problems. This is intentional: the score should reflect reality, not a polished picture.
Do Paused Websites Count Toward the Portfolio Score?
No. The portfolio score calculates the average across active websites only. Paused and archived websites are not included.
What Happens During Planned Maintenance?
During an active maintenance window with suppress_monitoring, no checks run. That means the score is based on the last available data. With suppress_alerts, checks continue but alerts are suppressed — the score is still affected if the website goes briefly offline during maintenance.
Why Does My Website Have a Low Score Even Though Everything Works?
Check the score breakdown on the website detail page. It's usually one of these factors:
- SSL certificate expiring soon (under 30 days)
- Domain expiring soon (under 90 days)
- One or more alerts are still open
- Response time is higher than expected
Measure Website Quality — and Continuously Improve It
The website health score isn't a gimmick. It's a tool that helps you check website health, catch problems early, and measure website quality — across your entire portfolio.
The formula is simple: uptime, SSL, domain, response time, alerts, and monitoring. Six metrics, weighted by their importance for ongoing operations. No magic, no black box.
And the best part: every improvement is immediately visible. SSL renewed? Score goes up. Alert resolved? Score goes up. Hosting switched and response time halved? Score goes up.
Use the score as a compass for your weekly website maintenance. Your portfolio will thank you.
Start now: Create a free pingport account and see the health score for your first 5 websites. On the Paid plan (5 EUR/month + 0.15 EUR/website), you get the full portfolio overview with todos, alerts, and hosting cost tracking.