Core Web Vitals Monitor – Track your Page Speed & Load Times for Real Users
Core Web Vitals Monitor adds a sidebar to posts & pages and dashboard widget that show you how quickly your pages are loading for real visitors. We report page load times from real users as they experience your site so your data isn’t limited to your internet speed.
Core Web Vitals
This plugin uses the Google Chrome team’s web vitals package to ensure you get the most accurate data from visitor’s loading experience.
Measurable Insights
With real user data, you can see if the changes you’re making are making a measurable impact for users. We collect all the core web vitals that Google uses as ranking factors:
* Cumulative Layout Shift (CLS)
* First Input Delay (FID)
* Largest Contentful Paint (LCP)
Plus the following experimental/less key statistics:
* First Contentful Paint (FCP)
* Input to Next Paint (INP)
* Time to First Byte (TTFB)
Tiny and Focused
The Core Web Vitals Monitor is a tiny plugin focused on one thing: accurate page speed data. Our load time tracker script is only 3.2kb large and is loaded asynchronously so it won’t increase your page load times.
FAQS
Does this work with the Gutenberg Block Editor?
Yes! The Core Web Vitals Monitor will appear on the right hand side under your post/page’s publishing settings.
Does this work with the Classic Editor?
Yes! The Core Web Vitals Monitor will appear on the right hand side under your post/page’s publishing settings.
Can I see page load times for a specific URL?
Yes, when you open a page or post in your WordPress admin area those statistics are only for the URL of that post. You can scroll down to the bottom of the monitor to see how many visits and what URL the data is for.
Where can I see the page load times for the entire site?
If you visit your WordPress admin dashboard, you’ll see the Core Web Vitals for all URLs collected on your site.
Will URL query parameters mess this up?
No. When we track the URL the user is on we strip back everything except the scheme (http or https), host name (www.example.com) and the path (/about-me). If the user is on a page with query parameters or a hash then this will be removed. The only thing that may lead to inconsistent results is if your scheme is inconsistent, for example if users are able to visit the site through HTTP and HTTPS.
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| c*i*o*r*c*i*o*f*c*d*s*g*.com | F | 2026-05-27 08:37:04 | |
| r*d*c*r*i*c*l*a*i*t*.ro | F | 2026-05-20 06:13:22 | |
| c*o*s*i*l*s*n*.com | F | 2026-05-14 07:06:06 | |
| c*o*s*i*l*s*e*i*n.com | F | 2026-05-14 07:06:06 | |
| t*c*a*.com (WP 6.8.5) | F | 2026-05-14 05:50:21 | |
| d*r*v*x.c*m.au (WP 6.9.4) | F | 2026-05-10 17:52:55 | |
| d*r*a*o*e*.c*m.br (WP 6.2.9) | F | 2026-05-08 09:59:02 | |
| i*f*-*a*a*i*s.com (WP 6.9.4) | F | 2026-05-07 12:11:07 | |
| k*c*i*a*i.c*.in (WP 6.9.1) | F | 2026-05-04 01:17:08 | |
| m*a*i*g*o*p.com (WP 6.8.3) | D | 2026-04-25 15:42:49 |