Open erakor opened 7 years ago
I see the same issue with Chrome 59 (on windows) as well
You should be able to get a decent approximation of first paint via the resource timing API, by using the maximum response end time out of all blocking CSS and script resources. I.e.
window.performance.getEntries("resource")
;initiatorType
of 'link' or 'script';startTime
later than window.performance.domInteractive
as they were not loaded statically and would not block first paint; andresponseEnd
of the remaining entries.
Hey, Currently, when browsing with Firefox,
firstPaint
is set to0
because, I believe, Firefox doesn't support anything to measure properly. Should that value be set tonull
instead of0
in that case?