• PerfKit
CrUX
    • CrUX Report
    • Compare URLs
    • Page vs Origin
    • Alerts
    • Reports
    • Webhooks
Lab
    • Audit
    • History
    • Schedules
React
  • ProfilerBeta
Page vs Origin

Compare with
Origin

See how a specific page performs against the overall site origin using real-world Chrome data.

compared with origin
Origin auto-detected from URL above
Page vs site-wide
Same CrUX data
Spot page-specific issues
Page vs Origin
/pricing
all pages
LCP
3.3s
2.9s
INP
298ms
263ms
CLS
0.06
0.04
FCP
1.2s
1.9s

What's in the comparison

See exactly where your page differs

/pricing
origin
LCP3.3s2.9s
INP298ms263ms
CLS0.060.04
FCP1.2s1.9s

Metric Comparison

Page metrics against the site average

See every Core Web Vital for your specific page next to the origin-wide P75 — instantly spot where the page diverges from the site.

LCP Divergence
Page
Origin
OctNovDecJanFebMar

Trend Divergence

Watch page and origin drift apart

6-month trend lines for both page and origin overlaid on good/poor zones — see if the gap is growing or shrinking.

Distribution Comparison
LCPpage / origin
INPpage / origin
CLSpage / origin

Distribution

Experience split, compared

Good, borderline, and poor user experience distribution for the page versus the entire origin.

CWV Assessment
/pricing46% pass
origin92% pass

CWV Assessment

Pass/fail history, side by side

Does this page fail CWV more often than the overall site? See the pass/fail timeline for both.

Delta Summary
Score
62-22.0084
LCP
3.3s+0.4s2.9s
CLS
0.06+0.020.04

Delta Summary

The gap at a glance

How much worse (or better) is this page compared to the origin? Key deltas summarized in one view.

Go deeper

Now that you've isolated the issue

CrUX Report
Field data

Get the full 6-month trend

Go beyond the page vs origin snapshot. See P75 trends, distributions, and CWV assessment history for any URL.

Try it
Lighthouse Audit
Lab data

Diagnose what's causing the gap

Found a page-level regression? Run a Lighthouse audit to identify render-blocking resources, layout shifts, and optimization opportunities.

Try it
Compare URLs
CrUX field data

Benchmark against competitors

See how your real-world Core Web Vitals compare to up to 4 other sites using Chrome field data, side by side.

Try it

Track over time

Don't just check once — monitor it

Set up alerts to get notified when Core Web Vitals regress, or subscribe to weekly reports that land in your inbox when CrUX data updates.

Frequently Asked Questions

How to interpret page vs origin comparisons and when to use this diagnostic tool.

What does 'origin' mean in CrUX?
In the Chrome User Experience Report, 'origin' refers to the aggregate performance data for an entire domain (e.g., all pages on example.com). It represents the combined experience of all Chrome users across every page on that site.
When is a page worse than the origin?
When a page's P75 metric is higher (slower) than the origin's, it means that specific page underperforms relative to the site average. This usually indicates a page-specific issue — heavy images, slow third-party scripts, or unoptimized layout unique to that page.
When is a page better than the origin?
When a page's metrics are faster than the origin average, it means the page is not the bottleneck. Other pages on the site are likely dragging down the overall score. This is useful for identifying which pages need attention and which are already optimized.
How is this different from Compare URLs?
Compare URLs benchmarks up to 5 arbitrary URLs against each other — different sites, different pages. Page vs Origin specifically compares one page against its own site-wide baseline, which is a diagnostic tool for isolating page-level vs sitewide issues.
What if the page and origin have similar metrics?
Similar metrics between a page and its origin usually indicate a sitewide or systemic issue — server configuration, shared JavaScript bundles, CDN setup, or CMS-level problems that affect all pages equally. Fixing the page alone won't help; you need to address the root cause across the site.
How is the origin URL detected?
The origin is automatically extracted from the URL you enter. For example, if you enter 'example.com/pricing', the origin becomes 'example.com'. Both the page and origin data come from the same CrUX dataset and form factor, ensuring an apples-to-apples comparison.
PerfKit

Free web performance toolkit. Analyze Core Web Vitals, compare URLs, and optimize real-world performance with Chrome field data.

CrUX

  • CrUX Report
  • Compare URLs
  • Page vs Origin

Product

  • All Tools
  • Lighthouse

© 2026 PerfKit. All rights reserved.