Analyzing Web Vitals Stored in Google Analytics
Published: November 8, 2020
Google Analytics is a convenient (free) place to store Web Vitals “field measurements”. The Google Chrome team has provided extensive instructions on how to do this.
When it comes to analyzing the data, the instructions are a bit more vague. If you spend some time trying to dig into the data, one thing will quickly become clear…the Google Analytics UI is not a good tool for this.
Here I’ll cover my approach, which involves extracting the data via the Google Analytics Reporting API and analyzing it with pandas.
Extracting the data
NOTE: This blog posts assumes have already created a Google API service account and it has been granted appropriate access for the Google Analytics Reporting API v4
Initially I began (and completed) writing my own script to do this in PHP. While it’s fairly simple to do this, there are also some CLI tools available. The most popular tool you’ll find is Google Analytics for Python, which also features a CLI. However it hasn’t been updated in a while and isn’t using Google Analytics v4.
gagocli is a decent alternative that uses v4 of the API and also has a CLI. Here’s an example command to fetch Web Vitals using
gagocli reports \ -a ~/service-account-credentials.json \ -start 2020-11-07 \ -end 2020-11-07 \ -view <<REDACTED>> \ -mets ga:avgEventValue \ -dims ga:eventAction,ga:eventLabel,ga:deviceCategory \ -max -1 | \ grep -E '(ga:|CLS|FID|LCP|FCP)' > web-vitals.csv
grep at the end is to filter out events other than Web Vitals or the header rows. A dimension filter would be a better way to do this, but
gago doesn’t currently support them.
Here’s a snippet of the output of this command.
ga:eventAction,ga:eventLabel,ga:deviceCategory,ga:avgEventValue CLS,1603565564853-2797512854296,desktop,322.0 CLS,1603823911817-3767336210138,desktop,0.0 CLS,1604157490353-2181475990414,desktop,0.0 CLS,1604244666344-8342106718758,desktop,0.0 CLS,1604244741729-1832161271177,desktop,0.0 CLS,1604255076403-6728536556600,desktop,0.0 CLS,1604258490934-2627169605613,desktop,121.0 CLS,1604364536338-3079300975286,desktop,0.0
As you can see since we used
ga:deviceCategory as a dimension, we can analyze by device type. A full list of dimensions are available here. Another recommendation is to set up Content Grouping. This will allow you to analyze specific page types via the
Analyzing the data
Initially I had wanted to use Excel Pivot Tables for this, however I quickly learned that Excel doesn’t support percentile values in Pivot Tables. I tried a few other spreadsheet tools without any luck…
- Google Sheets: Supports median (which Excel doesn’t) but no way to get 75th percentile (which is recommended benchmark by Google)
- Apple Numbers: Had never used it, but couldn’t even get it to load all the data (I guess it only supports ~6K rows)
- OpenOffice Calc: Don’t even ask…
While I could obviously write a script to parse the data and extract the percentiles it seemed like not the best solution. I wanted something flexible and I didn’t want to have to re-invent the wheel.
I had recently been playing around with
pandas while watching some machine learning videos and decided to give it a try. It turned out to be the perfect tool for the job (specifically
pandas.DataFrame.pivot_table). Here’s a quick script to get the median and 75th percentile for each Web Vitals metric…
import pandas as pd import numpy as np def my75(g): return np.percentile(g, 75) df = pd.read_csv("web-vitals.csv") table = pd.pivot_table( df, values='ga:avgEventValue', index=['ga:eventAction'], aggfunc=[np.median, my75] ) print (table)
Additional columns can be added to
index to further segment the data.