UpturaBeta
Free performance tool

Free Core Web Vitals Test

Check any page’s Core Web Vitals in seconds — mobile & desktop score plus LCP, CLS, and more, straight from Google PageSpeed Insights. Then monitor them for free as your site changes.

Free · no sign-up · mobile & desktop scores straight from Google PageSpeed Insights.

What you get

Every Core Web Vitals metric, explained

Enter a URL and Uptura measures it with Google PageSpeed Insights, then reports the six metrics that decide your score — for both mobile and desktop.

  • Largest Contentful Paint (LCP)

    Loading

    How long until the biggest element in view — usually the hero image or headline — has rendered. Google wants this under 2.5s. It's the metric most sites fail.

  • Cumulative Layout Shift (CLS)

    Stability

    How much the page jumps around as it loads — text reflowing, buttons moving under a tapping finger. A good score is 0.1 or lower.

  • Total Blocking Time (TBT)

    Interactivity

    How long the main thread is blocked by JavaScript while the page loads — the lab stand-in for INP (Interaction to Next Paint), which needs a real user to measure. Aim for under 200ms.

  • First Contentful Paint (FCP)

    First paint

    When the first text or image appears — the moment a visitor sees the page is actually loading. Good is under 1.8s.

  • Speed Index (SI)

    Visual load

    How quickly the page's content visibly populates. A lower Speed Index means the page feels fast, not just technically loaded.

  • Time to First Byte (TTFB)

    Server

    How long your server takes to send the first byte of the response. Slow TTFB (over 800ms) drags every other metric down with it.

Why it matters

Why Core Web Vitals are worth testing

Core Web Vitals sit at the intersection of SEO and revenue — and a single deploy can quietly move them. Here's why a one-time test is only half the job.

  • Core Web Vitals are a Google ranking factor

    Page experience is part of how Google ranks pages. Two pages with similar content don't rank equally if one is slow and janky — Core Web Vitals are how Google measures that difference.

  • Slow pages lose visitors before they convert

    Every extra second of load time drops conversions and pushes up bounce rate. A visitor who leaves during a 5-second LCP never sees your offer — the speed problem is a revenue problem.

  • Scores drift as your site changes

    A new hero image, a marketing tag, an unoptimised font, a plugin update — any deploy can quietly push a passing page into the red. A one-time test only tells you about today.

How to fix it

How to improve your Core Web Vitals

Once the test shows which metric is in the red, here's where to start. Fixing the worst offender usually lifts the whole score.

  • LCP

    Fix a slow LCP

    Compress and correctly size your hero image, serve it in a modern format (WebP/AVIF), preload it, and cut render-blocking CSS. A fast server (low TTFB) and a CDN help the most here.

  • CLS

    Stop layout shift

    Set explicit width and height on images and embeds, reserve space for ads and banners, and avoid injecting content above what's already on screen. Preload fonts to stop text reflow.

  • TBT / INP

    Reduce blocking JavaScript

    Ship less JavaScript, defer or lazy-load what isn't needed for first paint, break up long tasks, and remove unused third-party scripts. This is what makes a page feel responsive.

  • TTFB

    Speed up your server

    Add caching, use a CDN, and cut slow database queries or heavy server rendering. TTFB is the foundation — every millisecond here is paid back across every other metric.

From test to monitor

Turn a one-time test into continuous monitoring

The test tells you where a page stands today. Uptura's free Core Web Vitals monitoring re-tests your pages on a schedule and alerts you the moment a metric regresses.

  1. 1

    Add your pages

    Point Uptura at the URLs you care about. Free during our public beta — no credit card.

  2. 2

    We test them on a schedule

    Uptura runs the same PageSpeed Insights measurement automatically — mobile and desktop — and tracks every metric over time, so you see the trend, not just a single snapshot.

  3. 3

    You get alerted when a metric regresses

    When a deploy pushes LCP, CLS, or TBT into a worse band, Uptura emails you (and Slack) with exactly what changed — before it costs you rankings or conversions.

