ClickVitals /Shop & magazine (demo) Log in Sign up
Clear filters
Page views
669
7d
▼ 8% vs previous 7d
LCP · p75
1.96 s
85% good · 669 samples
▼ 1% vs previous 7d
INP · p75
199 ms
75% good · 410 samples
▼ 15% vs previous 7d
CLS · p75
0.04
90% good · 669 samples
▲ 5% vs previous 7d
FCP · p75
1.55 s
83% good · 669 samples
▼ 1% vs previous 7d
TTFB · p75
857 ms
72% good · 669 samples
▼ 3% vs previous 7d
Happy page views
65%
11% unhappy · 669 rated

10% 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 54% less engaged time and 87% fewer clicks than ones that loaded in under 2.5 s. Based on 44 slow page views across 4 page types.
Compare fast and slow page views →
Tablet visitors get a much slower INP
p75 INP is 317 ms on tablet against 156 ms on desktop. Tablet is 10% 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 →
This element makes the page jump as it loads
header.site-header
p75 CLS is 0.11 on the 76 page views where it shifted, mostly on /.
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
div.ad-slot
p75 CLS is 0.10 on the 68 page views where it shifted, mostly on /.
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 →
Taps and clicks on this element respond slowly
button.menu-toggle
p75 INP is 200 ms over 61 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.add-to-cart
p75 INP is 208 ms over 58 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 →
2 more findings
Key presses in this element respond slowly
#search_input
p75 INP is 225 ms over 52 page views, mostly on /search/. Most of the time goes on running the event handler. 1 more slow element is 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 →
All three Core Web Vitals pass
p75 LCP 1.96 s, INP 199 ms, CLS 0.04: that's Google's "good" for each. Watch "Biggest changes" for regressions.
Vitals →

Trend

By device

DevicePage viewsp75 LCPp75 INPp75 CLS
Mobile322 2.18 s 227 ms 0.03
Desktop277 1.48 s 156 ms 0.04
Tablet70 2.34 s 317 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
Good5671.73 36.4 s57%
Needs improvement560.57 28.6 s58%
Poor460.24 18.2 s39%

Biggest changes vs previous 7d

MeasurePreviousNowChange
p75 INP · Processing106 ms89 ms ▼ 15%
p75 INP · Presentation70 ms60 ms ▼ 15%
p75 INP235 ms199 ms ▼ 15%
p75 LCP · Load delay671 ms598 ms ▼ 11%
Avg engaged time31.6 s34.5 s ▲ 9%
p75 LCP · Render delay486 ms461 ms ▼ 5%
p75 TTFB · Server wait650 ms618 ms ▼ 5%
p75 TTFB886 ms857 ms ▼ 3%
Avg scroll depth54%56% ▲ 3%
p75 LCP · Load time708 ms726 ms ▲ 3%