All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=893623

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=0b6753357f679eea788bdfa2facc35e60d8410b638def61ba4c4d5476ce9acb3


Bot(s) for this bug's original alert(s):

linux-perf

loading.desktop - Benchmark documentation link:
  https://bit.ly/loading-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/174e8cd4e40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/174e8cd4e40000

[Password Manager] Get All Logins With Affiliation Info by jdoerrie@chromium.org
https://chromium.googlesource.com/chromium/src/+/9e057b75d8e0ca01ecbeead1a4553815527aedc7
timeToFirstContentfulPaint: 105.4 → 93.31 (-12.09)

Roll src/third_party/catapult 4fc4281d2152..9ec8468cfde0 (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/f80143088ca19a0af1fb3dd75e8503031ebaed25
timeToFirstContentfulPaint: 92.15 → 123.4 (+31.2)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/loading-benchmarks

eyaich@: Do you know if http://crrev.com/c/1257270 is impacting some real timing here?  Or it's just a change in calculation?

Issue 893603 has been merged into this issue.

Yes this was a change in calucation of firstContentfulPaint