Skip to content

Core Web Vitals history:When did your Core Web Vitals change?

See 40 weeks of real-user LCP, INP and CLS for your site, week by week, and spot the release that broke it and the one that fixed it.

Device
Scope
  • Free, no account
  • Results in seconds
  • Any site in the Chrome UX Report

Example resultWhole site · https://example-shop.hr

latest: good

40 weekly windows from 2025-11-16 to 2026-09-12, phone. Each point is the 75th percentile of a 28-day window.

Largest Contentful PaintLCP2.1 sgood−2.1 s over 40 weeks
2.5 s4.0 sDec 25Feb 26Apr 26Jun 26Aug 2613 Dec: 4.3 s (poor)20 Dec: 4.2 s (poor)27 Dec: 4.3 s (poor)3 Jan: 4.2 s (poor)10 Jan: 4.3 s (poor)17 Jan: 4.2 s (poor)24 Jan: 4.1 s (poor)31 Jan: 4.1 s (poor)7 Feb: 4.0 s (needs improvement)14 Feb: 4.0 s (poor)21 Feb: 3.9 s (needs improvement)28 Feb: 3.8 s (needs improvement)7 Mar: 3.8 s (needs improvement)14 Mar: 3.8 s (needs improvement)21 Mar: 3.6 s (needs improvement)28 Mar: 3.5 s (needs improvement)4 Apr: 3.5 s (needs improvement)11 Apr: 3.5 s (needs improvement)18 Apr: 3.4 s (needs improvement)25 Apr: 3.2 s (needs improvement)2 May: 3.3 s (needs improvement)9 May: 3.0 s (needs improvement)16 May: 3.1 s (needs improvement)23 May: 2.8 s (needs improvement)30 May: 2.7 s (needs improvement)6 Jun: 2.6 s (needs improvement)13 Jun: 2.6 s (needs improvement)20 Jun: 2.7 s (needs improvement)27 Jun: 2.4 s (good)4 Jul: 2.5 s (good)11 Jul: 2.4 s (good)18 Jul: 2.3 s (good)25 Jul: 2.3 s (good)1 Aug: 2.1 s (good)8 Aug: 2.1 s (good)15 Aug: 2.1 s (good)22 Aug: 2.2 s (good)29 Aug: 2.1 s (good)5 Sept: 2.1 s (good)12 Sept: 2.1 s (good)2.1 s

Latest window: 82% of visits good, 13% needs improvement, 5% poor.

Interaction to Next PaintINP179 msgood−71 ms over 40 weeks
200 ms500 msDec 25Feb 26Apr 26Jun 26Aug 2613 Dec: 250 ms (needs improvement)20 Dec: 248 ms (needs improvement)27 Dec: 246 ms (needs improvement)3 Jan: 267 ms (needs improvement)10 Jan: 247 ms (needs improvement)17 Jan: 249 ms (needs improvement)24 Jan: 252 ms (needs improvement)31 Jan: 264 ms (needs improvement)7 Feb: 238 ms (needs improvement)14 Feb: 247 ms (needs improvement)21 Feb: 248 ms (needs improvement)28 Feb: 255 ms (needs improvement)7 Mar: 250 ms (needs improvement)14 Mar: 248 ms (needs improvement)21 Mar: 228 ms (needs improvement)28 Mar: 228 ms (needs improvement)4 Apr: 223 ms (needs improvement)11 Apr: 236 ms (needs improvement)18 Apr: 234 ms (needs improvement)25 Apr: 206 ms (needs improvement)2 May: 203 ms (needs improvement)9 May: 202 ms (needs improvement)16 May: 198 ms (good)23 May: 202 ms (needs improvement)30 May: 202 ms (needs improvement)6 Jun: 189 ms (good)13 Jun: 178 ms (good)20 Jun: 187 ms (good)27 Jun: 183 ms (good)4 Jul: 186 ms (good)11 Jul: 195 ms (good)18 Jul: 185 ms (good)25 Jul: 177 ms (good)1 Aug: 179 ms (good)8 Aug: 179 ms (good)15 Aug: 159 ms (good)22 Aug: 183 ms (good)29 Aug: 179 ms (good)5 Sept: 181 ms (good)12 Sept: 179 ms (good)179 ms

