Web vitals
Errors & feedback → Web vitals shows how fast your pages feel and what slow loads cost you. It uses the same snippet as error tracking: the browser reports each page's speed as the visitor leaves, and SnowAnalytics reads it at the 75th percentile, the value three quarters of page loads are at or under. It follows the date range and filters in the page header.
Until the first reports arrive, the page says Turn on error tracking and shows what it will fill. Browsers send vitals as visitors leave, so the first ones turn up within minutes of someone browsing your site.
The three vitals
| Vital | What it measures | Good | Poor |
|---|---|---|---|
| LCP, largest paint | How long the biggest thing on the page takes to appear. | 2.5 s or less | Over 4 s |
| INP, response to clicks | How long the page takes to react to a click or tap. | 200 ms or less | Over 500 ms |
| CLS, layout shift | How much the page jumps around while loading. | 0.1 or less | Over 0.25 |
A value between good and poor reads needs work. The page also records TTFB (time to first byte) and FCP (first paint) to explain slow loads.
Speed and money
The first section puts the three vitals as tiles, each with its p75, its status and its target. Under them, Speed and money buckets every load by how long it took: Under 1.5 s, 1.5 to 2.5 s, 2.5 to 4 s and Over 4 s. For each bucket it shows the share of visits and the conversion rate of those visits.
A line below spells out the gap, such as Visits slower than 4 s buy at 40% of the rate of visits under 1.5 s. The conversion needs a connected payment provider and payments linked to visits. Until a page load in the period has ended in one, the chart shows the share of page loads by load time instead, and a line under it links to connect Stripe or to link your payments.
Why the slowest page is slow
Why a page is slow takes the slowest page and splits its LCP into four parts:
| Part | What it is |
|---|---|
| Server response | Time until your server answered. |
| Waiting to load | Time between the answer and the browser asking for the largest element. |
| Download | Time to download that element, with its size. |
| Render | Time between the download and the element appearing. |
It names the largest element and the file behind it, and adds a one-line suggestion. If the largest file comes from another site that doesn't allow timing, the split is unknown.
By device compares LCP at the 75th percentile on desktop, mobile and tablet.
Pages
Pages lists the slowest pages with their visits and their LCP, INP and CLS at the 75th percentile with a status. Once a page load has ended in a payment, it also shows each page's conversion and If it were fast.
If it were fast is the extra revenue a month if the page's slow visits (LCP over 2.5 s) converted like its fast ones, at what a conversion on this page is worth. It is an estimate, and needs revenue data.
A page counts as slow when its LCP at the 75th percentile is over 2.5 seconds and it has at least 20 loads. Pages with fewer loads are listed but not called slow.
Get alerted
An alert rule can tell you when a page's LCP at the 75th percentile over the last hour passes a threshold you choose.