Page views
2.3k
7d
▼ 10% vs previous 7d
LCP · p75
1.97 s
85% good · 2.3k samples
▲ 2% vs previous 7d
INP · p75
215 ms
73% good · 1.5k samples
▲ 1% vs previous 7d
CLS · p75
0.03
89% good · 2.3k samples
▲ 7% vs previous 7d
FCP · p75
1.53 s
81% good · 2.3k samples
▼ 2% vs previous 7d
TTFB · p75
846 ms
73% good · 2.3k samples
± 0% vs previous 7d
Happy page views
63%
11% unhappy · 2.3k 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 56% less engaged time and 77% fewer clicks than ones that loaded in under 2.5 s. Based on 136 slow page views across 5 page types.
Compare fast and slow page views →
Mobile visitors get a much slower INP
p75 INP is 271 ms on mobile against 148 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 →
Taps and clicks on this element respond slowly
#onetrust-accept-btn-handler
p75 INP is 218 ms over 374 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
ul.product-grid
p75 CLS is 0.11 on the 238 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 →
Taps and clicks on this element respond slowly
button.menu-toggle
p75 INP is 234 ms over 197 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 →
Key presses in this element respond slowly
#search_input
p75 INP is 257 ms over 195 page views, mostly on /search/. Most of the time goes on running the event handler. 2 more slow elements are in the Vitals tab.
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
This element makes the page jump as it loads
header.site-header
p75 CLS is 0.10 on the 231 page views where it shifted, mostly on /.
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
div.ad-slot
p75 CLS is 0.11 on the 211 page views where it shifted, mostly on /.
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 →
Trend
By device
| Device | Page views | p75 LCP | p75 INP | p75 CLS |
|---|---|---|---|---|
| Mobile | 1.1k | 2.12 s | 271 ms | 0.04 |
| Desktop | 856 | 1.57 s | 148 ms | 0.03 |
| Tablet | 282 | 2.14 s | 229 ms | 0.04 |
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 | 1.9k | 1.72 | 33.3 s | 57% |
| Needs improvement | 211 | 0.88 | 24.2 s | 57% |
| Poor | 136 | 0.39 | 14.8 s | 41% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 LCP · Render delay | 484 ms | 469 ms | ▼ 3% |
| Avg engaged time | 32.3 s | 31.3 s | ▼ 3% |
| p75 LCP | 1.92 s | 1.97 s | ▲ 2% |
| p75 FCP | 1.57 s | 1.53 s | ▼ 2% |