Latest window: 86% of visits good, 10% needs improvement, 4% poor.

Cumulative Layout ShiftCLS0.05good-0.15 over 40 weeks
0.100.25Dec 25Feb 26Apr 26Jun 26Aug 2613 Dec: 0.20 (needs improvement)20 Dec: 0.19 (needs improvement)27 Dec: 0.18 (needs improvement)3 Jan: 0.18 (needs improvement)10 Jan: 0.18 (needs improvement)17 Jan: 0.19 (needs improvement)24 Jan: 0.18 (needs improvement)31 Jan: 0.18 (needs improvement)7 Feb: 0.17 (needs improvement)14 Feb: 0.16 (needs improvement)21 Feb: 0.17 (needs improvement)28 Feb: 0.17 (needs improvement)7 Mar: 0.17 (needs improvement)14 Mar: 0.16 (needs improvement)21 Mar: 0.15 (needs improvement)28 Mar: 0.15 (needs improvement)4 Apr: 0.13 (needs improvement)11 Apr: 0.13 (needs improvement)18 Apr: 0.12 (needs improvement)25 Apr: 0.11 (needs improvement)2 May: 0.10 (needs improvement)9 May: 0.10 (needs improvement)16 May: 0.09 (good)23 May: 0.10 (good)30 May: 0.10 (good)6 Jun: 0.08 (good)13 Jun: 0.09 (good)20 Jun: 0.08 (good)27 Jun: 0.08 (good)4 Jul: 0.06 (good)11 Jul: 0.05 (good)18 Jul: 0.05 (good)25 Jul: 0.04 (good)1 Aug: 0.04 (good)8 Aug: 0.05 (good)15 Aug: 0.05 (good)22 Aug: 0.05 (good)29 Aug: 0.04 (good)5 Sept: 0.04 (good)12 Sept: 0.05 (good)0.05

Latest window: 83% of visits good, 12% needs improvement, 5% poor.

First Contentful PaintFCP1.5 sgood−822 ms over 40 weeks
1.8 s3.0 sDec 25Feb 26Apr 26Jun 26Aug 2613 Dec: 2.4 s (needs improvement)20 Dec: 2.4 s (needs improvement)27 Dec: 2.3 s (needs improvement)3 Jan: 2.5 s (needs improvement)10 Jan: 2.4 s (needs improvement)17 Jan: 2.4 s (needs improvement)24 Jan: 2.4 s (needs improvement)31 Jan: 2.4 s (needs improvement)7 Feb: 2.3 s (needs improvement)14 Feb: 2.4 s (needs improvement)21 Feb: 2.3 s (needs improvement)28 Feb: 2.2 s (needs improvement)7 Mar: 2.2 s (needs improvement)14 Mar: 2.1 s (needs improvement)21 Mar: 2.1 s (needs improvement)28 Mar: 2.1 s (needs improvement)4 Apr: 2.0 s (needs improvement)11 Apr: 2.1 s (needs improvement)18 Apr: 1.9 s (needs improvement)25 Apr: 2.0 s (needs improvement)2 May: 2.0 s (needs improvement)9 May: 1.9 s (needs improvement)16 May: 1.8 s (needs improvement)23 May: 1.8 s (needs improvement)30 May: 1.8 s (good)6 Jun: 1.8 s (needs improvement)13 Jun: 1.7 s (good)20 Jun: 1.7 s (good)27 Jun: 1.6 s (good)4 Jul: 1.6 s (good)11 Jul: 1.7 s (good)18 Jul: 1.6 s (good)25 Jul: 1.6 s (good)1 Aug: 1.6 s (good)8 Aug: 1.6 s (good)15 Aug: 1.5 s (good)22 Aug: 1.5 s (good)29 Aug: 1.5 s (good)5 Sept: 1.5 s (good)12 Sept: 1.5 s (good)1.5 s

