Page views
106
24h
▼ 44% vs previous 24h
LCP · p75
2.35 s
77% good · 106 samples
▼ 9% vs previous 24h
INP · p75
171 ms
81% good · 68 samples
▼ 34% vs previous 24h
CLS · p75
0.02
92% good · 106 samples
▼ 51% vs previous 24h
FCP · p75
2.33 s
60% good · 106 samples
▼ 10% vs previous 24h
TTFB · p75
1.25 s
49% good · 106 samples
▼ 14% vs previous 24h
Happy page views
67%
13% unhappy · 106 rated
14% 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
Slow page loads cost you engagement
Comparing like with like (the same page type), page views whose main content took over 4 s got 44% less engaged time and 63% fewer clicks than ones that loaded in under 2.5 s. Based on 11 slow page views across 1 page type.
Compare fast and slow page views →
People arriving from search get a slow first page
p75 LCP of the landing page is 2.77 s for 33 search visits, and 27% of them bounced. It's their first impression, and page experience is one of Google's ranking signals.
Landing pages →
Mobile visitors get a much slower LCP
p75 LCP is 2.85 s on mobile against 1.92 s on desktop. Mobile is 41% 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.
LCP by device →
Taps and clicks on this element respond slowly
button.menu-toggle
p75 INP is 365 ms over 13 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 →
Taps and clicks on this element respond slowly
nav.toc > a.toc-link
p75 INP is 315 ms over 7 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
#onetrust-banner-sdk
p75 CLS is 0.11 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 →
1 more finding
All three Core Web Vitals pass
p75 LCP 2.35 s, INP 171 ms, CLS 0.02: that's Google's "good" for each. Watch "Biggest changes" for regressions.
Vitals →
Based on 106 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 | 49 | 1.92 s | 117 ms | 0.03 |
| Mobile | 43 | 2.85 s | 183 ms | 0.00 |
| Tablet | 14 | 2.32 s | 357 ms | 0.05 |
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 | 82 | 1.73 | 31.5 s | 53% |
| Needs improvement | 13 | 0.77 | 29.5 s | 59% |
| Poor | 11 | 0.64 | 17.6 s | 44% |
Biggest changes vs previous 24h
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 CLS | 0.04 | 0.02 | ▼ 51% |
| p75 INP · Presentation | 78 ms | 51 ms | ▼ 34% |
| p75 INP · Processing | 117 ms | 77 ms | ▼ 34% |
| p75 INP | 260 ms | 171 ms | ▼ 34% |
| p75 INP · Input delay | 65 ms | 43 ms | ▼ 34% |
| p75 TTFB · Connect | 82 ms | 97 ms | ▲ 18% |
| p75 TTFB | 1.46 s | 1.25 s | ▼ 14% |
| p75 TTFB · Server wait | 1.22 s | 1.10 s | ▼ 10% |
| p75 FCP | 2.58 s | 2.33 s | ▼ 10% |
| p75 LCP | 2.59 s | 2.35 s | ▼ 9% |
| Avg engaged time | 28.3 s | 29.8 s | ▲ 5% |