Core Web Vitals monitoring that catches a slowdown early.
Relvato measures your Core Web Vitals — LCP, INP and CLS — plus FCP, TBT and TTFB, in a controlled real-browser run with PageSpeed-comparable throttling on your key pages. It grades them against Google’s thresholds, shows you why they’re slow, and alerts you when a change pushes them into the red.
- ✓LCP, INP and CLS — plus FCP, TBT and TTFB — graded against Google’s thresholds
- ✓PageSpeed-comparable throttling on mobile: Slow 4G + 4× CPU, so the numbers match what Google sees
- ✓The LCP breakdown — TTFB, load delay, load time and render delay — and the exact element that’s slow
- ✓Unused JavaScript & CSS, with the real transfer-byte savings per file
- ✓The render-blocking critical path and how long it delays first paint
- ✓What’s freezing the main thread — blocking scripts named by vendor (Klaviyo, Meta Pixel…)
- ✓Layout-shift culprits, oversized or late-loaded images, DOM size and third-party page weight
- ✓Every key page, on desktop and mobile
Core Web Vitals are a Google ranking factor, and they slip quietly — a new hero image, a third-party script, a theme update. A throttled lab run gives you a stable, PageSpeed-comparable number on every change — and, unlike a once-a-month audit, it tells you exactly what to fix: the slow LCP element, the unused JavaScript, the render-blocking request, the script freezing the main thread.
On WordPress, when the largest thing on a page is a background image set in CSS — which the browser only finds after loading the stylesheets — Relvato suggests preloading it, and you apply it with one click in WordPress → Relvato: the plugin adds a preload hint for that image to the page's head and clears the page cache. It's undoable, and the monitor re-runs so you see the difference.
Lab data or real-user data — which should you trust? Our guide compares Core Web Vitals vs RUM: what each measures, when to use it, and which one Google actually ranks on.
- Loads your key pages in a real headless Chrome — with PageSpeed-comparable throttling (Slow 4G + 4× CPU) on mobile — and measures LCP, INP, CLS, FCP, TBT and TTFB.
- Grades each against Google’s thresholds on desktop and mobile, and breaks LCP into its phases so you can tell a slow server from render-blocking code.
- Pinpoints the cause — the slow element, unused JS/CSS, the render-blocking chain, main-thread-blocking scripts by vendor, heavy images and DOM size — and re-runs on every change.
Lab or real-user data?
This is the lab (synthetic) run — a stable, repeatable measurement. Pair it with Real-user Web Vitals (RUM) for field data from actual visitors.
Do I need a plugin?
No — the lab run works on any site with a verified domain.
Do the numbers match PageSpeed Insights?
They’re in the same ballpark — we apply PageSpeed-comparable throttling (Slow 4G + 4× CPU) on mobile. PageSpeed simulates that throttling while we apply it, so expect them to agree directionally, not to the last decimal.
Put this monitor on autopilot.
Free forever on one site — 100 runs a month, started by you or weekly, no card. Pro re-runs your monitors by itself after every update.