ClickVitals /Shop & magazine (demo) Log in Sign up
Clear filters
Page views
648
30d
▲ 440% vs previous 30d
LCP · p75
2.63 s
72% good · 648 samples
▲ 10% vs previous 30d
INP · p75
281 ms
62% good · 407 samples
▲ 22% vs previous 30d
CLS · p75
0.03
90% good · 648 samples
▼ 11% vs previous 30d
FCP · p75
2.61 s
53% good · 648 samples
▲ 9% vs previous 30d
TTFB · p75
1.42 s
46% good · 648 samples
▲ 6% vs previous 30d
Happy page views
49%
17% unhappy · 648 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 78% fewer clicks than ones that loaded in under 2.5 s. Based on 70 slow page views across 1 page type.
Compare fast and slow page views →
INP got 22% worse than the previous 30d
p75 INP is now 281 ms. The Vitals tab shows when it changed and which pages it changed on.
INP over time →
/search/ pages are slow to show their main content
p75 LCP is 2.63 s over 648 full page loads; 11% 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 →
People arriving from search get a slow first page
p75 LCP of the landing page is 2.57 s for 182 search visits, and 31% of them bounced. It's their first impression, and page experience is one of Google's ranking signals.
Landing pages →
Taps and clicks on this element respond slowly
#onetrust-accept-btn-handler
p75 INP is 270 ms over 100 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 274 ms over 55 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 →
3 more findings
Key presses in this element respond slowly
#search_input
p75 INP is 258 ms over 62 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
header.site-header
p75 CLS is 0.11 on the 77 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 →
This element makes the page jump as it loads
ul.product-grid
p75 CLS is 0.11 on the 63 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

DevicePage viewsp75 LCPp75 INPp75 CLS
Mobile2.5k 2.63 s 244 ms 0.04
Desktop1.9k 2.01 s 151 ms 0.04
Tablet648 2.63 s 281 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.

LCPPage viewsClicks per viewEngaged timeAvg scroll
Good4641.64 32.6 s57%
Needs improvement1140.82 25.5 s63%
Poor700.36 14.8 s38%

Biggest changes vs previous 30d

MeasurePreviousNowChange
p75 TTFB · TLS80 ms101 ms ▲ 26%
p75 TTFB · Connect100 ms125 ms ▲ 25%
p75 INP · Presentation69 ms84 ms ▲ 22%
p75 INP · Processing104 ms126 ms ▲ 22%
p75 INP230 ms281 ms ▲ 22%
p75 INP · Input delay58 ms70 ms ▲ 22%
p75 LCP · Render delay1.10 s1.21 s ▲ 10%
p75 LCP2.40 s2.63 s ▲ 10%
Avg engaged time26.9 s29.4 s ▲ 9%
p75 FCP2.39 s2.61 s ▲ 9%
p75 HTML download155 ms166 ms ▲ 7%
p75 TTFB1.35 s1.42 s ▲ 6%