Page views
3
24h
▼ 50% vs previous 24h
LCP · p75
3.98 s
33% good · 3 samples
▲ 220% vs previous 24h
INP · p75
275 ms
67% good · 3 samples
▼ 62% vs previous 24h
CLS · p75
0.08
67% good · 3 samples
FCP · p75
1.69 s
67% good · 3 samples
▲ 29% vs previous 24h
TTFB · p75
937 ms
67% good · 3 samples
▲ 57% vs previous 24h
Happy page views
33%
33% unhappy · 3 rated
What to fix first
Key presses in this element respond slowly
#search_input
p75 INP is 275 ms over 3 page views, mostly on /articles/10/. 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 →
Based on 3 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 |
|---|---|---|---|---|
| Mobile | 2 | 4.59 s | 339 ms | 0.10 |
| Desktop | 1 | 740 ms | 60 ms | 0.00 |
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 | 0.00 | 42.0 s | 100% |
| Needs improvement | 1 | 1.00 | 30.2 s | 40% |
| Poor | 1 | 0.00 | 21.6 s | 17% |
Biggest changes vs previous 24h
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 LCP · Load delay | 376 ms | 1.96 s | ▲ 422% |
| p75 LCP · Load time | 328 ms | 1.12 s | ▲ 242% |
| p75 LCP | 1.24 s | 3.98 s | ▲ 220% |
| p75 LCP · Render delay | 444 ms | 62 ms | ▼ 86% |
| p75 TTFB · Connect | 39 ms | 8 ms | ▼ 80% |
| p75 TTFB · TLS | 42 ms | 9 ms | ▼ 79% |
| p75 TTFB · Server wait | 549 ms | 937 ms | ▲ 71% |
| p75 INP · Presentation | 217 ms | 82 ms | ▼ 62% |
| p75 INP | 723 ms | 275 ms | ▼ 62% |
| p75 INP · Input delay | 181 ms | 69 ms | ▼ 62% |
| p75 INP · Processing | 325 ms | 124 ms | ▼ 62% |
| p75 TTFB | 598 ms | 937 ms | ▲ 57% |