Core Web Vitals report: up to 40 weeks of real-user history
This Core Web Vitals report shows up to 40 weeks of real-user LCP, INP and CLS for your site, week by week, so you can spot the release that broke it and the one that fixed it.
- Free, no account
- Results in seconds
- Any site in the Chrome UX Report
Example resultWhole site · https://example-shop.hr
latest: good40 weekly windows from 2025-11-16 to 2026-09-12, phone. Each point is the 75th percentile of a 28-day window.
Latest window: 82% of visits good, 13% needs improvement, 5% poor.
Latest window: 86% of visits good, 10% needs improvement, 4% poor.
Latest window: 83% of visits good, 12% needs improvement, 5% poor.
Latest window: 78% of visits good, 15% needs improvement, 7% poor.
Latest window: 79% of visits good, 15% needs improvement, 6% poor.
The numbers, week by week
| Window ends | LCP p75 | INP p75 | CLS p75 | FCP p75 | TTFB p75 | LCP good share |
|---|---|---|---|---|---|---|
| 2025-12-13 | 4.3 s | 250 ms | 0.20 | 2.4 s | 1.1 s | 44% |
| 2025-12-20 | 4.2 s | 248 ms | 0.19 | 2.4 s | 1.1 s | 42% |
| 2025-12-27 | 4.3 s | 246 ms | 0.18 | 2.3 s | 1.0 s | 47% |
| 2026-01-03 | 4.2 s | 267 ms | 0.18 | 2.5 s | 1.1 s | 46% |
| 2026-01-10 | 4.3 s | 247 ms | 0.18 | 2.4 s | 1.1 s | 41% |
| 2026-01-17 | 4.2 s | 249 ms | 0.19 | 2.4 s | 1.1 s | 45% |
| 2026-01-24 | 4.1 s | 252 ms | 0.18 | 2.4 s | 1.0 s | 44% |
| 2026-01-31 | 4.1 s | 264 ms | 0.18 | 2.4 s | 1.1 s | 48% |
| 2026-02-07 | 4.0 s | 238 ms | 0.17 | 2.3 s | 1.1 s | 64% |
| 2026-02-14 | 4.0 s | 247 ms | 0.16 | 2.4 s | 1.1 s | 42% |
| 2026-02-21 | 3.9 s | 248 ms | 0.17 | 2.3 s | 983 ms | 67% |
| 2026-02-28 | 3.8 s | 255 ms | 0.17 | 2.2 s | 989 ms | 58% |
| 2026-03-07 | 3.8 s | 250 ms | 0.17 | 2.2 s | 948 ms | 61% |
| 2026-03-14 | 3.8 s | 248 ms | 0.16 | 2.1 s | 1.0 s | 65% |
| 2026-03-21 | 3.6 s | 228 ms | 0.15 | 2.1 s | 944 ms | 59% |
| 2026-03-28 | 3.5 s | 228 ms | 0.15 | 2.1 s | 910 ms | 62% |
| 2026-04-04 | 3.5 s | 223 ms | 0.13 | 2.0 s | 928 ms | 57% |
| 2026-04-11 | 3.5 s | 236 ms | 0.13 | 2.1 s | 969 ms | 64% |
| 2026-04-18 | 3.4 s | 234 ms | 0.12 | 1.9 s | 940 ms | 65% |
| 2026-04-25 | 3.2 s | 206 ms | 0.11 | 2.0 s | 855 ms | 63% |
| 2026-05-02 | 3.3 s | 203 ms | 0.10 | 2.0 s | 824 ms | 66% |
| 2026-05-09 | 3.0 s | 202 ms | 0.10 | 1.9 s | 898 ms | 60% |
| 2026-05-16 | 3.1 s | 198 ms | 0.09 | 1.8 s | 838 ms | 64% |
| 2026-05-23 | 2.8 s | 202 ms | 0.10 | 1.8 s | 836 ms | 63% |
| 2026-05-30 | 2.7 s | 202 ms | 0.10 | 1.8 s | 746 ms | 63% |
| 2026-06-06 | 2.6 s | 189 ms | 0.08 | 1.8 s | 725 ms | 62% |
| 2026-06-13 | 2.6 s | 178 ms | 0.09 | 1.7 s | 785 ms | 65% |
| 2026-06-20 | 2.7 s | 187 ms | 0.08 | 1.7 s | 738 ms | 66% |
| 2026-06-27 | 2.4 s | 183 ms | 0.08 | 1.6 s | 681 ms | 82% |
| 2026-07-04 | 2.5 s | 186 ms | 0.06 | 1.6 s | 772 ms | 83% |
| 2026-07-11 | 2.4 s | 195 ms | 0.05 | 1.7 s | 723 ms | 78% |
| 2026-07-18 | 2.3 s | 185 ms | 0.05 | 1.6 s | 731 ms | 84% |
| 2026-07-25 | 2.3 s | 177 ms | 0.04 | 1.6 s | 635 ms | 83% |
| 2026-08-01 | 2.1 s | 179 ms | 0.04 | 1.6 s | 719 ms | 86% |
| 2026-08-08 | 2.1 s | 179 ms | 0.05 | 1.6 s | 616 ms | 85% |
| 2026-08-15 | 2.1 s | 159 ms | 0.05 | 1.5 s | 705 ms | 80% |
| 2026-08-22 | 2.2 s | 183 ms | 0.05 | 1.5 s | 651 ms | 81% |
| 2026-08-29 | 2.1 s | 179 ms | 0.04 | 1.5 s | 634 ms | 83% |
| 2026-09-05 | 2.1 s | 181 ms | 0.04 | 1.5 s | 657 ms | 78% |
| 2026-09-12 | 2.1 s | 179 ms | 0.05 | 1.5 s | 701 ms | 82% |
Want the lab side too (the element behind the LCP, the scripts behind INP)? Run the Core Web Vitals checker on the same page.
What the Core Web Vitals report shows
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 the Core Web Vitals report works
Enter a site or page
Type the address of your site, or of one popular page, and pick phone, desktop or all form factors.
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.
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.
Core Web Vitals report questions
How long do Core Web Vitals take to update after a fix?
About four weeks to show in full. The Chrome UX Report covers a rolling 28-day window, and the history adds a new point every week, so a fix shipped today moves the line a little each week. Search Console's Core Web Vitals report uses the same data, which is why its Validate fix runs for 28 days.
How do I check Core Web Vitals over time?
Enter your site above and pick phone, desktop or both. The tool asks the Chrome UX Report History API for up to 40 weekly data points and draws each metric against Google's thresholds. Search Console's Core Web Vitals report shows a shorter trend for sites you have verified; this works for any site in the dataset, including your competitors.
Can I see the Core Web Vitals of a competitor's site?
Yes, if the site has enough Chrome traffic to be in the Chrome UX Report, which is public data. Enter its address to see up to 40 weeks of its LCP, INP and CLS. Nothing is requested from the site itself, so its owner does not see the lookup. Smaller sites are not in the dataset and show no data.
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 and shows what to fix.
Page or whole site?
Most sites only have origin-level data, all pages combined. Page-level history exists for popular URLs, so try your home page or a top landing page. When the page you enter has no data, the tool falls back to the origin and says so, so the chart never mixes the two without telling you.
How current is it?
Each point is a 28-day window that ends on the date shown, and Google adds a new point once a week, so the latest point covers roughly the last month. A fix you ship today shows fully only after four weeks, as the older days roll out of the window.
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.
Is this Core Web Vitals report free?
Yes, with no sign-up. getReport is funded by donations, so there is no paid tier and nothing to unlock. The data comes from Google's public Chrome UX Report, and the daily limits only keep the service free for everyone. Paid monitoring tools sell this view; Google publishes the data for free.
Related free tools
All 59 tools →Free, funded by the people who use it
No account, no paid plan. Donations keep it running.