Website speed monitoring that tells you what got slow.

A slow page costs you customers long before it goes down. Uptimia loads your site in a real browser from 171+ locations, watches its speed on every check, and alerts you the moment pages get slower than you allow.

Start free trial → View pricing
30-day free trial · no credit card Real Chrome, real page load GDPR-ready
Fastest interval
60s
Alert channels
12
Checkpoints
171+
Countries covered
70+

Slow check to alert: 31 minutes

A marketing tag ships at 09:04. Here is what every check after it recorded.

09:04 A new marketing tag shipsEvery check now records a slower LCP: 2.6 s → 3.4 s — no alert yet visitors: waiting
09:34 The budget window fills — 82% over9 of the last 11 checks breach your 2.5 s LCP budget visitors: waiting
09:35 Degraded — never DownThe alert names it: median 3.4 s vs 2.5 s budget → Slack, email visitors: waiting
10:12 Tag deferred — back under budgetMost checks recover and the incident closes on its own visitors: fast again
0downtime logged
Caught while it was only slow.10:12
A slowdown is invisible to uptime checks — the site stayed up all morning. The budget caught the creep at 82%, named the metric and the median, and never once called it Down.
median vs budget in the alertDegraded ≠ Downclosed on its ownLCP · CLS · FCP · TTFB — budget any vital
And without a budget? A page that takes twice as long still counts as up — uptime checks don't measure waiting. The slowdown ships in the morning, and by next week it's just how the site feels. the new normal

What website speed monitoring records

One real-Chrome load per check — load time, four lab web vitals, where the time goes, and any asset that failed to load.

Full page load timeOne real-Chrome load per check
Web vitalsLCP & CLS, plus FCP · TTFB, lab-graded
Own vs third-party timeYours or theirs — time split out
Page weight by typeImages vs JS vs CSS, in bytes
1 real-chrome trace per check — not an estimate
Requests & hostsEvery call, every domain contacted
Failing assetsImages, scripts and CSS that fail
Alert budgets are yours to set: LCP, FCP, CLS, TTFB or full page load over budget — or a script, image or stylesheet failing to load. your budgets

Inside a speed check

Real browser

Every asset timed in one load

A ping only tells you a server answered. Uptimia loads your whole page in real Chrome — every script, image and stylesheet — and times the complete load.

  • Full page load in real Chrome — waits for the load event, then a paint settle so late content still counts
  • Time split by resource type — HTML, CSS, scripts, images and the rest
  • Your code vs everyone else's — own-domain time separated from third-party
How page load is measured →
caldmont.com
every minute · 6 locations
A ping
server answered — all it can say
62 ms
Real Chrome — the whole page09:14
Waits for the load event, then a paint settle — late content still counts. Timed by resource type:
html62 ms
css140 ms
script1,240 ms
image410 ms
text90 ms
other88 ms
87 requestsload event + 600 ms settlefull load 3.2 s
Whose slowdown is it? Own-domain time is split from third-party — here 1.2 s of script traces back to 6 outside hosts. 6 hosts
Core Web Vitals

Core Web Vitals, before Google grades you

The two Core Web Vitals a lab load can measure — LCP and CLS — plus FCP and TTFB alongside them, read from the same Chrome trace, graded against Google's own thresholds, and charted over time so you see a metric drifting early.

  • Four lab vitals from one trace — no second engine, no external API call
  • Google's thresholds built in — each metric scored good, needs-improvement or poor
  • Per location or pooled — catch a regression the day it lands
One Chrome trace09:14
Recorded during the check you already run — all four vitals are read straight from it.
timeToFirstByte0.42 s
firstContentfulPaint1.61 s
largestContentfulPaint2.94 s
cumulativeLayoutShift0.06
loadEventEnd3.21 s
no second engineno external API
LCP
good ≤ 2.5 s
2.9 sneeds work
FCP
good ≤ 1.8 s
1.6 sgood
TTFB
good ≤ 0.8 s
0.42 sgood
CLS
good ≤ 0.10
0.06good
Graded per location or pooled — every vital is read from the trace of a check you already run, so a regression shows up the day it lands. 1 trace
Budget alerts

