Page views
59
7d
▼ 25% vs previous 7d
LCP · p75
2.02 s
81% good · 59 samples
▼ 13% vs previous 7d
INP · p75
185 ms
77% good · 39 samples
▲ 28% vs previous 7d
CLS · p75
0.06
86% good · 59 samples
▲ 106% vs previous 7d
FCP · p75
2.01 s
73% good · 59 samples
▼ 13% vs previous 7d
TTFB · p75
1.03 s
63% good · 59 samples
▼ 14% vs previous 7d
Happy page views
59%
19% unhappy · 59 rated
15% of these page views were in-app (soft) navigations. Those report INP and CLS, but browsers only measure LCP, FCP and TTFB on full page loads, so those three cover fewer page views.
What to fix first
CLS got 106% worse than the previous 7d
p75 CLS is now 0.06. The Vitals tab shows when it changed and which pages it changed on.
CLS over time →
Mobile visitors get a much slower INP
p75 INP is 362 ms on mobile against 139 ms on desktop. Mobile is 42% of your page views.
Try: Test on a real mid-range phone or with CPU throttling: big images, heavy JavaScript and third-party scripts cost far more there.
INP by device →
INP got 28% worse than the previous 7d
p75 INP is now 185 ms. The Vitals tab shows when it changed and which pages it changed on.
INP over time →
Taps and clicks on this element respond slowly
button.menu-toggle
p75 INP is 225 ms over 10 page views, mostly on /search/. Most of the time goes on running the event handler.
Try: The event handler itself is slow: do less work in it, or yield (scheduler.yield / setTimeout) before the heavy part.
INP by element →
This element makes the page jump as it loads
ul.product-grid
p75 CLS is 0.13 on the 6 page views where it shifted, mostly on /search/.
Try: Reserve its space before it arrives: width and height (or aspect-ratio) on images and embeds, a min-height for content inserted later, and font-display with matched fallback metrics for web fonts.
CLS by element →
Key presses in this element respond slowly
#search_input
p75 INP is 324 ms over 4 page views, mostly on /search/. Most of the time goes on running the event handler.
Try: The event handler itself is slow: do less work in it, or yield (scheduler.yield / setTimeout) before the heavy part.
INP by element →
2 more findings
Taps and clicks on this element respond slowly
div.related-articles > a
p75 INP is 213 ms over 4 page views, mostly on /search/. Most of the time goes on running the event handler.
Try: The event handler itself is slow: do less work in it, or yield (scheduler.yield / setTimeout) before the heavy part.
INP by element →
All three Core Web Vitals pass
p75 LCP 2.02 s, INP 185 ms, CLS 0.06: that's Google's "good" for each. Watch "Biggest changes" for regressions.
Vitals →
Based on 59 page views. Findings need at least 5 measured page views each, so more show up as traffic grows (try the 30d range).
Trend
By device
| Device | Page views | p75 LCP | p75 INP | p75 CLS |
|---|---|---|---|---|
| Desktop | 30 | 1.94 s | 139 ms | 0.05 |
| Mobile | 25 | 1.49 s | 362 ms | 0.05 |
| Tablet | 4 | 3.07 s | 288 ms | 0.03 |
Does speed cost engagement?
Page views grouped by their own LCP. If slower pages get fewer clicks and less reading, that's the cost of slowness.
| LCP | Page views | Clicks per view | Engaged time | Avg scroll |
|---|---|---|---|---|
| Good | 48 | 1.58 | 30.8 s | 62% |
| Needs improvement | 4 | 1.25 | 68.2 s | 63% |
| Poor | 7 | 0.57 | 32.5 s | 40% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 CLS | 0.03 | 0.06 | ▲ 106% |
| p75 INP · Processing | 65 ms | 83 ms | ▲ 28% |
| p75 INP · Presentation | 43 ms | 56 ms | ▲ 28% |
| p75 INP | 145 ms | 185 ms | ▲ 28% |
| p75 INP · Input delay | 36 ms | 46 ms | ▲ 28% |
| p75 TTFB · TLS | 136 ms | 112 ms | ▼ 18% |
| p75 TTFB · Server wait | 872 ms | 728 ms | ▼ 17% |
| p75 TTFB | 1.20 s | 1.03 s | ▼ 14% |
| p75 LCP | 2.32 s | 2.02 s | ▼ 13% |
| p75 FCP | 2.30 s | 2.01 s | ▼ 13% |
| p75 TTFB · Connect | 115 ms | 100 ms | ▼ 12% |
| Avg scroll depth | 57% | 60% | ▲ 5% |