Latest window: 78% of visits good, 15% needs improvement, 7% poor.

Time to First ByteTTFB701 msgood−405 ms over 40 weeks
800 ms1.8 sDec 25Feb 26Apr 26Jun 26Aug 2613 Dec: 1.1 s (needs improvement)20 Dec: 1.1 s (needs improvement)27 Dec: 1.0 s (needs improvement)3 Jan: 1.1 s (needs improvement)10 Jan: 1.1 s (needs improvement)17 Jan: 1.1 s (needs improvement)24 Jan: 1.0 s (needs improvement)31 Jan: 1.1 s (needs improvement)7 Feb: 1.1 s (needs improvement)14 Feb: 1.1 s (needs improvement)21 Feb: 983 ms (needs improvement)28 Feb: 989 ms (needs improvement)7 Mar: 948 ms (needs improvement)14 Mar: 1.0 s (needs improvement)21 Mar: 944 ms (needs improvement)28 Mar: 910 ms (needs improvement)4 Apr: 928 ms (needs improvement)11 Apr: 969 ms (needs improvement)18 Apr: 940 ms (needs improvement)25 Apr: 855 ms (needs improvement)2 May: 824 ms (needs improvement)9 May: 898 ms (needs improvement)16 May: 838 ms (needs improvement)23 May: 836 ms (needs improvement)30 May: 746 ms (good)6 Jun: 725 ms (good)13 Jun: 785 ms (good)20 Jun: 738 ms (good)27 Jun: 681 ms (good)4 Jul: 772 ms (good)11 Jul: 723 ms (good)18 Jul: 731 ms (good)25 Jul: 635 ms (good)1 Aug: 719 ms (good)8 Aug: 616 ms (good)15 Aug: 705 ms (good)22 Aug: 651 ms (good)29 Aug: 634 ms (good)5 Sept: 657 ms (good)12 Sept: 701 ms (good)701 ms

Latest window: 79% of visits good, 15% needs improvement, 6% poor.

The numbers, week by week
75th percentile per 28-day window ending on the date, for each metric
Window endsLCP p75INP p75CLS p75FCP p75TTFB p75LCP good share
2025-12-134.3 s250 ms0.202.4 s1.1 s44%
2025-12-204.2 s248 ms0.192.4 s1.1 s42%
2025-12-274.3 s246 ms0.182.3 s1.0 s47%
2026-01-034.2 s267 ms0.182.5 s1.1 s46%
2026-01-104.3 s247 ms0.182.4 s1.1 s41%
2026-01-174.2 s249 ms0.192.4 s1.1 s45%
2026-01-244.1 s252 ms0.182.4 s1.0 s44%
2026-01-314.1 s264 ms0.182.4 s1.1 s48%
2026-02-074.0 s238 ms0.172.3 s1.1 s64%
2026-02-144.0 s247 ms0.162.4 s1.1 s42%
2026-02-213.9 s248 ms0.172.3 s983 ms67%
2026-02-283.8 s255 ms0.172.2 s989 ms58%
2026-03-073.8 s250 ms0.172.2 s948 ms61%
2026-03-143.8 s248 ms0.162.1 s1.0 s65%
2026-03-213.6 s228 ms0.152.1 s944 ms59%
2026-03-283.5 s228 ms0.152.1 s910 ms62%
2026-04-043.5 s223 ms0.132.0 s928 ms57%
2026-04-113.5 s236 ms0.132.1 s969 ms64%
2026-04-183.4 s234 ms0.121.9 s940 ms65%
2026-04-253.2 s206 ms0.112.0 s855 ms63%
2026-05-023.3 s203 ms0.102.0 s824 ms66%
2026-05-093.0 s202 ms0.101.9 s898 ms60%
2026-05-163.1 s198 ms0.091.8 s838 ms64%
2026-05-232.8 s202 ms0.101.8 s836 ms63%
2026-05-302.7 s202 ms0.101.8 s746 ms63%
2026-06-062.6 s189 ms0.081.8 s725 ms62%
2026-06-132.6 s178 ms0.091.7 s785 ms65%
2026-06-202.7 s187 ms0.081.7 s738 ms66%
2026-06-272.4 s183 ms0.081.6 s681 ms82%
2026-07-042.5 s186 ms0.061.6 s772 ms83%
2026-07-112.4 s195 ms0.051.7 s723 ms78%
2026-07-182.3 s185 ms0.051.6 s731 ms84%
2026-07-252.3 s177 ms0.041.6 s635 ms83%
2026-08-012.1 s179 ms0.041.6 s719 ms86%
2026-08-082.1 s179 ms0.051.6 s616 ms85%
2026-08-152.1 s159 ms0.051.5 s705 ms80%
2026-08-222.2 s183 ms0.051.5 s651 ms81%
2026-08-292.1 s179 ms0.041.5 s634 ms83%
2026-09-052.1 s181 ms0.041.5 s657 ms78%
2026-09-122.1 s179 ms0.051.5 s701 ms82%

