In this codelab, you'll learn how to use Firebase Performance Monitoring to measure the performance of a chat web app. Visit https://fireperf-friendlychat.web.app/ to see a live demo.

What you'll learn

• How to add Firebase Performance Monitoring to your web app to get out-of-the-box metrics (page load and network requests).
• How to measure a specific piece of code with custom traces.
• How to record additional, custom metrics tied to a custom trace.
• How to further segment your performance data with custom attributes.
• How to use the performance monitoring dashboard to understand your web app's performance.

What you'll need

• The IDE or text editor of your choice, such as WebStorm, Atom, Sublime, or VS Code
• The package manager npm, which typically comes with NodeJS
• A terminal/console
• A browser of your choice, such as Chrome
• The codelab's sample code (See the next section of this codelab for how to get the code.)

Clone the codelab's GitHub repository from the command line:

git clone https://github.com/firebase/friendlychat-web

Alternatively, if you do not have git installed, you can download the repo as a zip file.

Import the starter app

Using your IDE, open or import the 📁 performance-monitoring-start directory from the cloned repository. This 📁 performance-monitoring-start directory contains the starting code for the codelab, which is a chat web app.

Add Firebase to the project

1. In the Firebase console, click Add Project.
2. Select the existing project using the dropdown.
3. Click Add Firebase.

Add a Firebase web app to the project

1. Click the web icon to create a new Firebase web app.
2. Register the app with the nickname Friendly Chat, and then check the box next to Also set up Firebase Hosting for this app.
3. Click Register app.
4. Click through the remaining steps. You don't need to follow the on-screen instructions now; these will be covered in later steps of this codelab.

Enable Google sign-in for Firebase authentication

To allow users to sign in to the chat app with their Google accounts, we'll use the Google sign-in method.

You'll need to enable Google sign-in:

1. In the Firebase console, locate the Develop section in the left panel.
2. Click Authentication, then click the Sign-in method tab (go to console).
3. Enable the Google sign-in provider, and then click Save.

Enable Cloud Firestore

The web app uses Cloud Firestore to save chat messages and receive new chat messages.

You'll need to enable Cloud Firestore:

1. In the Firebase console's Develop section, click Database.
2. Click Create database in the Cloud Firestore pane.
3. Select the Start in test mode option, then click Enable after reading the disclaimer about the security rules.

The starter code for this codelab includes more secure rules. We'll deploy them later in the codelab.

Enable Cloud Storage

The web app uses Cloud Storage for Firebase to store, upload, and share pictures.

You'll need to enable Cloud Storage:

1. In the Firebase console's Develop section, click Storage.
2. Click Get Started.
3. Read the disclaimer about security rules for your Firebase project, and then click Got it.

The starting code includes a basic security rule, which we'll deploy later in the codelab.

The Firebase command-line interface (CLI) allows you to use Firebase Hosting to serve your web app locally as well as to deploy your web app to your Firebase project.

1. Install the CLI by running the following npm command:

npm -g install firebase-tools

2. Verify that the CLI has been installed correctly by running the following command:

firebase --version

Make sure that your version of the Firebase CLI is v4.1.0 or later.

3. Authorize the Firebase CLI by running the following command:

firebase login

We've set up the web app template to pull your app's configuration for Firebase Hosting from your app's local directory (the repository that you cloned earlier in the codelab). But to pull the configuration, we need to associate your app with your Firebase project.

4. Make sure that your command line is accessing your app's local performance-monitoring-start directory.

5. Associate your app with your Firebase project by running the following command:

firebase use --add

6. When prompted, select your project ID, and then give your Firebase project an alias.

An alias is useful if you have multiple environments (production, staging, etc). However, for this codelab, let's just use the alias of default.

7. Follow the remaining instructions in your command line.

There are various ways to integrate with the Firebase Performance Monitoring SDK for web (refer to the documentation for details). In this codelab, we'll enable performance monitoring from Hosting URLs.

Add performance monitoring and initialize Firebase

1. Open the public/index.html file, then add the following line below the TODO to include the Firebase Performance Monitoring SDK.

index.html

<!-- TODO: Import the Firebase Performance Monitoring library here. -->
<script src="/__/firebase/6.4.0/firebase-performance.js"></script>

2. We also need to initialize the Firebase SDK with a configuration object that contains information about the Firebase project and the web app we want to use. Since we're using Firebase Hosting, you can import a special script that will do this configuration for you. For this codelab, we've already added the following line for you at the bottom of the public/index.html file, but double-check that it is there.

index.html

<script src="/__/firebase/init.js"></script>

