Core Web Vitals History Checker
Know if the Core Web Vitals for your website degraded in the last six months.
FreeHelpersMonitoring1,453 impressions#8 of its week
Core Web Vitals History Checker visualizes a URL’s Core Web Vitals trends over the past six months using Google’s CrUX data.
- for
- Web developers and site owners monitoring performance trends
- pricing
- free
Key features
- Six-month trend chart — Shows visual graphs of Core Web Vitals for a URL or origin over the last six months.
- CrUX data source — Fetches real-user metrics directly from Google’s CrUX API.
- Metric categories — Displays Good, Needs Improvement, and Poor ranges for LCP, FID, CLS, etc.
- No data storage — The tool does not capture or store any user data; it only displays fetched results.
Use cases
- Identify when a performance regression occurred on a site
- Correlate metric drops with code or infrastructure changes
- Validate the impact of recent optimizations over time
- Check if a new release improved or degraded user experience
Core Web Vitals History Checker vs alternatives
 Pulsetic |  Argos |  Void Analytics | ||
|---|---|---|---|---|
| Best for | Historical Core Web Vitals view | Website uptime alerts | Visual regression testing | Privacy-focused web analytics |
| Pricing | Free | Free | Free | Subscription |
| DevHunt upvotes | 1 | 162 | 17 | 17 |
| Launched | Dec 2025 | Jan 2024 | Jan 2023 | Mar 2024 |
- Core Web Vitals History Checker vs Pulsetic: Provides real-time uptime monitoring, not historical performance metrics
- Core Web Vitals History Checker vs Argos: Offers visual UI testing rather than performance metric history
- Core Web Vitals History Checker vs Void Analytics: Focuses on privacy-first analytics, not Core Web Vitals trends
Core Web Vitals History Checker FAQ
What information does this tool provide?+
It provides a visual representation of Core Web Vitals for a given URL for the last six months, if data is available.
Where does the data come from?+
Data is fetched from Google’s CrUX API, the same source used by pagespeed.web.dev and Google Search Console.
How is this different from Google PageSpeed?+
PageSpeed shows current metrics, while this tool shows historical data to pinpoint when degradations or improvements happened.
Why isn’t there data for some URLs?+
Google excludes URLs with low traffic from CrUX, so the tool cannot display metrics for them.
Does the tool store any data?+
No, it only retrieves and displays data from the CrUX API without storing anything.
Summarized by DevHunt from punits.dev · Sep 28, 2026. Details may change; check the official site.
.png?width=64)
.png?width=64)