Degraded alerts when a metric breaks budget

Set a budget per metric — LCP, FCP, TTFB, CLS. When one stays over across the recent window, a single Degraded incident opens, naming the metric, its median versus budget, and how many checks breached.

  • One budget per web vital — pre-filled to Google's "good" thresholds, change any of them
  • Confirmed over a window, not one bad check — a short-lived blip won't page you
  • Marked Degraded, never Down — a slow page never dents your availability
How budget alerts work →
LCP
3.4 s vs budget 2.5 s
over
FCP
1.6 s vs budget 1.8 s
ok
TTFB
0.42 s vs budget 0.8 s
ok
CLS
0.06 vs budget 0.10
ok
82%of checks
over budget
27 of 33 · 30 min
Degraded — LCP over budget
Opened 09:35 for caldmont.com — one incident naming the metric, median vs budget and the breach rate. Availability untouched.
SlackEmailPagerDuty+ 9 more
A single slow check changes nothing. The window has to stay over budget to page you — and a slow page is Degraded, never Down. never Down
Dead element detection

Catch scripts, images or CSS failing silently

A page can look fine while a background script 404s. Uptimia classifies every request and alerts you when an asset keeps failing, so a dead script doesn't sit there for a week.

  • Every request classified — a 4xx, 5xx or dead connection is a failing asset
  • Alert on your terms — after a set number of failing checks in a row, for the types you watch
  • Ignore the noise you expect — glob out assets you already know are optional