3. In the public/scripts/main.js file, add the following line below the TODO to initialize performance monitoring.

main.js

// TODO: Initialize Firebase Performance Monitoring.
firebase.performance();

Performance Monitoring will now automatically collect page load and network request metrics for you when users use your site! Refer to the documentation to learn more about automatic page load traces.

Add the first input delay polyfill library

First input delay is useful since the browser responding to a user interaction gives users their first impressions about the responsiveness of your app.

First input delay starts when the user first interacts with an element on the page, like clicking a button or hyperlink. It stops immediately after the browser is able to respond to the input, meaning that the browser isn't busy loading or parsing your content.

This polyfill library is optional for performance monitoring integration.

Open the public/index.html file, then uncomment the following line.

index.html

<!-- TODO: Enable First Input Delay polyfill library. -->
<script type="text/javascript">!function(n,e){var t,o,i,c=[],f={passive:!0,capture:!0},r=new Date,a="pointerup",u="pointercancel";function p(n,c){t||(t=c,o=n,i=new Date,w(e),s())}function s(){o>=0&&o<i-r&&(c.forEach(function(n){n(o,t)}),c=[])}function l(t){if(t.cancelable){var o=(t.timeStamp>1e12?new Date:performance.now())-t.timeStamp;"pointerdown"==t.type?function(t,o){function i(){p(t,o),r()}function c(){r()}function r(){e(a,i,f),e(u,c,f)}n(a,i,f),n(u,c,f)}(o,t):p(o,t)}}function w(n){["click","mousedown","keydown","touchstart","pointerdown"].forEach(function(e){n(e,l,f)})}w(n),self.perfMetrics=self.perfMetrics||{},self.perfMetrics.onFirstInputDelay=function(n){c.push(n),s()}}(addEventListener,removeEventListener);</script>

At this point, you've finished the integration with Firebase Performance Monitoring in your code!

In the following steps, you learn about adding custom traces using Firebase Performance Monitoring. If you only want to collect the automatic traces, go to the "Deploy and start sending images" section.

Performance Monitoring allows you to create custom traces. A custom trace is a report for the duration of an execution block in your app. You define the start and end of a custom trace using the APIs provided by the SDK.

1. In the public/scripts/main.js file, get a performance object, then create a custom trace for uploading an image message.

main.js

// TODO: Create a custom trace to monitor image upload.
const trace = firebase.performance().trace('saveImageMessage');

2. To record a custom trace, you need to specify the starting point and stopping point for the trace. You can think of a trace as a timer.

main.js

// TODO: Start the "timer" for the custom trace.
trace.start();

 ...

    // TODO: Stop the "timer" for the custom trace.
    trace.stop();

You have successfully defined a custom trace! After deploying your code, the duration of the custom trace will be recorded if a user sends an image message. This will give you an idea of how long it takes real-world users to send images in your chat app.

You can further configure a custom trace to record custom metrics for performance-related events that occur within its scope. For example, you can use a metric to investigate if the upload time is affected by the size of an image for the custom trace we defined in the last step.

1. Locate the custom trace from the previous step (defined in your public/scripts/main.js file).
2. Add the following line below the TODO to record the size of the uploaded image.

main.js

 ...

// TODO: Record image size.
trace.putMetric('imageSize', file.size);

 ...

This metric enables performance monitoring to record the custom trace duration as well as the uploaded image size.

Building on the previous steps, you can also collect custom attributes on your custom traces. Custom attributes can help in segmenting data by categories specific to your app. For example, you can collect the image file's MIME type to investigate how the MIME type might affect the performance.

1. Use the custom trace defined in your public/scripts/main.js file.
2. Add the following line below the TODO to record the MIME type of the uploaded image.

main.js

 ...

// TODO: Record image MIME type.
trace.putAttribute('imageType', file.type);

 ...

This attribute enables performance monitoring to categorize the custom trace duration based on uploaded image type.

The Firebase Performance Monitoring SDK was designed so it could be loaded asynchronously, and so it wouldn't negatively impact the performance of web apps during page load. Before the SDK is loaded, the Firebase Performance Monitoring API is not available. In this scenario, you are still able to add custom traces by using the User Timing API. Firebase performance SDK will pick up the durations from measure() and log them as custom traces.

We are going to measure the duration of loading app styling scripts using User Timing API.

1. In the public/index.html file, add the following line to mark the start of the app styling scripts load.

index.html

<!-- TODO: Mark the starting of `timer` for loading App Styling script. -->
<script type="text/javascript">performance && performance.mark('loadStylingStart');</script>

2. Add the following lines to mark the end of the app styling scripts load, and to measure the duration between start and end.

