ClickVitals /Shop & magazine (demo) Log in Sign up
Clear filters
Page views
91
7d
▼ 3% vs previous 7d
LCP · p75
2.05 s
81% good · 91 samples
± 0% vs previous 7d
INP · p75
288 ms
62% good · 68 samples
▲ 59% vs previous 7d
CLS · p75
0.02
89% good · 91 samples
▲ 5% vs previous 7d
FCP · p75
1.57 s
82% good · 91 samples
▲ 12% vs previous 7d
TTFB · p75
742 ms
77% good · 91 samples
▼ 21% vs previous 7d
Happy page views
55%
18% unhappy · 91 rated

13% 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

INP got 59% worse than the previous 7d
p75 INP is now 288 ms. The Vitals tab shows when it changed and which pages it changed on.
INP over time →
Taps and clicks on this element respond slowly
div.related-articles > a
p75 INP is 573 ms over 9 page views, mostly on /p/sku-0/. 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 →
People arriving from search get a slow first page
p75 LCP of the landing page is 2.64 s for 30 search visits, and 43% of them bounced. It's their first impression, and page experience is one of Google's ranking signals.
Landing pages →
Mobile visitors get a much slower INP
p75 INP is 407 ms on mobile against 173 ms on desktop. Mobile is 56% 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 →
Key presses in this element respond slowly
#search_input
p75 INP is 232 ms over 11 page views, mostly on /p/sku-0/. 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
#onetrust-accept-btn-handler
p75 INP is 229 ms over 16 page views, mostly on /p/sku-0/. 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 →
2 more findings
This element makes the page jump as it loads
header.site-header
p75 CLS is 0.17 on the 9 page views where it shifted, mostly on /p/sku-0/.
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
#onetrust-banner-sdk
p75 CLS is 0.11 on the 9 page views where it shifted, mostly on /p/sku-0/.
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 →

Based on 91 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

DevicePage viewsp75 LCPp75 INPp75 CLS
Mobile51 2.33 s 407 ms 0.01
Desktop33 1.37 s 173 ms 0.05
Tablet7 2.09 s 66 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.

LCPPage viewsClicks per viewEngaged timeAvg scroll
Good741.72 38.8 s59%
Needs improvement101.30 22.3 s68%
Poor70.43 9.3 s49%

Biggest changes vs previous 7d

MeasurePreviousNowChange
p75 TTFB · Connect34 ms65 ms ▲ 93%
p75 INP · Processing82 ms129 ms ▲ 59%
p75 INP181 ms288 ms ▲ 59%
p75 INP · Input delay45 ms72 ms ▲ 59%
p75 INP · Presentation54 ms86 ms ▲ 59%
p75 TTFB · TLS54 ms72 ms ▲ 33%
p75 LCP · Load time702 ms856 ms ▲ 22%
p75 TTFB940 ms742 ms ▼ 21%
p75 TTFB · Server wait738 ms606 ms ▼ 18%
Avg engaged time40.0 s34.7 s ▼ 13%
p75 FCP1.41 s1.57 s ▲ 12%
p75 LCP · Load delay566 ms614 ms ▲ 9%