Performance Monitoring uses traces to collect data about monitored processes in your app. A trace is a report that contains data captured between two points in time in your app.
For web apps, Performance Monitoring automatically collects a trace for each page of your app called a page load trace. Each page load trace collects the following default metrics:
first paint — A metric that measures the time between when the user navigates to a page and when any visual change happens
first contentful paint — A metric that measures the time between when a user navigates to a page and when meaningful content displays, like an image or text
domInteractive — A metric that measures the time between when the user navigates to a page and when the page is considered interactive for the user
domContentLoadedEventEnd — A metric that measures the time between when the user navigates to a page and when the initial HTML document is completely loaded and parsed
loadEventEnd — A metric that measures the time between when the user navigates to the page and when the current document's load event completes
first input delay — A metric that measures the time between when the user interacts with a page and when the browser is able to respond to that input
View data from page load traces in the On device tab of the Firebase console (learn more later on this page).
Definition of a page load trace
This trace measures several metrics about how the pages in your app load, specifically how long it takes to reach common loading points, like an a responsive app.
Page load traces help you track your app's core web vitals, like first contentful paint.
Metrics collected for page load traces
These traces are out-of-the-box traces, so you cannot add custom metrics or custom attributes to them.
First paint
This metric measures the time between when the user navigates to a page and when any visual change happens.
This metric is useful since the first paint signals to your users that the page is starting to load.
Starts when the user navigates to a page.
Stops when any visual change happens, including a background color change or a header loading.
First contentful paint
This metric measures the time between when a user navigates to a page and when meaningful content displays, like an image or text.
This metric is useful for insights into how soon your users see any of your app's actual content rather than just a new background color or header.
Starts when the user navigates to a page.
Stops immediately after the browser renders the first content from the DOM, including any text, image (including background images), non-white canvas, or SVG.
domInteractive
This metric measures the time between when the user navigates to a page and when the page is considered interactive for the user.
This metric is useful for insights into how soon your users can actually interact with elements in your app, like buttons and hyperlinks, rather than just seeing them on the screen. Note that this doesn't mean that the browser will respond to the interaction (for this metric, refer to first input delay trace).
Starts when the user navigates to a page.
Stops immediately before the user agent sets the current HTML document's readiness to "interactive".
domContentLoadedEventEnd
This metric measures the time between when the user navigates to a page and when the initial HTML document is completely loaded and parsed.
Starts when the user navigates to a page.
Stops immediately after the initial HTML document is completely loaded and parsed (
DOMContentLoaded), but this does not mean that stylesheets, images, and subframes are finished loading.
loadEventEnd
This metric measures the time between when the user navigates to the page and when the current document's load event completes.
This metric is useful for insights into how long it takes to load all your content, including stylesheets and images.
Starts when the user navigates to a page.
Stops immediately after the current HTML document's load event completes.
First input delay
This metric measures the time between when the user interacts with a page and when the browser is able to respond to that input.
This metric is useful since the browser responding to a user interaction gives your users their first impressions about the responsiveness of your app.
Starts when the user first interacts with an element on the page, like clicking a button or hyperlink.
Stops immediately after the browser is able to respond to the input, meaning that the browser isn't busy loading or parsing your content.
Note that to measure the first input delay metric, you need to add the polyfill library for this metric. For installation instructions, refer to the library's documentation.
Track, view, and filter performance data
Track key metrics in your dashboard
Add your key metrics to your dashboard to learn how they're trending. You can quickly identify regressions by seeing week-over-week changes or verify that recent changes in your code are improving performance.
To add a metric to your dashboard, go to the Performance dashboard in the Firebase console, then click the Dashboard tab. Click an empty metric card, then select an existing metric to add to your dashboard. Click on a populated metric card for more options, like to replace or remove a metric.
The dashboard shows collected metric data over time, both in graphical form and as a numerical percentage change.
Learn more about using the dashboard.
View all traces and their data
To view these traces, go to the Performance dashboard in the Firebase console, then click the On device tab.
From the On Device tab, you can click through various screens to explore a trace and
drill down into metrics of interest. On most pages, you can use the
- Filter by Page URL to view data for a specific page of your site
- Filter by Effective connection type to learn how a 3g connection impacts your app
- Filter by Country to make sure your database location isn't affecting a specific region
Learn more about viewing data for your traces.
Next Steps
Learn more about using attributes to examine performance data.
Learn more about how to track performance issues in the Firebase console.