Start monitoring free

Free during our public beta, no credit card required. Prefer to read more first? See how Core Web Vitals monitoring works.

The guide

Core Web Vitals, explained properly

What changed when INP replaced FID, why two tools show different numbers, whether any of it moves your rankings — and how to actually pass the assessment.

FID is gone — INP is the metric that matters now

If you last brushed up on Core Web Vitals a couple of years ago, one of the three metrics you memorised no longer exists. In March 2024, Google retired First Input Delay (FID) and replaced it with Interaction to Next Paint (INP). If you've searched "core web vitals INP replaces FID" and come away more confused than before, here's the plain version.

FID only ever measured the delay before the browser started responding to your very first tap or click. It was a low bar, and nearly every site cleared it — which made it close to useless. INP is stricter and a lot fairer: it looks at how responsive interactions are across the whole visit, not just the first one, and reports something near the worst lag a real user hit. A page can no longer coast on a good first impression.

The number to remember is the INP threshold: an INP of 200ms (200 milliseconds) or less is "good," up to 500ms is "needs improvement," and anything slower is poor. If your site felt fine under FID but suddenly looks worse in reports, this switch is almost always why — nothing broke, the ruler just got more honest.

Lab data vs field data — why two tests disagree

Run this tool, then open the same page's report in Google Search Console, and you might see two different stories. That's not a bug — the two are measuring in completely different ways, and knowing which is which saves a lot of head-scratching.

The test above is lab data: one controlled measurement, from one location, on a simulated device, right now. It's ideal for debugging because it's instant and repeatable. Search Console shows field data — real Core Web Vitals collected from actual Chrome users over the trailing 28 days. That second set is the data Google actually ranks on.

The practical upshot: use a lab test like this one to find and fix problems fast, because you get an answer in seconds instead of waiting weeks for the field data to update. Just remember INP can't truly be measured in a lab — it needs a real person clicking things — so lab tools report Total Blocking Time as its stand-in. Bring TBT down and your real-world INP almost always follows. And if you've ever wondered whether Google PageSpeed is accurate, this is the answer: it is — a lab score just measures something different from the field data Google ranks on.

Do Core Web Vitals actually affect SEO?

So does Core Web Vitals affect SEO? The honest answer is yes — but they're a tiebreaker, not a magic wand. They're a confirmed Google ranking signal, which means page speed is a ranking factor, part of the page-experience assessment. Relevance and content quality still do the heavy lifting, though: a blazing-fast page about the wrong thing won't outrank a slower page that genuinely answers the query.

Where speed decides the race is between pages that are otherwise close. When two results are similarly relevant, the faster, more stable one gets the edge — and on mobile, where connections are flaky and patience is thin, that edge is bigger. There's also a knock-on effect people forget: fast pages keep visitors from bouncing straight back to the search results, and they convert better once they land. So even if you set rankings aside entirely, the vitals still pay for themselves.

How to pass the Core Web Vitals assessment

"Passing" has a precise meaning, and it trips people up. All three core metrics — LCP, INP, and CLS — have to sit in the "good" band for the 75th percentile of your real visitors over 28 days. Not your best visitors, not your fastest test run: three out of every four real page loads have to be good. That bottom quarter — slower phones, worse connections — is usually where a failing assessment is hiding.

If the test above came back with a metric in the red, here's a Core Web Vitals strategy that actually holds up rather than a list of everything you could theoretically do:

  • Fix the worst metric first one red metric fails the whole assessment, so there's no payoff in polishing a green one. Find the red, start there, ignore the rest until it's fixed.
  • Test the device your visitors actually use your laptop on office wifi is not the 75th percentile. Check a throttled mobile profile — that's far closer to the person whose experience decides your score.
  • Give the fix time to register field data moves on a 28-day rolling window, so a fix you ship today won't show in Search Console for weeks. Confirm it in a lab test straight away, then wait for the field to catch up.
  • Then hold the line passing once is easy to lose. A new hero image, a marketing tag, or an unoptimised font in the next deploy can quietly drop you back into the red without anyone noticing.

