Skip to content
PricingPlans from $15 a month billed yearly: ~20% less than monthly
MetricDeck
Log inStart free

Site health

Know a client's site is down before they do

Hourly uptime checks, SSL and domain expiry and page speed for every client's site, with an alert when one slips.

Start freeSee the live demo
  • Free for one client
  • No card
  • Read-only access
Trailhead Coffee· Site health · trailheadcoffee.example
Sample data

The numbers behind it

Mobile performance, last 2 runs (median)
47
Mobile performance, the month before (median of 27 runs)
79
Largest Contentful Paint (main content visible)
2.6s → 4.6s

Uptime

Checked every hour · 524 ms on average

24 hours
100%
24 checks
7 days
98.81%
168 checks, 2 down
30 days
99.72%
720 checks, 2 down

36 hours agoNow

Incidents

Runs of checks that were down, confirmed by a second try

  • Server error (HTTP 502)1 day ago · 2 checks · back within 2 hours

Certificate and domain

Checked each night on the website

  • SSL certificate9 days left
  • Domain registration188 days left

Page speed

Lighthouse performance, median of the last 2 runs, against the month before

mobile
47was 79
desktop
93was 93
Trailhead Coffee is one of the demo agency's made-up clients. The alerts are what MetricDeck's rules raise on its latest checks; the cards are the Site health tab's.
Short outages are the ones nobody sees. Trailhead Coffee's site answered “Server error (HTTP 502)” for 2 checks in a row 1 day ago, and was back before anyone opened a browser. It's on record, with its reason, for the next client call.

The monthly check, before and after

Making sure one client's site is up, secure and fast.

Time you get back

2 h 20 min

A month, if you look after 10 clients.

For one client

By hand15 min
With MetricDeck1 min

Our estimate for checking one site once a month by hand. MetricDeck checks uptime every hour and the rest every night, which nobody does by hand.

By hand

15 min
  1. 01Open the site and check the certificate's expiry date in the browser2 min
  2. 02Look up the domain's expiry with the registrar3 min
  3. 03Run PageSpeed Insights on mobile and desktop, and note the scores5 min
  4. 04Compare them with last month's2 min
  5. 05Read the uptime tool's log for outages3 min

With MetricDeck

1 min
  1. 01Nothing to run: you hear when the site goes down, a date gets close or speed fallsAutomatic
  2. 02Open Site health for the detail when you want it1 min

What you get

  • Uptime every hour

    Each failure is tried again 5 seconds later before the site is called down, so a blip never wakes you.

  • Incidents with a reason

    No DNS, a timeout, a refused connection, a certificate error, a server error or a 404, with when it began and how long it lasted.

  • Expiry dates, in time

    The certificate at 21 days and again at 7, the domain at 30 days and again at 7, with the registrar to renew it with.

  • Speed, mobile and desktop

    Lighthouse scores, loading times and real visitors' numbers, with an alert when a score falls out of good or is poor now.

  • More pages than the home page

    Watch the pages that matter: 2 on Starter, 5 on Pro and 10 on Agency, each with its own uptime and speed.

  • AI search readiness

    Whether ChatGPT, Claude and Perplexity can read each page, checked every night.

Why you can trust the alerts

  • A site is only called down after two failed checks in a row, 5 seconds apart.

  • A server that turns our checker away is running, so it counts as up and never alerts.

  • Speed alerts take two slow runs, never one, so Lighthouse's own wobble stays quiet.

  • Failures on Google's side, like a PageSpeed error, are never blamed on the site.

FAQ

Questions

How often is each site checked?
Uptime every hour. The certificate, the domain, page speed and AI search readiness with every full sync: each night, and whenever you press Sync now.
What counts as down?
A check that fails twice, 5 seconds apart: the address doesn't resolve, the server doesn't answer or refuses the connection, the certificate fails, or the page returns a server error or a 404. A server that answers but turns our checker away (401, 403 or 429) is running, so it counts as up and never alerts.
Page speed scores jump around. Won't that mean false alarms?
Lighthouse scores move 5 to 10 points between identical runs, so one slow run never alerts. MetricDeck compares the median of the last two runs with the month before, and only a fall of 15 points or more that leaves the good range (90 and up) counts. A score that's poor now (below 50) alerts on its own.
Where do the speed numbers come from?
Google's PageSpeed Insights, for mobile and desktop: the Lighthouse scores, loading times, and the real visitors' numbers from Chrome when Google has enough of them for the page.
Where does the domain's expiry date come from?
From RDAP, the domain registries' public record, looked up at most once a day. You hear at 30 days and again at 7, with the registrar to renew it with.
Which pages are watched?
The project's website, plus extra pages you add on its Site health tab: 2 on Starter, 5 on Pro and 10 on Agency. Each gets uptime and speed; the certificate and domain are checked on the website.

More of what MetricDeck does

Watch every client's site

Add a project with its website and the first checks start at once: uptime, certificate, domain, speed and AI search readiness. Free for one site.

Start freeSee the live demo

Free for one client · No card · Read-only access