Page views
1.8k
7d
▼ 13% vs previous 7d
LCP · p75
2.23 s
80% good · 1.8k samples
▼ 2% vs previous 7d
INP · p75
259 ms
65% good · 1.2k samples
▲ 2% vs previous 7d
CLS · p75
0.04
89% good · 1.8k samples
▲ 8% vs previous 7d
FCP · p75
1.78 s
76% good · 1.8k samples
▼ 4% vs previous 7d
TTFB · p75
954 ms
66% good · 1.8k samples
▼ 7% vs previous 7d
Happy page views
55%
14% unhappy · 1.8k 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 50% less engaged time and 80% fewer clicks than ones that loaded in under 2.5 s. Based on 143 slow page views across 5 page types.
Compare fast and slow page views →
Taps and clicks on this element respond slowly
#onetrust-accept-btn-handler
p75 INP is 260 ms over 313 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.11 on the 209 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.12 on the 202 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 →
/search/ pages are slow to show their main content
p75 LCP is 2.79 s over 182 full page loads; 10% took over 4 s. Most of the time goes on waiting for the server.
Try: Most of the time passes before the HTML arrives: cache pages at the edge/CDN or speed up the server.
LCP by page and element →
Taps and clicks on this element respond slowly
nav.toc > a.toc-link
p75 INP is 268 ms over 152 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 →
2 more findings
Taps and clicks on this element respond slowly
div.gallery > button.next
p75 INP is 249 ms over 160 page views, mostly on /. Most of the time goes on running the event handler. 4 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 →
This element makes the page jump as it loads
#onetrust-banner-sdk
p75 CLS is 0.11 on the 169 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 →
Trend
By device
| Device | Page views | p75 LCP | p75 INP | p75 CLS |
|---|---|---|---|---|
| Mobile | 1.4k | 2.21 s | 257 ms | 0.04 |
| Tablet | 369 | 2.28 s | 268 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 | 1.4k | 1.76 | 35.6 s | 57% |
| Needs improvement | 215 | 0.87 | 24.4 s | 56% |
| Poor | 143 | 0.36 | 17.7 s | 39% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 TTFB | 1.03 s | 954 ms | ▼ 7% |
| p75 TTFB · Server wait | 856 ms | 805 ms | ▼ 6% |
| p75 LCP · Load time | 724 ms | 762 ms | ▲ 5% |
| Avg engaged time | 31.2 s | 32.8 s | ▲ 5% |
| p75 LCP · Render delay | 522 ms | 497 ms | ▼ 5% |
| p75 FCP | 1.85 s | 1.78 s | ▼ 4% |
| p75 LCP · Load delay | 721 ms | 746 ms | ▲ 4% |