One test today, or the whole trend over time

The tool at the top of this page is built for the first job: paste a URL, get your LCP, CLS, TBT and the rest in seconds, and know exactly which metric to fix. The numbers match what Google's PageSpeed Insights would give you, because it's the same engine underneath — no sign-up, test as many pages as you like.

But a single score is a photo, and Core Web Vitals are a movie. They drift every time you deploy — a heavier image here, a new third-party script there — and the page that passed last month can slip without anyone noticing until rankings dip. That's the gap Uptura fills: it runs this same test on a schedule, charts every metric over time, and alerts you the moment one crosses into a worse band. You find out from us, not from your analytics three weeks later.

FAQ

Core Web Vitals, answered

  • How do I check my Core Web Vitals?

    Enter your URL above and this free tool measures it with Google's PageSpeed Insights — the same engine behind pagespeed.web.dev — and reports your mobile and desktop scores plus LCP, CLS, TBT, FCP, Speed Index, and TTFB. Because it uses Google's own API, the numbers match what you'd see in Search Console and PageSpeed Insights exactly.

  • What is a good Core Web Vitals score?

    Google's thresholds are: Largest Contentful Paint (LCP) under 2.5s, Cumulative Layout Shift (CLS) 0.1 or lower, and Interaction to Next Paint (INP) under 200ms — proxied in the lab by Total Blocking Time under 200ms. A page passes when all three core metrics are in the "good" band. The overall 0–100 performance score is Lighthouse's weighted blend of these metrics; 90+ is good, 50–89 needs work, below 50 is poor.

  • What is Largest Contentful Paint (LCP)?

    LCP measures how long it takes for the largest element in the viewport — typically the hero image, a large banner, or a block of headline text — to finish rendering. It's the clearest signal of how fast a page feels to load. Google considers an LCP under 2.5 seconds "good." It's the metric most sites fail, usually because of an unoptimised hero image or a slow server.

  • What's the difference between First Contentful Paint and Largest Contentful Paint?

    First Contentful Paint (FCP) is when the first piece of content — any text or image — appears, telling the visitor the page is loading. Largest Contentful Paint (LCP) is when the biggest, most meaningful element has rendered, telling them the page is actually usable. FCP fires first; LCP is the one Google ranks on.

  • How do I improve my Core Web Vitals?

    It depends which metric is failing. For LCP: optimise and preload your hero image, use a CDN, and cut render-blocking resources. For CLS: set explicit image dimensions and reserve space for ads and fonts. For TBT/INP: ship less JavaScript, defer non-critical scripts, and break up long tasks. For TTFB: add caching and speed up your server. Run the test above to see which metric to start with.

  • Why is my website slow?

    The most common causes are large unoptimised images, too much JavaScript blocking the main thread, a slow server or hosting (high TTFB), render-blocking CSS and fonts, and heavy third-party scripts like chat widgets and analytics. The test above pinpoints which of these is hurting you by showing exactly which metric is in the red.

  • Is this Core Web Vitals test free?

    Yes — completely free, no sign-up. Test as many pages as you like. If you'd rather not re-test by hand after every change, you can set up free automated Core Web Vitals monitoring during our public beta, which tracks your scores over time and alerts you when one regresses.

  • Can I monitor Core Web Vitals over time and get alerts?

    Yes. A one-time test tells you where a page stands today, but scores drift with every deploy. Add your pages to Uptura and it runs this same measurement on a schedule, charts each metric over time, and alerts you by email and Slack the moment a metric regresses into a worse band — free during our public beta.

Catch a Core Web Vitals regression before Google does

Add your pages and let Uptura test them on a schedule — mobile and desktop — and alert you the moment a metric slips. Free during our public beta, no credit card required.

Free during beta · no credit card required