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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/Naver

Revision             Result                  N
chromium@491570      1241.48 +- 133.004      21      good
chromium@491694      1226.34 +- 22.6688      21      bad

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

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

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


For feedback, file a bug with component Speed>Bisection

bisect can't repro.