Skip to content

Uptime monitoring

Uptime monitoring that catches a broken page, not just a down server

A server responding does not mean your site works. Sitewatch does everything an uptime monitor does — then keeps going: scripts, styles, images, third parties, SSL and your critical pages. When something breaks, you get one plain-English alert.

  • We open your site every 5 minutes and check every part of it loads
  • Catch a page that loads but has quietly stopped working — invisible to ping-based tools
  • Alerts across 6 channels that tell you what broke, not just that something did

01Why it's different

Same page. Two very different answers.

Server responds

Traditional uptime:
Detected
Sitewatch:
Detected

A script file goes missing — the page renders blank

Traditional uptime:
Reported as healthy
Sitewatch:
Flagged on the affected page

The stylesheet is missing — the page loads unstyled

Traditional uptime:
Reported as healthy
Sitewatch:
The right kind of file, checked every time

Images fail to load

Traditional uptime:
Not checked
Sitewatch:
Every image reference resolved

Third-party script host goes down

Traditional uptime:
Your origin is fine — nothing flagged
Sitewatch:
Vendor going healthy → down is alerted

API endpoint stops responding

Traditional uptime:
Pings the page, sees nothing wrong
Sitewatch:
Endpoints monitored separately

SSL certificate expires

Traditional uptime:
A basic reminder, if any
Sitewatch:
Warned 30 days early, urgent at 14

02The blind spots

Failures that happen while your uptime tool says OK.

Missing script file

JS-404

A script file is renamed or dropped during a deploy, and forms, navigation and checkout silently stop working.

UptimeServer responds — 100% up.
SitewatchFlags the failed script on a critical page within minutes.

Missing stylesheet

CSS-MIME

The stylesheet goes missing or arrives as the wrong kind of file, so the page loads as raw unstyled text.

UptimeLoads fast, reports healthy.
SitewatchChecks each stylesheet loads, and loads as a stylesheet.

Images disappear

IMG-CDN

An image host goes down and product photos and hero images vanish from the page.

UptimePage is "up" but looks abandoned.
SitewatchChecks every image on the page resolves.

Third-party outage

3P-DOWN

A vendor script's host has an outage, so its widget is missing from every page on the site.

UptimeYour origin is fine — nothing flagged.
SitewatchAlerts on a known vendor going from healthy to down.

Expired SSL

SSL-EXP

A certificate lapses and browsers start blocking the site with a full-page security warning.

UptimeA basic reminder, if any.
SitewatchWarns 30 days early and escalates to critical at 14.

Broken API

API-500

The homepage loads normally but a key endpoint behind it starts returning errors.

UptimePings the page — sees nothing wrong.
SitewatchMonitors the endpoint and flags it when it fails.

03Anatomy of a page

Every layer of your page, watched.

A page is far more than a server. Select any layer to see how it fails — and how Sitewatch catches it.

HTML

document

How it fails — The server hands back an error page or an empty shell instead of your real page.

How Sitewatch detects it — Confirms your critical pages come back as real pages with the content you expect.

CSS & styles

stylesheet

How it fails — A stylesheet goes missing or arrives as the wrong kind of file — the page renders completely unstyled.

How Sitewatch detects it — Checks that every stylesheet the page asks for loads, as a stylesheet.

Images & media

assets

How it fails — Images vanish from a broken path or a downed image host, and the layout falls apart.

How Sitewatch detects it — Resolves every image reference and flags the ones that fail.

JavaScript files

scripts

How it fails — A script file is renamed, missing or misconfigured, so the page loads blank or half-working.

How Sitewatch detects it — Confirms each script the page needs is there and usable — no test scripts to write.

Third-party scripts

vendors

How it fails — A chat, consent or analytics vendor has an outage and its script goes missing from every page.

How Sitewatch detects it — Watches known third-party resources and alerts when a working one goes down.

APIs

endpoints

How it fails — A key endpoint starts erroring or times out while the page itself still loads.

How Sitewatch detects it — Monitors configured API endpoints for status and response, separately from the page.

SSL & DNS

transport

How it fails — A certificate expires or an MX record changes, breaking secure loads or email.

How Sitewatch detects it — Tracks SSL and domain expiry with 30/14/7-day warnings, plus MX and CNAME record changes.

Critical pages

journeys

How it fails — Checkout, login or pricing goes down or errors while the homepage stays perfectly fine.

How Sitewatch detects it — Monitors the pages that matter most and alerts you the moment one breaks.

04The full list

Everything checked on a single page visit

Asset and resource failures

  • Script files that go missing after a deployment
  • Stylesheets served as the wrong kind of file, so browsers refuse them
  • Missing images, fonts, and media resources
  • Third-party scripts failing or timing out
  • Image and file hosts serving an error page while reporting themselves healthy

Navigation and routing failures

  • Redirects that send visitors in circles or bounce them too many times
  • Error pages that report themselves as healthy
  • Mixed content warnings blocking secure resources

Functional breakage

  • Forms that load but fail to submit
  • Checkout flows broken by missing dependencies
  • API endpoints returning errors behind a healthy homepage

05How it works

What happens on every check.

No test scripts. No credentials. Point Sitewatch at a URL and it does the rest — around the clock, from up to 2 regions on Pro.

Start free
  1. 1

    Sitewatch opens your site

    We open your site every 5 minutes to check it is reachable, and run a full check on a schedule — every 30 minutes on Free, down to every 5 on Pro.

  2. 2

    Fetches every asset

    The page HTML is parsed and every script, stylesheet, image and third-party resource is requested and checked.

  3. 3

    Verifies the page

    Confirms the page came back with real content, a valid certificate and working critical pages — not just that something answered.

  4. 4

    Finds a problem

    A 404 script, a downed vendor, an expiring certificate — anything that breaks the page for a real visitor.

  5. 5

    Opens an incident

    With the exact request, the affected page and a plain-English summary. Confirmed by 2-of-3 retries first, so transient blips never page you.

  6. 6

    Alerts you

    Email, Slack, webhook, PagerDuty, Opsgenie or SMS — before your customers notice.

06What you get

Outcomes, not a feature list.

Catch missing scripts and styles before customers do.

On every check, Sitewatch parses the page and verifies each script, stylesheet and image loads — the right file, the right content type, no 404. A blank page becomes an alert, not a customer complaint.

$ sitewatch check yoursite.com
html 200 · rendered
styles 4/4 loaded
images 28/28 loaded
scripts 3/4 — app.2f9c.js 404
✕ incident opened · page renders blank

Know immediately when a deploy breaks production.

Add a deploy hook and every release triggers a full check. Sitewatch compares against the last good version and flags a broken deploy — often before the first customer even lands on the page.

▸ deploy main@7c1e triggered check
homepage · pricing · docs
/checkout — stale bundle referenced
✕ deploy flagged · rollback suggested

Yes — the fundamental uptime part too.

5-minute pings

Fast availability checks on every plan that catch a hard outage the moment it happens.

Uptime percentage

Rolling uptime % per site and page, tracked over configurable windows.

Uptime history

A clear timeline of outages and recoveries you can share with clients on a status page.

Complementary

Runs alongside your existing tool — Sitewatch extends uptime monitoring, it does not require replacing it.

Every page

Not just the homepage — all your critical pages are checked.

2 regions

Regional checks on Pro catch failures that only appear far from home.

2-of-3

Retry confirmation before an alert fires, so blips never page you.

Your uptime tool says everything's fine. Is it?

Start with one site, free forever. No credit card required.

08Questions

Uptime monitoring questions, answered.