metric: First meaningful paint (1.0) about lighthouse HOT 11 CLOSED

Just a heads up: in the report.html, I get a -1 for Fast first paint of content (target value: 1,000ms ) - for airhorner.

from lighthouse.

We need to adopt firstContentfulPaint. This'll match tracing and also make airhorner work. :)

from lighthouse.

cc @brendankenny to poke into the negative values and filtering for main frame timings only.

from lighthouse.

Our phase 1 implementation using firstContentfulPaint landed.

Now that ksakamoto has finished the spec of first meaningful paint, based on the layout sizes, we will track our phase 2 implementation with this ticket.

Time to First Meaningful Paint: a layout-based approach

this doc includes link to draft implementation of trace-based fMP 1.0 in ruby: ttfmp.rb https://gist.github.com/irori/e5af3d2994f34b7a2a68ac596e5c9ceb

from lighthouse.

Did the initial port: master...paulirish:fmp1point0

However! This analysis relies on a few trace points that are not yet landed (https://codereview.chromium.org/1773633003), so we can't adopt it yet. I'll work with ksakamoto to move this forward.

from lighthouse.

Update from ksakamoto. He's landing half of his CL this week.
The second half (the fonts part) will have to wait until he returns from vacation (after May 8th). However the fonts part is something that we can calculate on our end, if need be, so it shouldn't be a problem. :)

update: https://codereview.chromium.org/1922823003/ frameID is in.

from lighthouse.

with this PR or just in general?

from lighthouse.

In general via the webstore extension, was commenting here because of the related title, oops

from lighthouse.

all good. this PR will fix the bug. but thank you. :)

from lighthouse.

Hello, wanted to ask when will this be available in chrome. will these metrics be exposed through js api, do we kno details

from lighthouse.

early work was done a while ago.
#618 picks up the remaining stuff.

from lighthouse.