Features

Page speed vs conversion

On this page

Turn on Page speed and MetricRaven measures how fast each page loads for your real visitors. You see it next to each page's conversion, and Pages → Details, the API, CLI and MCP server list the pages where slow loads go with fewer buyers.

What you see

WhereWhat
Pages → view allTwo columns after the purchase rate: LCP (when the main content showed) and INP (how quickly the page answered clicks and taps), each at the 75th percentile with a green, amber or red dot. Hover a value for CLS, FCP, TTFB and how many page loads it is based on. Entry pages show the same columns. Below 768 px one dot shows the worse of the two ratings; INP shows from 1024 px (from 1280 px while Scroll depth is on, so the page names keep room).
Traffic → Pages → Details, API, CLI and MCPSlow pages that lose buyers: for each page, how many visitors had a slow load, the share of them who paid, the share of visitors with a fast load who paid, and the buyers that gap suggests were lost, with LCP and INP at the 75th percentile. Up to 10 pages, most buyers lost first. In the dashboard, open Pages → Details and choose See slow pages that lose buyers under the list's controls (it shows once the speed columns do; click a page to filter by it). Also GET /stats/page-speed, analytics speed and get_page_speed.

Both follow the period and filters you choose, and show on share links and embeds wherever Pages shows (the slow pages list where the link also shows revenue, since it compares purchase rates). They are aggregates: no visitor is named.

Turn it on

  1. Open Settings → Tracking & install → Advanced → Page speed

    It is off until you turn it on. Admins and the owner can change it.

  2. Switch on Page speed (Web Vitals)

    It saves at once. Pages pick it up on their next load; nothing changes in your snippet.

  3. Wait for page loads

    A page needs 10 page loads in the period before its numbers show, and the slow pages list needs 30 slow and 30 fast visitors on a page.

How it works

Measuring

  • When the setting is on, the tracker loads a small add-on, /js/addons/vitals.js (about 3 KB compressed), from the same place as the script. Sites without the setting never load it.
  • The add-on uses Google's open-source web-vitals library. When the visitor leaves the page or switches tab, it sends one snapshot for that page load: LCP, INP, CLS, FCP and TTFB, as far as the browser measured them. Nothing is stored in the browser.
  • Each page's numbers are the 50th, 75th and 90th percentile of its snapshots in the period. The columns show the 75th: three in four page loads were at least this fast, the figure Google uses.

Ratings

MetricGood / poor
LCP (Largest Contentful Paint)Good at 2.5 s or less, poor over 4.0 s
INP (Interaction to Next Paint)Good at 200 ms or less, poor over 500 ms
CLS (Cumulative Layout Shift)Good at 0.10 or less, poor over 0.25
FCP (First Contentful Paint)Good at 1.8 s or less, poor over 3.0 s
TTFB (Time to First Byte)Good at 800 ms or less, poor over 1.8 s

In between is amber, needs improvement. These are Google's published thresholds.

Slow pages that lose buyers

  • A visitor had a slow load of a page when any of their loads of it had a poor LCP (over 4 s) or a poor INP (over 500 ms).
  • A visitor had a fast load when every load of it had a good LCP (2.5 s or less) and a good INP (200 ms or less). A missing measurement counts as good. Visitors in between are in neither group.
  • A visitor paid when they made a positive payment in the period, the same paying visitors as the Purchase rate tile. Revenue isn't split here, so the first-visit crediting rule doesn't apply.
  • Buyers lost = slow visitors × (fast purchase rate − slow purchase rate). Pages are listed only when fast loads paid more often, most buyers lost first, up to 10.
  • Slow loads often come with slower devices and networks, which also change how people buy. Treat a row as a lead to look into, not proof that speed caused it.

Limits

  • Snapshots are kept 90 days, then deleted.
  • A page needs 10 page loads in the period; the slow pages list needs 30 slow and 30 fast visitors per page.
  • At most 50,000 snapshots per website per day (UTC); later ones that day are ignored.
  • In single-page apps the snapshot belongs to the first page of the page load; route changes after it aren't measured separately.
  • Snapshots don't count toward your monthly events. Page speed is on every plan.
  • Some ad blockers block the add-on when it loads from metricraven.com. Serving it through your own domain (the managed proxy or your proxy) avoids that.
  • Browsers that don't measure a metric leave it out of the snapshot; the others still count.

Troubleshooting

No LCP or INP columns in Pages

The setting is off, or the site has no snapshots yet. A page with fewer than 10 loads shows —. Turn on data-debug and leave a page: the console shows Sending vitals.

Behind your own proxy

With a managed proxy nothing changes: it serves the add-ons too. With your own proxy the add-on loads from metricraven.com unless you forward /js/addons/* and add data-addons="/a/addons/" to the script tag; see Proxy. Data always goes to your proxied collect endpoint.

Content Security Policy

The add-on comes from the same host as the script, so no new directive is needed. The script passes its nonce on; see Content Security Policy.

Through the API, add include=speed to GET /stats/breakdown or read GET /stats/page-speed; AI assistants use get_page_speed, and the CLI metricraven analytics speed.