Page views
536
7d
▼ 10% vs previous 7d
LCP · p75
2.65 s
72% good · 536 samples
▲ 6% vs previous 7d
INP · p75
277 ms
65% good · 348 samples
▲ 6% vs previous 7d
CLS · p75
0.03
92% good · 536 samples
▲ 8% vs previous 7d
FCP · p75
2.64 s
56% good · 536 samples
▲ 6% vs previous 7d
TTFB · p75
1.42 s
48% good · 536 samples
▲ 3% vs previous 7d
Happy page views
51%
17% unhappy · 536 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 81% fewer clicks than ones that loaded in under 2.5 s. Based on 52 slow page views across 1 page type.
Compare fast and slow page views →
Visitors in IN wait a long time for the first byte
p75 TTFB is 1.81 s for 34 page loads from IN (6% of page views), against 815 ms in IT. Most of the time goes on waiting for the server.
Try: The server takes long to start sending the page: cache the HTML (at the CDN if you can) or speed up the code and database queries behind it.
TTFB by country →
People arriving from search get a slow first page
p75 LCP of the landing page is 2.54 s for 156 search visits, and 31% of them bounced. It's their first impression, and page experience is one of Google's ranking signals.
Landing pages →
/search/ pages are slow to show their main content
p75 LCP is 2.65 s over 536 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
#onetrust-accept-btn-handler
p75 INP is 241 ms over 98 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 307 ms over 51 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
Key presses in this element respond slowly
#search_input
p75 INP is 307 ms over 40 page views, mostly on /search/. 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
div.ad-slot
p75 CLS is 0.13 on the 46 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 | 536 | 2.65 s | 277 ms | 0.03 |
| Desktop | 413 | 2.03 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 | 384 | 1.78 | 33.3 s | 57% |
| Needs improvement | 100 | 0.90 | 22.2 s | 53% |
| Poor | 52 | 0.35 | 15.9 s | 40% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| Avg engaged time | 32.1 s | 29.5 s | ▼ 8% |
| p75 INP | 260 ms | 277 ms | ▲ 6% |
| p75 FCP | 2.48 s | 2.64 s | ▲ 6% |
| p75 LCP | 2.51 s | 2.65 s | ▲ 6% |
| p75 TTFB · Server wait | 1.10 s | 1.14 s | ▲ 4% |
| p75 TTFB | 1.38 s | 1.42 s | ▲ 3% |