Ready to boost your SEO?

View Pricing Login
All features
PageSpeed Monitor PRO

Lighthouse says green.
Google sees red.

A lab test simulates one visit. Google ranks on what real Chrome users experience. TamRank shows both numbers side by side, inside WP admin.

LCP · INP · CLScurrent Core Web Vitals lab + fieldside by side p50 / p75 / p95percentiles
Largest Contentful Paint / · mobile
Simulated · lab 2.1s Good
Real visitors · field 3.8s Poor at p75

Same page, same day. Google ranks on the number on the right.

What's in the monitor

Three parts, all PRO.

PageSpeed Monitor

Desktop and mobile via Google PageSpeed Insights, inside WP admin. LCP, INP and CLS per page.

PRO

CrUX Real User Data

Field data from real Chrome users next to your lab score, with the good / needs improvement / poor distribution and p50, p75 and p95 percentiles.

PRO

Bulk PageSpeed Scan

Test all pages at once and export the results.

PRO
example.com/wp-admin/admin.php?page=tamrank-pagespeed
Screenshot: PageSpeed results table, all pages, mini-bars per metric, CrUX field-status column on the right

Field data · CrUX

The number Google actually uses.

Field data is collected from real Chrome users over a rolling 28-day window. Google evaluates the p75 value: if p75 is poor, a perfect lab score will not change the signal.

LCP · field distribution 28-day window
Good 62% Needs improvement 23% Poor 15%
p502.4s
p753.8s
p956.1s

Half of your visitors are fine. The slowest quarter is what Google grades you on.

example.com/wp-admin · CrUX detail
Screenshot: expanded CrUX detail, distribution bar plus p50/p75/p95 percentile breakdown for one URL

When you'll reach for it

Use this when

A client says the site feels slow, but your lab score is 95

Their phones disagree with your test rig. Field data settles it with real visitor numbers, per page.

Use this when

Search Console flags CWV issues you can't reproduce

The issue lives in the field distribution, not in your lab run. Check the poor bucket and the p75 value for that URL.

Use this when

You run a performance sprint and need a before and after

Bulk-scan every page, export, fix, scan again. The delta is your report.

How this compares

Both numbers, in one place.

Most WordPress SEO plugins stop at a lab score, if they measure speed at all.

Yoast Rank Math AIOSEO TamRank
Lighthouse lab data
CrUX field data
Lab vs field, side by side
Percentile breakdown (p50 / p75 / p95)
Origin fallback for low-traffic pages

As of July 2026, based on public plugin documentation. Speed measurement is not part of the other plugins’ SEO modules.

PageSpeed Monitor is one piece of TamRank PRO.

What's included

PRO
PageSpeed Monitor, desktop and mobile CrUX field data with percentiles Bulk scan with export
PRO

Priority Actions

Impact-ordered fixes

PRO

SEO Change Tracker

Proof per change

PRO

Page Insights

Per-page GSC queries

PRO

Position Stability

Solid or shaky, per keyword

PRO

REST API write + batch

30 writes/min, 50 per batch

PRO

AI assistant integration

Your assistant runs TamRank

See everything included in TamRank PRO.

Frequently asked questions

Where does the field data come from?

From the Chrome UX Report (CrUX): anonymized performance data from real Chrome users, aggregated by Google over a rolling 28-day window.

Why do my lab and field numbers differ?

A lab test runs once, on one simulated device and network. Field data covers every real visitor, on slow phones and fast fiber alike. Both are true, they answer different questions.

My page has little traffic. Is there field data at all?

If a URL has too few samples, TamRank falls back to origin-level field data, so you still see how your site performs for real users.

Which metrics are tracked?

The current Core Web Vitals: LCP, INP and CLS, for desktop and mobile.

Does the monitor slow down my site?

No. Tests run through Google's PageSpeed Insights API. Nothing is injected into your visitors' pages.

See what Google sees.

Lab and field data for every page, inside WP admin. Part of TamRank PRO.