Skip to content

Asset monitoring

The page loads. Half of it never arrives.

A missing script quietly kills your checkout. A missing stylesheet makes your site look like it is from 1998. Your server answers normally the entire time, so every uptime tool reports you as healthy. Sitewatch checks every script, stylesheet and image your page needs, and alerts you before your customers notice.

  • Detect scripts and stylesheets that break after a deployment
  • Catch missing images that quietly erode trust and credibility
  • Spot CDN failures and third-party script outages
Catch broken assets nowSee pricing

Free scan

Find broken assets on your site right now

Enter any URL. We check every image, script and stylesheet the page needs and show you which ones are missing or silently failing. Free, no signup.

02The gap in your monitoring

Uptime tools miss the pages that load but don't work.

The page loads

Uptime tools:
Detected
Sitewatch:
Detected

A script goes missing — buttons stop working

Uptime tools:
Server answers, so it looks fine
Sitewatch:
Every script checked, by name

A stylesheet goes missing — the page looks broken

Uptime tools:
Not checked
Sitewatch:
Reported with the exact file

The CDN serves an error page instead of your file

Uptime tools:
Looks fine from a ping
Sitewatch:
Caught by checking the file type

A payment or chat vendor stops loading

Uptime tools:
Users discover it first
Sitewatch:
Every third-party script verified

Product images disappear

Uptime tools:
Not monitored
Sitewatch:
Every image resolved on each check

03Why it matters

Your site is "up" but broken. That is the expensive kind of failure.

Checkout silently stops working

JS-GONE

A missing script breaks form submissions, shopping carts and checkout flows. Customers click, nothing happens, and they leave.

UptimeServer responds — 100% up.
SitewatchNames the missing script and the page it breaks.

The page loses its design

CSS-GONE

A stylesheet goes missing or arrives as the wrong kind of file, and visitors stare at raw unformatted text.

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

Images turn into placeholders

IMG-GONE

Missing product photos, broken hero banners and placeholder icons destroy credibility. Visitors who see them rarely come back.

UptimePage is "up" but looks abandoned.
SitewatchResolves every image the page references.

The CDN sends an error page

CDN-ERR

Your CDN returns an error page where your script should be — and reports it as a success, so the browser refuses to run it.

UptimeA response came back, so it looks fine.
SitewatchChecks each file is the kind of file it claims to be.

A vendor quietly disappears

3P-DOWN

Payment scripts, analytics tags and chat widgets vanish or start erroring. Your site still loads, but key features stop working.

UptimeYour own server is fine — nothing flagged.
SitewatchVerifies every third-party script the page loads.

Ad spend lands on a broken page

SEO-LOSS

Search engines and ad platforms both penalise pages with missing resources. Every broken landing page is budget spent on a bad first impression.

UptimeReports the page as healthy.
SitewatchFlags broken landing pages before the campaign runs.

04What we check

Every file your page depends on.

A modern page pulls in dozens of separate files. Select any one to see how it fails — and how Sitewatch catches it.

Scripts

behaviour

How it fails — A script is renamed or dropped during a deploy, so forms, menus and checkout silently do nothing.

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

Stylesheets

appearance

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

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

Images & media

content

How it fails — Product photos and hero images vanish because a path broke or the image host went down.

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

Fonts

typography

How it fails — A web font fails to load and the page falls back to a default typeface that breaks your layout.

How Sitewatch detects it — Checks font files load alongside every other file the page requests.

Third-party scripts

vendors

How it fails — A chat, consent, payment 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.

The CDN

delivery

How it fails — The CDN serves a cached error page in place of your file, while reporting the request as successful.

How Sitewatch detects it — Checks the response is the kind of file expected, not just that something came back.

05The full list

Every file referenced by your page, verified

Availability

  • Scripts and stylesheets that can no longer be found
  • Server errors returned for files the page needs
  • Missing images, icons and media
  • Third-party scripts returning errors

Delivery and file type

  • Scripts served as web pages, which browsers then refuse to run
  • Stylesheets delivered as the wrong kind of file
  • CDN nodes serving error pages in place of your files
  • Files redirecting to unexpected URLs or error pages

06How 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 page

    We request the page and work out every script, stylesheet, image and font it references.

  2. 2

    Checks every file

    Each one is requested to confirm it exists and arrives as the right kind of file. A file that comes back as an error page is caught here.

  3. 3

    Finds a broken file

    A script that moved in a deploy, an image host that went down, a vendor that stopped responding.

  4. 4

    Confirms before it alerts

    The failure has to repeat 2 out of 3 times, so a momentary glitch never creates an incident.

  5. 5

    Alerts you with the evidence

    Across your configured channels, naming the exact file, what went wrong and which page is affected.

07What you get

Outcomes, not a feature list.

Catch a broken deploy before the first customer does.

Renamed bundles are the single most common way a release breaks production. Sitewatch verifies every file the page needs on every check, so a missing script becomes an alert in minutes instead of a support ticket on Monday.

$ sitewatch check yoursite.com
✓ styles 4/4 loaded
✓ images 28/28 loaded
✓ fonts 2/2 loaded
✕ scripts 3/4 — main.a4f2c.js missing
✕ incident opened · checkout button dead

Know when a vendor breaks your site for you.

Your payment provider, chat widget and analytics tag all run on somebody else's infrastructure. When one of them goes down, your own servers stay perfectly healthy — and your checkout still stops working.

▸ third-party check · yoursite.com
✓ analytics vendor responding
✓ consent banner responding
✕ payment widget host unreachable
✕ vendor outage · payments unavailable

Every file

Scripts, styles, images and fonts — checked on each visit.

2-of-3

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

5–30 min

Check intervals, depending on your plan.

How much revenue are broken assets costing you right now?

Find out in 2 minutes. Free plan, no credit card required.

Check your site free See pricing

08Questions

Broken asset questions, answered.