mozilla/wpt-api

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

Open

#228 opened on Jan 22, 2019

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Python (7 forks)auto 404
firefoxhelp wantedmetrics

Repository metrics

Stars
 (28 stars)
PR merge metrics
 (PR metrics pending)

Description

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.

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.