Want the lab side too (the element behind the LCP, the scripts behind INP)? Run the Core Web Vitals checker on the same page.

Run it on your site

What this tool checks

Google's own field data for your site or one page, plotted against the good and poor thresholds. Nothing is measured by us.

  • Up to 40 weeks

    Up to 40 weekly collection periods, each a 28-day window, from the Chrome UX Report History API.

  • Five metrics

    The 75th percentile of LCP, INP, CLS, FCP and TTFB for every week.

  • Good, needs improvement, poor

    The share of visits that were good, needs-improvement and poor, week by week.

  • Plotted against Google's thresholds

    A regression or an improvement shows as a line crossing a band, so the week it happened stands out.

  • Phone, desktop or both

    Choose phone, desktop or all form factors combined.

  • Whole site or one page

    Query the origin or a single page. When the page has no data, the tool falls back to the origin and says so.

Show 2 more checks

  • Phone, desktop or both

    Choose phone, desktop or all form factors combined.

  • Whole site or one page

    Query the origin or a single page. When the page has no data, the tool falls back to the origin and says so.

How it works

  1. Enter a site or page

    Type the address of your site, or of one popular page, and pick phone, desktop or all form factors.

  2. Query the Chrome UX Report

    We ask the Chrome UX Report History API for that origin or page. This is what real Chrome users experienced.

  3. Read the chart

    Each metric is drawn against Google's thresholds. Look for the week a line crosses a band and match it to a release.

Real-user data exists only for sites and pages with enough Chrome traffic. Smaller sites are not in the dataset; test them with the speed test instead.

Questions

Is this really free?

Yes. getReport is funded by donations, not plans, so there is no paid tier and nothing to unlock. The daily limits only keep the service free for everyone.

Why is there no data for my site?

Google publishes Core Web Vitals only for origins and pages with enough Chrome visitors to be statistically meaningful and anonymous. Smaller sites are not in the dataset; test the page with the speed test instead, which measures it in a lab.

Page or whole site?

Most sites only have origin-level data (all pages combined). Page-level history exists for popular URLs; the tool falls back to the origin when the page has none and says so.

Why does history beat a single test?

A lab test tells you how the page performs on one machine, now. The field data tells you how it performed for your visitors, and the history tells you when it changed. A Core Web Vitals drop usually has a date: a theme update, a new plugin, a heavier hero image, a tag manager container. The week it happened is in this chart. The paid monitoring tools sell exactly this view; Google publishes the data for free.

How current is it?

Each point is a 28-day window that ends on the given date; Google updates the history weekly, usually on Tuesdays. The last point covers roughly the last month.

Related free tools

All 41 tools →

Free, funded by the people who use it

€0 of €75 this month. At €75, site crawl up to 500 pages + weekly re-check switches on for everyone.

Chip in