Monitoring
Status Pages
Pricing
Last updated: January 28, 2026
Google’s Core Web Vitals (CWV) are a set of user‑experience metrics designed to quantify how real users experience the web. They are not abstract SEO scores, they are signals derived from how pages load, respond, and remain visually stable for users.
This guide is written as a practical, engineering‑led reference. Rather than focusing only on definitions or scores, it explains:
Throughout, the emphasis is on diagnosis and action, not just measurement.
Core Web Vitals are a subset of Google’s Page Experience signals. They focus on three aspects of user experience:
Google evaluates these using aggregated real‑user data over time. Individual page loads may vary, but Core Web Vitals reflect the overall experience users have in the real world.
What it measures: Loading experience
LCP measures how long it takes for the largest visible element (such as a hero image or main heading) to render within the viewport.
A slow LCP usually indicates server response delays, large media assets, or render‑blocking resources.
What it measures: Responsiveness
INP measures how quickly a page responds to user interactions, such as clicks or taps. It replaced First Input Delay (FID) as Google’s primary responsiveness metric.
Poor INP scores are commonly caused by heavy JavaScript execution or long tasks blocking the main thread.
What it measures: Visual stability
CLS measures how much the layout shifts unexpectedly during page load or interaction.
High CLS often results from images, fonts, or ads loading without reserved space.
Pages that load quickly, respond immediately, and remain visually stable are easier and more pleasant to use. Poor Core Web Vitals often correlate with frustration, misclicks, and abandonment.
Core Web Vitals are part of Google’s Page Experience signals. While they are not the sole ranking factor, consistently poor CWV performance can limit a page’s ability to compete in search results.
Performance issues frequently impact conversion rates, engagement, and retention. Improving Core Web Vitals often delivers benefits beyond SEO alone.
Core Web Vitals scores indicate how a page performed for users. They do not explain why it performed that way.
CWV scores are outcome metrics. They are useful for benchmarking and prioritisation, but meaningful improvements require diagnostic insight into what happens during page load and execution. This is where page speed monitoring and request waterfalls become essential.
Page speed monitoring provides repeatable tests that show how a page loads under controlled conditions. While page speed metrics are not identical to Core Web Vitals, they strongly correlate with them and are one of the most practical ways to identify performance bottlenecks.
For most teams, page speed monitoring is the fastest way to:
A page speed waterfall visualises every request made during page load and how long each takes. This turns performance issues into concrete, actionable problems.
A waterfall helps identify:
If the largest visual element appears late in the waterfall, it often explains a poor LCP score.
While INP is influenced by real user interactions, waterfalls often reveal contributing factors such as:
These patterns frequently correlate with responsiveness problems.
Waterfalls highlight resources that load late and cause layout shifts, including:
Once you understand where time is being spent during page load, the next step is deciding what to change. The table below maps each Core Web Vitals metric to common symptoms, likely causes, and the areas teams typically optimise.
| CWV metric | What you’ll see | Common causes | Where to look in the waterfall | Typical fixes |
|---|---|---|---|---|
| LCP | Main content appears late | Slow TTFB, large images, blocking CSS | Long initial request, late-loading hero asset | Image optimisation, caching, CSS prioritisation |
| INP | Page feels sluggish to interact | Heavy JS, long tasks, third-party scripts | Large JS bundles, long execution gaps | Code splitting, deferring scripts, reducing JS |
| CLS | Page jumps during load | Late fonts, ads, injected content | Resources loading after render | Reserve space, fix font loading, stabilise embeds |
This approach focuses on continuous improvement rather than chasing isolated metrics.
Many of these issues are visible immediately in a request waterfall.
No. Core Web Vitals are measured per UR. Different pages can have very different scores depending on content and complexity.
Yes. Google primarily evaluates Core Web Vitals using mobile user data, reflecting real‑world usage patterns.
Yes. Scores can change due to deployments, traffic patterns, infrastructure changes, or user behaviour.
No. Performance is an ongoing concern. Regular monitoring helps prevent regressions and maintain a good user experience.
Page speed monitoring tools, such as StatusCake, provide visibility into load behaviour and performance trends. Waterfall views make bottlenecks explicit, helping teams understand where changes will have the greatest impact on user experience.
The value lies not in the score itself, but in the ability to diagnose and improve performance over time.
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
