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

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


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

android-nexus5X

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12be2d7f240000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12be2d7f240000

Roll src/third_party/catapult f989b62823cb..484f9f764dc5 (1 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/80863fcdfdb7ce776922a92a5e04c990ea814913
1.676e+04 → 3.29e+04 (+1.614e+04)

Assigning to sheriff sullivan@chromium.org because "Roll src/third_party/catapult f989b62823cb..484f9f764dc5 (1 commits)" is a roll.

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

The only CL in the roll is "2018-06-27 sarath.singapati@huawei.com Corrected the traffic settings to reflect the settings by devtool."

This slows down the network simulation (to make it accurate) which slowed down the page loading times; Working as intended.