Skip to content
This repository has been archived by the owner on Aug 18, 2021. It is now read-only.

Add Chrome's firstContentfulPaint user-timing metric (so we can correlate with Firefox's timeToContentfulPaint metric) #228

Open
stephendonner opened this issue Jan 22, 2019 · 0 comments
Assignees
Labels
firefox help wanted Extra attention is needed metrics

Comments

@stephendonner
Copy link
Contributor

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.

screen shot 2019-01-22 at 1 01 39 pm

screen shot 2019-01-22 at 2 20 50 pm

@stephendonner stephendonner added help wanted Extra attention is needed metrics firefox labels Jan 22, 2019
@stephendonner stephendonner self-assigned this Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
firefox help wanted Extra attention is needed metrics
Projects
None yet
Development

No branches or pull requests

1 participant