Page views
1.1k
7d
▼ 13% vs previous 7d
LCP · p75
2.36 s
77% good · 1.1k samples
▼ 2% vs previous 7d
INP · p75
225 ms
71% good · 703 samples
▲ 4% vs previous 7d
CLS · p75
0.03
91% good · 1.1k samples
▲ 12% vs previous 7d
FCP · p75
2.33 s
62% good · 1.1k samples
▼ 2% vs previous 7d
TTFB · p75
1.25 s
53% good · 1.1k samples
▼ 2% vs previous 7d
Happy page views
59%
12% unhappy · 1.1k rated
11% 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 52% less engaged time and 82% fewer clicks than ones that loaded in under 2.5 s. Based on 76 slow page views across 1 page type.
Compare fast and slow page views →
Mobile visitors get a much slower LCP
p75 LCP is 2.65 s on mobile against 2.04 s 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.
LCP by device →
Tablet visitors get a much slower INP
p75 INP is 296 ms on tablet against 148 ms on desktop. Tablet is 12% 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 245 ms over 184 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
button.menu-toggle
p75 INP is 222 ms over 112 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
div.ad-slot
p75 CLS is 0.11 on the 112 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
Taps and clicks on this element respond slowly
div.related-articles > a
p75 INP is 236 ms over 84 page views, mostly on /search/. Most of the time goes on running the event handler. 3 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 →
Trend
By device
| Device | Page views | p75 LCP | p75 INP | p75 CLS |
|---|---|---|---|---|
| Mobile | 536 | 2.65 s | 277 ms | 0.03 |
| Desktop | 412 | 2.04 s | 148 ms | 0.03 |
| Tablet | 125 | 2.34 s | 296 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 | 825 | 1.65 | 33.9 s | 57% |
| Needs improvement | 172 | 0.97 | 23.3 s | 55% |
| Poor | 76 | 0.30 | 16.2 s | 38% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| Avg engaged time | 32.5 s | 30.9 s | ▼ 5% |
| p75 TTFB | 1.29 s | 1.25 s | ▼ 2% |
| p75 FCP | 2.39 s | 2.33 s | ▼ 2% |