index.html

<!-- TODO: Mark the ending of `timer` for loading App Styling script. Measure the duration from start to end. -->
<script type="text/javascript">
  performance && performance.mark('loadStylingEnd');
  performance && performance.measure('loadStyling', 'loadStylingStart', 'loadStylingEnd');
</script>

The entry you have created here will be automatically collected by Firebase Performance Monitoring. You will be able to find a custom trace called loadStyling in the Firebase Performance console later.

Deploy to Firebase Hosting

After adding Firebase Performance Monitoring to your code, follow these steps to deploy your code to Firebase Hosting:

1. Make sure that your command line is accessing your app's local performance-monitoring-start directory.
2. Deploy your files to your Firebase project by running the following command:

firebase deploy

3. The console should display the following:

=== Deploying to 'friendlychat-1234'...

i  deploying firestore, storage, hosting
i  storage: checking storage.rules for compilation errors...
✔  storage: rules file storage.rules compiled successfully
i  firestore: checking firestore.rules for compilation errors...
✔  firestore: rules file firestore.rules compiled successfully
i  storage: uploading rules storage.rules...
i  firestore: uploading rules firestore.rules...
i  hosting[friendlychat-1234]: beginning deploy...
i  hosting[friendlychat-1234]: found 8 files in ./public
✔  hosting[friendlychat-1234]: file upload complete
✔  storage: released rules storage.rules to firebase.storage/friendlychat-1234.appspot.com
✔  firestore: released rules firestore.rules to cloud.firestore
i  hosting[friendlychat-1234]: finalizing version...
✔  hosting[friendlychat-1234]: version finalized
i  hosting[friendlychat-1234]: releasing new version...
✔  hosting[friendlychat-1234]: release complete

✔  Deploy complete!

Project Console: https://console.firebase.google.com/project/friendlychat-1234/overview
Hosting URL: https://friendlychat-1234.firebaseapp.com

4. Visit your web app that's now fully hosted using Firebase Hosting at two of your very own Firebase subdomains: https://<projectId>.firebaseapp.com and https://<projectId>.web.app.

Verify that performance monitoring is enabled

1. Open your browser's developer tools, and open the Network tab. (instructions for Chrome)
2. Click Search . (instructions for Chrome)
3. Search for https://firebaselogging.googleapis.com/, which is the endpoint for receiving performance events. Find the request highlighted in the following screenshot.

4. Verify that the request was sent successfully. (Look for Status Code 200.)

Send image message

1. After signing in to your chat app, click the image upload button .
2. Select an image file using the file picker.
3. Try sending multiple images (a few samples are stored in public/images/) so that you can test the distribution of custom metrics and custom attributes.

New messages should display in the app's UI along with your selected images.

After deploying your web app and sending image messages as a user, you can review performance data in the performance monitoring dashboard (in the Firebase console).

Access your dashboard

1. In the Firebase console, select the project that has your Friendly Chat app.
2. In the left panel, locate the Quality section, and click Performance.

Review on-device data

After performance monitoring has processed your app's data, you'll see tabs along the top of the dashboard. Make sure to check back later if you don't see any data or tabs yet.

1. Click the On device tab.

• The Page loads table shows the various performance metrics that performance monitoring automatically collects while your page is loading.
• The Durations table shows any custom traces that you've defined in your app's code.

2. Click saveImageMessage in the Durations table to review specific metrics for the trace.

3. Click Aggregate to review the distribution of image sizes. You can see the metric you added to measure the image size for this custom trace.

4. Click Over time which is next to Aggregate in the previous step. You can also view the Duration of the custom trace. Click View more to review the collected data in more detail.

5. In the page which opens, you can segment the duration data by image MIME type by clicking imageType. This specific data was logged because of the imageType attribute you added to your custom trace.

Review network data

An HTTP/S network request is a report that captures the response time and payload size of network calls.

1. Go back to the main screen of the performance monitoring dashboard.
2. Click the Network tab to see a list of network request entries for your web app.
3. Browse through them to identify slow requests and start working on a fix to improve your app's performance!

You have enabled the Firebase SDK for performance monitoring and collected automatic traces and custom traces to measure the real-world performance of your chat app!

What we've covered:

• Adding the Firebase Performance Monitoring SDK to your web app.
• Adding custom traces to your code.
• Recording custom metrics tied to the custom trace.
• Segmenting performance data using custom attributes.
• Understanding how to use the performance monitoring dashboard to gain insights into your app's performance.

Learn more:

• firebase.google.com
• firebase.google.com/docs/perf-mon/get-started-web