Page views
230
7d
▼ 12% vs previous 7d
LCP · p75
1.53 s
93% good · 230 samples
▲ 11% vs previous 7d
INP · p75
194 ms
77% good · 149 samples
▼ 10% vs previous 7d
CLS · p75
0.08
77% good · 230 samples
▲ 7% vs previous 7d
FCP · p75
1.53 s
80% good · 230 samples
▲ 12% vs previous 7d
TTFB · p75
826 ms
73% good · 230 samples
▲ 11% vs previous 7d
Happy page views
60%
13% unhappy · 230 rated
What to fix first
This element makes the page jump as it loads
#onetrust-banner-sdk
p75 CLS is 0.30 on the 20 page views where it shifted, mostly on /c/headsets/.
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.30 on the 27 page views where it shifted, mostly on /c/headsets/.
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 →
Mobile visitors get a much slower INP
p75 INP is 223 ms on mobile against 135 ms on tablet. Mobile is 54% 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 →
This element makes the page jump as it loads
div.ad-slot
p75 CLS is 0.14 on the 25 page views where it shifted, mostly on /c/headsets/. 1 more element that shifts is in the Vitals tab.
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 291 ms over 19 page views, mostly on /c/headsets/. 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
nav.toc > a.toc-link
p75 INP is 223 ms over 21 page views, mostly on /c/headsets/. 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 →
1 more finding
All three Core Web Vitals pass
p75 LCP 1.53 s, INP 194 ms, CLS 0.08: that's Google's "good" for each. Watch "Biggest changes" for regressions.
Vitals →
Based on 230 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 |
|---|---|---|---|---|
| Mobile | 124 | 1.74 s | 223 ms | 0.09 |
| Desktop | 80 | 1.26 s | 179 ms | 0.04 |
| Tablet | 26 | 1.53 s | 135 ms | 0.14 |
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 | 214 | 1.76 | 32.0 s | 59% |
| Needs improvement | 10 | 1.20 | 15.3 s | 57% |
| Poor | 6 | 0.33 | 9.0 s | 47% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 FCP | 1.37 s | 1.53 s | ▲ 12% |
| p75 LCP | 1.38 s | 1.53 s | ▲ 11% |
| p75 TTFB | 744 ms | 826 ms | ▲ 11% |
| p75 INP | 216 ms | 194 ms | ▼ 10% |
| Avg engaged time | 28.7 s | 30.7 s | ▲ 7% |
| p75 TTFB · Server wait | 649 ms | 681 ms | ▲ 5% |
| Avg scroll depth | 57% | 59% | ▲ 4% |
| p75 LCP · Render delay | 676 ms | 659 ms | ▼ 3% |