Page views
727
7d
▲ 2% vs previous 7d
LCP · p75
1.86 s
85% good · 727 samples
± 0% vs previous 7d
INP · p75
198 ms
75% good · 488 samples
▼ 4% vs previous 7d
CLS · p75
0.03
90% good · 727 samples
▲ 20% vs previous 7d
FCP · p75
1.52 s
82% good · 727 samples
▼ 1% vs previous 7d
TTFB · p75
817 ms
74% good · 727 samples
▼ 4% vs previous 7d
Happy page views
64%
12% unhappy · 727 rated
What to fix first
Slow page loads cost you engagement
Comparing like with like (the same page type), page views whose main content took over 4 s got 48% less engaged time and 77% fewer clicks than ones that loaded in under 2.5 s. Based on 52 slow page views across 4 page types.
Compare fast and slow page views →
Mobile visitors get a much slower INP
p75 INP is 233 ms on mobile against 144 ms on desktop. Mobile is 50% 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 →
CLS got 20% worse than the previous 7d
p75 CLS is now 0.03. The Vitals tab shows when it changed and which pages it changed on.
CLS over time →
Taps and clicks on this element respond slowly
#onetrust-accept-btn-handler
p75 INP is 214 ms over 125 page views, mostly on /. 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
div.ad-slot
p75 CLS is 0.10 on the 87 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 →
This element makes the page jump as it loads
header.site-header
p75 CLS is 0.11 on the 75 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 →
3 more findings
Taps and clicks on this element respond slowly
button.add-to-cart
p75 INP is 210 ms over 62 page views, mostly on /articles/0/. 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 →
Taps and clicks on this element respond slowly
div.related-articles > a
p75 INP is 231 ms over 54 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 1.86 s, INP 198 ms, CLS 0.03: that's Google's "good" for each. Watch "Biggest changes" for regressions.
Vitals →
Trend
By device
| Device | Page views | p75 LCP | p75 INP | p75 CLS |
|---|---|---|---|---|
| Mobile | 367 | 2.16 s | 233 ms | 0.05 |
| Desktop | 277 | 1.53 s | 144 ms | 0.02 |
| Tablet | 83 | 2.19 s | 214 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 | 617 | 1.74 | 38.7 s | 57% |
| Needs improvement | 56 | 0.98 | 24.8 s | 61% |
| Poor | 54 | 0.39 | 19.2 s | 40% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| Avg engaged time | 30.0 s | 36.2 s | ▲ 21% |
| p75 LCP · Render delay | 484 ms | 400 ms | ▼ 17% |
| p75 TTFB | 848 ms | 817 ms | ▼ 4% |
| p75 TTFB · Server wait | 620 ms | 606 ms | ▼ 2% |