Page views
487
7d
▼ 17% vs previous 7d
LCP · p75
6.47 s
23% good · 487 samples
▼ 11% vs previous 7d
INP · p75
286 ms
61% good · 317 samples
▲ 15% vs previous 7d
CLS · p75
0.03
91% good · 487 samples
▼ 21% vs previous 7d
FCP · p75
4.08 s
28% good · 487 samples
▼ 4% vs previous 7d
TTFB · p75
2.16 s
25% good · 487 samples
▼ 5% vs previous 7d
Happy page views
14%
56% unhappy · 487 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 55% less engaged time and 79% fewer clicks than ones that loaded in under 2.5 s. Based on 253 slow page views across 5 page types.
Compare fast and slow page views →
/articles/* pages are slow to show their main content
p75 LCP is 6.53 s over 287 full page loads; 51% took over 4 s. Most of the time goes on the image starting to load late.
Try: The browser finds the LCP image late: don't lazy-load it, give it fetchpriority="high", and make it discoverable in the HTML (or preload it).
LCP by page and element →
The server is slow to respond on /articles/*
p75 time to first byte is 1.88 s over 287 page loads, so nothing can appear before then. 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 breakdown →
People arriving from search get a slow first page
p75 LCP of the landing page is 6.33 s for 145 search visits, and 34% of them bounced. It's their first impression, and page experience is one of Google's ranking signals.
Landing pages →
/ pages are slow to show their main content
p75 LCP is 6.50 s over 50 full page loads; 68% took over 4 s. Most of the time goes on the image starting to load late.
Try: The browser finds the LCP image late: don't lazy-load it, give it fetchpriority="high", and make it discoverable in the HTML (or preload it).
LCP by page and element →
/p/* pages are slow to show their main content
p75 LCP is 7.14 s over 50 full page loads; 62% took over 4 s. Most of the time goes on the image starting to load late.
Try: The browser finds the LCP image late: don't lazy-load it, give it fetchpriority="high", and make it discoverable in the HTML (or preload it).
LCP by page and element →
7 more findings
The server is slow to respond on /
p75 time to first byte is 1.96 s over 50 page loads, so nothing can appear before then. 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 breakdown →
/search/ pages are slow to show their main content
p75 LCP is 6.45 s over 53 full page loads; 53% 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 →
The server is slow to respond on /p/*
p75 time to first byte is 2.20 s over 50 page loads, so nothing can appear before then. 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 breakdown →
/c/* pages are slow to show their main content
p75 LCP is 4.14 s over 47 full page loads; 28% 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 298 ms over 64 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 →
Taps and clicks on this element respond slowly
button.add-to-cart
p75 INP is 287 ms over 54 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 →
Taps and clicks on this element respond slowly
div.related-articles > a
p75 INP is 311 ms over 43 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 →
Trend
By device
| Device | Page views | p75 LCP | p75 INP | p75 CLS |
|---|---|---|---|---|
| Mobile | 487 | 6.47 s | 286 ms | 0.03 |
| Desktop | 374 | 4.59 s | 141 ms | 0.03 |
| Tablet | 126 | 6.75 s | 225 ms | 0.04 |
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 | 114 | 1.81 | 41.6 s | 60% |
| Needs improvement | 120 | 0.84 | 24.2 s | 56% |
| Poor | 253 | 0.35 | 17.5 s | 40% |
Biggest changes vs previous 7d
| Measure | Previous | Now | Change |
|---|---|---|---|
| p75 LCP · Load delay | 5.04 s | 3.64 s | ▼ 28% |
| p75 INP · Presentation | 75 ms | 86 ms | ▲ 15% |
| p75 INP · Processing | 112 ms | 129 ms | ▲ 15% |
| p75 INP | 249 ms | 286 ms | ▲ 15% |
| p75 TTFB · TLS | 158 ms | 176 ms | ▲ 12% |
| p75 LCP | 7.31 s | 6.47 s | ▼ 11% |
| p75 TTFB · DNS | 97 ms | 86 ms | ▼ 11% |
| p75 TTFB · Connect | 162 ms | 180 ms | ▲ 11% |
| p75 LCP · Load time | 1.87 s | 1.68 s | ▼ 10% |
| Avg engaged time | 22.5 s | 24.8 s | ▲ 10% |
| p75 TTFB · Server wait | 1.86 s | 1.68 s | ▼ 10% |
| Avg scroll depth | 46% | 49% | ▲ 6% |