Page views
693
7d
▼ 4% vs previous 7d
LCP · p75
1.89 s
83% good · 693 samples
± 0% vs previous 7d
INP · p75
200 ms
75% good · 426 samples
▼ 3% vs previous 7d
CLS · p75
0.03
90% good · 693 samples
▼ 22% vs previous 7d
FCP · p75
1.58 s
81% good · 693 samples
▲ 5% vs previous 7d
TTFB · p75
852 ms
72% good · 693 samples
▲ 7% vs previous 7d
Happy page views
62%
14% unhappy · 693 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 65% less engaged time and 77% fewer clicks than ones that loaded in under 2.5 s. Based on 56 slow page views across 5 page types.
Compare fast and slow page views →
Tablet visitors get a much slower INP
p75 INP is 233 ms on tablet against 146 ms on desktop. Tablet is 15% 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.11 on the 74 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
nav.toc > a.toc-link
p75 INP is 260 ms over 55 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 →
/search/ pages are slow to show their main content
p75 LCP is 2.62 s over 66 full page loads; 6% 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
button.menu-toggle
p75 INP is 235 ms over 48 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 →
2 more findings
This element makes the page jump as it loads
#onetrust-banner-sdk
p75 CLS is 0.11 on the 47 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 →
All three Core Web Vitals pass
p75 LCP 1.89 s, INP 200 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 | 336 | 2.14 s | 227 ms | 0.04 |
| Desktop | 254 | 1.46 s | 146 ms | 0.02 |
| Tablet | 103 | 2.26 s | 233 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 | 572 | 1.69 | 36.2 s | 58% |
| Needs improvement | 65 | 0.82 | 21.6 s | 56% |
| Poor | 56 | 0.38 | 12.7 s | 39% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 TTFB | 795 ms | 852 ms | ▲ 7% |
| p75 LCP · Load time | 644 ms | 599 ms | ▼ 7% |
| p75 LCP · Load delay | 620 ms | 663 ms | ▲ 7% |
| Avg engaged time | 31.3 s | 33.0 s | ▲ 5% |
| p75 FCP | 1.51 s | 1.58 s | ▲ 5% |
| p75 LCP · Render delay | 425 ms | 438 ms | ▲ 3% |