Skip to main content

Why are some transactions not showing up in Web Vitals?

Issue

Browser JavaScript SDK tracing is on, and the Web Vitals dashboard shows some pages, but not every route appears in the list. Missing routes, SPA client-side navigations, pageload vs navigation transactions, and page loads without a Performance Score are common causes.

Applies To

  • All SaaS Customers and Self-Hosted Users

  • Tracing

  • Web Vitals

  • Browser JavaScript SDKs

Resolution

A route appears in the Web Vitals page list based only on initial page-load data. Client-side navigation transactions are not included.

  1. Check transaction.op (or span.op). If the route only has navigation transactions, it will not appear until Sentry receives a pageload event for that URL, either from a direct visit or a page refresh. For sample-count differences, see Why Web Vitals lists fewer sampled events than Transaction Summary.
    ​

  2. Open a matching pageload event. If a required Web Vital is missing, Sentry cannot assign a Performance Score, so the event is omitted from the samples list. See the browser support table. Scores are supported for Chrome, Firefox, Safari, Opera, and Edge on both desktop and mobile.
    ​

  3. Use the latest JavaScript SDK. If you're on the 7.x series, use 7.98.0 or later to ensure lcp and cls are captured.
    ​

  4. In Explore → Traces, search for:
    ​

    is_transaction:true span.op:pageload transaction:"/your_route"


    Confirm that the event contains the Web Vitals reported by the browser (ttfb, fcp, and, on Chromium-based browsers, often lcp and cls).

If scored pageloads for the route still do not appear, contact Sentry Support.

Related Articles
Did this answer your question?