Every request, classified09:14
caldmont.com — 87 requests this check. Any 4xx, 5xx or dead connection marks that asset as failing.
imagescriptcssother — off
85 requests — clean
2xx · connections fine
ok
gtm.js — HTTP 404
script · tagmanager.example.com
failing · 5 in a row
px.js — also failing
matches your ignore glob · cdn.ads.example.com/**
muted
The page still renders fine. Without every request classified, gtm.js fails silently — you hear it from monitoring, not from a customer. every request

How website speed monitoring works

Live in under a minute — nothing to install, every check runs in real Chrome on our network.

Step 120 s

Add your page

Paste the URL and choose locations — every monitor runs from at least six, so one slow network can't skew your numbers.

Page URL
https://caldmont.com
loaded in real Chrome from eu-fra · 1.79 s
Check frequency
Every 1 minute
Locations
6 minimum · add more from 171+
Step 220 s

Set your budgets

Each vital comes pre-filled to Google's "good" threshold — keep, tighten or turn any off, then pick who hears about a breach.

Web-vitals budgets · Google defaults
LCP 2.5 sFCP 1.8 sTTFB 0.8 sCLS 0.10
Reset to Google's thresholds any time
Alert via
Slack · Email · PagerDuty
CancelStart monitoring →
Step 3automatic

Alerts fire when the budget breaks

If a metric stays over budget, one Degraded incident opens and alerts your team — never marked Down.

#perf-alerts
Uptimia 09:35
⚠ Degraded — caldmont.com
LCP over budget3.4 s vs 2.5 s82% over
Also sent to EmailPagerDuty

Set a budget per vital.Get paged when it breaks.

Every load, every vital, every alert channel — free for 30 days, and none of it is a paid add-on.

Start your free 30-day trial →
30 days free no credit card cancel anytime

What is website speed monitoring?

Website speed monitoring is an automated service that repeatedly loads a web page in a real browser and measures how fast it loads for visitors — recording full page load time and Core Web Vitals such as LCP and CLS. When a metric drifts over your target, it alerts you, so slowdowns get fixed before they cost visitors or ranking.

On every check

How does website speed monitoring work?

Uptimia
real Chrome · 171+
loads once · records a trace
Your page
load + vitals

One trace per check yields the load time, all four lab vitals, and where every millisecond went — own-domain versus third-party.

Lab conditions

Lab metrics, measured — not guessed

Chrome trace
controlled load
parsed in the same run
LCP · FCP
TTFB · CLS

Lab vitals from a controlled load — the same conditions on every check, so a change in the number is a change in your page, not in someone's phone or wifi.

The thresholds

Web vitals thresholds

LCP and CLS are Core Web Vitals; FCP and TTFB are the supporting metrics Google publishes thresholds for. Google grades each one good, needs-improvement or poor — Uptimia scores every check against the same thresholds and pre-fills your budgets to the "good" line.

Guide: understanding Core Web Vitals →
MetricGoodNeeds improvementPoor
LCP≤ 2.5 s2.5 – 4.0 s> 4.0 s
FCP≤ 1.8 s1.8 – 3.0 s> 3.0 s
TTFB≤ 0.8 s0.8 – 1.8 s> 1.8 s
CLS≤ 0.100.10 – 0.25> 0.25

Website speed monitoring FAQ

01What is website speed monitoring?+
An automated service that loads your page in a real browser on a schedule and measures how fast it is for visitors — full page load time plus four lab web vitals — the Core Web Vitals LCP and CLS, alongside FCP and TTFB. When a metric goes over your target, Uptimia alerts you before it costs conversions or ranking.
02How does Uptimia measure my page speed?+
Every check loads your page in real, headless Chrome and records a DevTools trace — waiting for the load event plus a paint settle so late content counts. Load time and all four lab vitals come from that one trace: no second engine, no external API call.
03Which Core Web Vitals does Uptimia track?+
Google's Core Web Vitals are LCP, CLS and INP. Uptimia measures the two a lab load can measure — Largest Contentful Paint and Cumulative Layout Shift — and records First Contentful Paint and Time to First Byte beside them, all from one Chrome trace. INP needs a real person interacting, so no lab tool reports it; lab CLS covers the page-load window.
04How often does Uptimia check my page speed?+
As often as every minute on paid plans, and you choose the interval per monitor. Each check is a full real-browser page load — heavier than an uptime ping — so the fastest interval is one minute.
05How is this different from the free Page Speed Test?+
The free Page Speed Test is a one-time Lighthouse lab test from a single location — good for a quick score. Speed monitoring is continuous: scheduled loads from multiple locations, load time and vitals charted over time, alerts when something slips.
06When do I get a speed alert?+
When a metric stays over budget across the recent window — a single slow check won't page you. The incident is marked Degraded, never Down, and the alert names the metric, its median versus budget, and the share of checks over.
07Can it tell me if a third-party script is slowing me down?+
Yes. Every check separates own-domain from third-party time and records requests made and hosts contacted, charted over time — so you can see whether it's your code or an analytics tag, ad, font or chat widget.
08What happens if an image or script fails to load?+
Every request is classified; a 4xx, 5xx or dead connection is a failing asset. You're alerted after your chosen number of consecutive failing checks, for the asset types you watch — and known-optional assets can be ignored with glob patterns.
09Does a slow page hurt my uptime numbers?+
No. A budget breach or failing asset opens a Degraded incident — never counted as Down. Speed and uptime are tracked separately, so a slow afternoon doesn't blemish your uptime record.
10Is website speed monitoring free?+
It isn't part of the free plan, but the 30-day trial includes it in full — no credit card. Every paid plan includes it alongside uptime, SSL, transaction, DNS and heartbeat monitoring — never as a paid add-on.

Start monitoring your site speed today.

Paste a URL, set your budgets — be the first to know when your page starts to drag.

Monitor your page speed →
30-day free trial Real Chrome, real page load No credit card EU-hosted, GDPR-ready
Speed monitoring is part of every paid Uptimia plan, beside uptime, SSL and more.