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

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


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

android-one

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973342411902705232

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstMeaningfulPaint_avg/Regular-3G/KapanLagi

Revision             Result                  N
chromium@487768      10030.2 +- 1209.27      21      good
chromium@487823      10017.2 +- 958.289      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=KapanLagi loading.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973342411902705232


For feedback, file a bug with component Speed>Bisection

Bisect couldn't reproduce and these came back down eventually.