Although we have metrics for First Contentful Paint for Firefox (Nightly), we're missing them for both Chrome release + Canary builds. We don't seem to need to enable a pref for it, so we should be able to just grab values from: ```chromeUserTiming.firstContentfulPaint``` - see https://wpt.stage.mozaws.net/result/190122_BR_13W/?f=json There are actually a few raw values available: ```firstContentfulPaint``` ```PerformancePaintTiming.first-contentful-paint``` (doesn't appear to round up/down) We can also see in the 2nd screenshot that our Fx-specific raw metric ```timeToContentfulPaint``` comes up ```null``` in Chrome, which makes sense. <img width="2032" alt="screen shot 2019-01-22 at 1 01 39 pm" src="https://user-images.githubusercontent.com/387249/51569380-111fed00-1e51-11e9-89ce-ef181b4377d7.png"> <img width="1327" alt="screen shot 2019-01-22 at 2 20 50 pm" src="https://user-images.githubusercontent.com/387249/51569406-24cb5380-1e51-11e9-9e78-d84586dcae6c.png">
Although we have metrics for First Contentful Paint for Firefox (Nightly), we're missing them for both Chrome release + Canary builds.
We don't seem to need to enable a pref for it, so we should be able to just grab values from:
chromeUserTiming.firstContentfulPaint- see https://wpt.stage.mozaws.net/result/190122_BR_13W/?f=jsonThere are actually a few raw values available:
firstContentfulPaintPerformancePaintTiming.first-contentful-paint(doesn't appear to round up/down)We can also see in the 2nd screenshot that our Fx-specific raw metric
timeToContentfulPaintcomes upnullin Chrome, which makes sense.