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

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


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

Android Nexus5 Perf
Android Nexus6 WebView Perf
android-nexus5x-perf

blink_perf.css - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

blink_perf.parser - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/127534a7640000

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

Roll AFDO from 71.0.3554.0_rc-r1 to 71.0.3555.0_rc-r1 by afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/4b8803051fc24556622b6c8532a7b7ba73f64a8d
1119 → 1280 (+161.2)

Remove LazyParseCSS runtime flag. by futhark@chromium.org
https://chromium.googlesource.com/chromium/src/+/9ee2fe62d03cec95fb69ae3ab915cc7a343ef8fe
1282 → 1242 (-40.07)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

Probably the AFDO one. Graphs changed later to what it was before or recovered.