Website health check with a clear score, risk callouts, and fixes

Get Your Website Health Report in Seconds

Enter your website and email to receive a full report on uptime, latency, SSL status, risks, and recommended fixes, straight to your inbox.

Health Report Terms Explained

What each part of your website health report means and how the score is calculated.

Health score

A number from 0 to 100 that sums up how healthy your website is right now, based on its HTTP status, SSL certificate, and latency. Every site starts at 100; points are taken off for each risk found, and a few bonus points are added when everything is healthy.

How to calculateStart at 100 − 30 if SSL is invalid, or − 12 if it expires in under 30 days − 40 for a 5xx error, − 28 for 4xx, − 12 for 3xx − 25 if latency > 2000 ms, or − 12 if > 700 ms + 8 if HTTP 200, valid SSL and latency ≤ 700 ms Final score is kept between 0 and 100

ExampleA site returns HTTP 200, its SSL expires in 20 days, and latency is 850 ms. 100 − 12 (SSL renewal soon) − 12 (latency elevated) = 76.

Grade

A letter that turns the health score into a quick verdict.

Example90-100 = A, 80-89 = B, 70-79 = C, 60-69 = D, below 60 = F. The score of 76 above is a C.

Uptime

Whether the website was up and answering requests when we checked it. Over time, uptime is shown as a percentage of the time a site was available.

How to calculateUptime % = (Total time − Downtime) ÷ Total time × 100

ExampleA 30-day month has 43,200 minutes. If the site was down for 43 minutes: (43,200 − 43) ÷ 43,200 × 100 = 99.9% uptime.

Latency

How long the full request took to complete, in milliseconds (ms). The report flags latency over 700 ms as elevated and over 2000 ms as slow, because slow pages lose visitors and rank lower in search.

SSL status

Whether your SSL/TLS certificate is valid, trusted, and not expired, plus how many days are left before it expires. An invalid or expired certificate makes browsers show a "Not secure" warning.

SSL renewal window

The last 30 days before a certificate expires. The report warns you when your certificate enters this window so you can renew it before visitors see errors.

Risk callouts

The specific problems found during the check, each with a short explanation of the impact, such as an SSL certificate issue, a server-side error, a redirect issue, or slow page speed.

Server-side error (5xx)

A status code from 500 to 599, meaning the server failed to handle a valid request. Visitors see broken pages or failed requests. Common causes are application crashes, an overloaded server, or a down database.

Client or routing error (4xx)

A status code from 400 to 499, meaning the request could not be served as sent, for example 404 Not Found or 403 Forbidden. It usually points to a missing page, wrong URL, or access rule.

Redirect or routing issue (3xx)

A status code from 300 to 399, meaning the page sent the visitor somewhere else instead of loading directly. Redirects are normal (e.g. http to https), but long chains slow pages down and can hurt SEO.

Recommended fixes

Practical next steps included in the emailed report for each risk found, such as renewing a certificate, investigating server errors, or reducing response time.