GMCSuspension
Core Web Vitals

Monitor Your Core Web Vitals Every Week

LCP, CLS, TBT, and FCP checked against Google's thresholds every Monday. Failing metrics come with specific AI-written fix suggestions. No PageSpeed logins required.

Why Core Web Vitals matter for rankings

Google officially made Core Web Vitals a ranking signal in May 2021. Sites that pass all three core metrics can expect a modest boost over otherwise equal competitors. More importantly, sites that fail, particularly on mobile, face a visible disadvantage in competitive search results.

Beyond rankings, the metrics measure real user experience. A site with a 5-second LCP means users sit watching a mostly blank page for 5 seconds before the main content appears. Many of them leave before it finishes loading. A high CLS means buttons and links jump around as the page loads, causing accidental clicks and frustration. These are problems that cost you both rankings and conversions.

The challenge is that CWV scores drift. A plugin update adds a third-party script that slows your TBT. An image gets uploaded without compression and LCP climbs. Without weekly monitoring, these problems silently accumulate over months until you notice a traffic drop.

The four metrics, explained

LCP — Largest Contentful Paint

Good: <2.5s | Needs work: 2.5–4s | Poor: >4s

How long it takes for the largest visible element (usually a hero image or heading) to appear on screen. The single most noticeable speed metric for users. Slow LCP means users see a blank or partially loaded page for too long.

CLS — Cumulative Layout Shift

Good: <0.1 | Needs work: 0.1–0.25 | Poor: >0.25

Measures how much page elements move unexpectedly while loading. A score above 0.1 means visible content shifts, which causes users to click the wrong thing or lose their reading position. Common cause: images loaded without defined dimensions.

TBT — Total Blocking Time

Good: <200ms | Needs work: 200–600ms | Poor: >600ms

The total time the main browser thread is blocked and unable to respond to user input while the page loads. High TBT makes a page feel frozen or unresponsive. Usually caused by large JavaScript bundles or third-party scripts.

FCP — First Contentful Paint

Good: <1.8s | Needs work: 1.8–3s | Poor: >3s

How long until the browser shows the first piece of content, text or an image. FCP is the user's first feedback that the page is loading at all. A fast FCP reduces perceived wait time even if LCP is slower.

What happens when a metric fails

When your weekly report flags a failing metric, the AI action plan generates specific instructions for that metric. Here's an example of what the output looks like for an LCP failure:

AI ACTION PLAN — LCP FAILURE
Your LCP score this week is 3.8s (needs improvement). Your homepage hero image (hero-banner.jpg, 2.4MB) is loading as a standard img element with no preload hint and no compression. To fix this:

1. Convert hero-banner.jpg to WebP format. Target file size under 200KB. You can use Squoosh (squoosh.app) in the browser, or the cwebp command-line tool.

2. Add a preload link in your HTML head: <link rel="preload" as="image" href="hero-banner.webp">

3. If your hero image is not visible above the fold on mobile, remove the preload and add loading="lazy" instead.

Expected improvement: LCP should drop to approximately 1.4–2.1s after these changes, putting you in the "Good" range.

The output varies based on what the scan detects. If your LCP is slow because of a render-blocking stylesheet rather than an image, the suggestion will address that instead.

How to improve each metric

These are the most common fixes for each CWV metric. The AI action plan will identify which ones apply to your site specifically:

The good news: fixing any one of these metrics rarely requires a developer. Most improvements come down to image optimization and a few lines of HTML or configuration changes in your CMS.

Frequently asked questions

Is this the same as running PageSpeed Insights myself?

Similar but not the same. PageSpeed Insights gives you a one-time snapshot with raw data. SEO Monitor gives you weekly tracking so you can see whether metrics are improving or declining after changes you make. It also connects your CWV data to your keyword rankings so you can see whether speed improvements are correlating with ranking gains.

Do you test desktop, mobile, or both?

Both. The email report shows separate scores for desktop and mobile. Google's CWV ranking signal is based on field data from real users and weighted toward mobile, so mobile scores matter most for SEO purposes.

My site uses Shopify or WordPress. Do those platforms score well?

It depends on your theme and installed apps or plugins. Default Shopify themes generally score in the "needs improvement" range. WordPress performance varies widely, from poor with heavy page builders to excellent with optimized themes and caching plugins. The report tells you exactly which metrics you're failing and why.

What if my CWV scores are already good?

The report still monitors them weekly. CWV scores can degrade after theme updates, plugin additions, or new content with unoptimized images. Weekly monitoring catches regressions the week they happen, not after rankings have already dropped.

Start monitoring your Core Web Vitals today

Register your site and your first CWV scan runs within 24 hours. Every Monday after that, you'll know exactly where your site stands against Google's thresholds, with specific fixes if anything is failing.

Register Your Site, From $9/Month