Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the really-simple-ssl domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/sodapixel.com/httpdocs/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/sodapixel.com/httpdocs/wp-includes/functions.php on line 6114
Core Web Vitals Monitor - SodaPixel

Core Web Vitals Monitor – Track Real User Page Speed on your WordPress Site

With the Core Web Vitals Monitor WordPress plugin, you can gather page speed and core web vital data from real users visiting your website on a page by page basis. 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.

Download Core Web Vitals Monitor for WordPress

Real Users, Real Data

When you use online tools or run Lighthouse from you own browser, your results are limited by your own internet speed or the speed of the service you use. With the Core Web Vitals Monitor for WordPress, your data comes from the real users who visit your website, it’s not simulated by a tool.

Built for Modern WordPress and Classic Installations

The Core Web Vitals Monitor WordPress plugin integrates with Gutenberg & full-site editing as well as the Classic Editor. You can view your page speed by page/post or site wide from your dashboard.

Accurate Page Speed Data, Defined by Google

Our WordPress plugin uses the Google Chrome team’s web vitals package to ensure your data is perfectly accurate. Your visitor’s loading experience is measured to Google’s standards and includes the full suite of ranking Core Web Vitals factors and new and experimental statistics.

Tiny, Focused & Fast

The Core Web Vitals Monitor is a tiny WordPress plugin focused on one thing: accurate page speed data. Our load time tracker script is only 3.2kb and is loaded asynchronously so it won’t increase your page load times. Don’t let your page load tracking increase page load times.

Measurable Page Speed 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 plus new experimental statistics.

  • Cumulative Layout Shift (CLS)
  • First Input Delay (FID)
  • Largest Contentful Paint (LCP)
  • First Contentful Paint (FCP)
  • Input to Next Paint (INP)
  • Time to First Byte (TTFB)

Frequently Asked Questions

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.

Collect Real Core Web Vitals on WordPress