Performance & Core Web Vitals (/analytics/performance)
The Performance view gives you Real User Monitoring (RUM) across all five key web performance metrics, collected directly from real visitors’ browsers via the native PerformanceObserver and NavigationTiming APIs.
Note: Performance & Core Web Vitals analytics are available on paid plans (Starter, Pro, and Enterprise).
1. Percentile Selector (P75, P90, P99)
In the top-right corner of the view, switch between three statistical percentiles:
- P75 (75th Percentile): Google’s official Core Web Vitals standard. If your P75 score is “Good”, at least 75% of your visitors experienced fast performance.
- P90 (90th Percentile): Highlights performance for users on slower networks or older mobile devices.
- P99 (99th Percentile): Captures tail-end worst-case experiences.
2. Interactive Core Web Vitals Cards
Five cards display your current score at the selected percentile, a status rating badge (Good, Needs Improvement, or Poor), and a distribution bar showing the percentage of visits falling into each rating bucket:
| Metric | What It Measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | How quickly the main hero image or heading finishes rendering. | ≤ 2.5s | ≤ 4.0s | > 4.0s |
| CLS (Cumulative Layout Shift) | Visual stability—whether elements jump around unexpectedly while loading. | ≤ 0.10 | ≤ 0.25 | > 0.25 |
| INP (Interaction to Next Paint) | Responsiveness when a user clicks, taps, or presses a key. | ≤ 200ms | ≤ 500ms | > 500ms |
| FCP (First Contentful Paint) | Time until the browser renders the very first piece of DOM content. | ≤ 1.8s | ≤ 3.0s | > 3.0s |
| TTFB (Time to First Byte) | Server and CDN response latency before the first byte arrives. | ≤ 800ms | ≤ 1.8s | > 1.8s |
Tip: Click any of the five cards to toggle its trendline on or off in the Performance Trends chart below.
3. Performance Trends Chart
The Performance Trends line chart plots your active Web Vitals metrics over time across the selected date range (Today, 24h, 48h, 7d, 30d). Overlay multiple metrics—such as TTFB and LCP—to see whether a spike in page load time was caused by backend server latency (TTFB) or heavy frontend assets (LCP).
4. Diagnostics & Element Attribution
Knowing your CLS or LCP score is poor is only half the battle—you also need to know which DOM element caused the issue. At the bottom of the page, three attribution tables list the exact CSS selectors (tag#id or tag.class) responsible for non-good experiences:
- Top LCP Elements: Lists the slowest-rendering hero images, video posters, or heading blocks, ranked by occurrence count and percentage share.
- Top CLS Shifts: Lists the specific containers or dynamic elements shifting layout without user input.
- Top INP Interactions: Lists the buttons, inputs, or interactive elements that caused >200ms main-thread blocking delays when clicked or tapped.