Application Version (from "Chrome Settings > About Chrome"): 56.0.2924.18
Android Build Number (from "Android Settings > About Phone/Tablet"): LXI22.50-62
Device: Moto E

Steps to reproduce:

1) Put the device on a slow network (e.g., GIN-2gpoor)
2) Try to load any page.

Observed behavior: 

All the user sees is a blank screen with a static loading bar stuck at about 10% for a very long time (30 seconds or more).

Expected behavior: 

We need to drastically rethink the loading experience when Chrome is on a slow network. Even if the user has Flywheel enabled and will eventually get a Preview page, the period of time that elapses before *any* content is shown can be quite long.

Some ideas (though there may be others)...

- After a short (~4-5 sec) timeout with no network activity, acknowledge that the network is slow and suggest another action (e.g., offline content, load later, etc.)

- Animate the loading bar to make it clear that something is happening. Other browsers (e.g., UC Browser) "pulse" the loading bar instead of having it be a static blue line.

- Revise timeout thresholds on slow networks to, e.g., retry requests more quickly when it's likely that the connection is stalled.

See internal doc for more details on experiment:
https://docs.google.com/a/google.com/document/d/19ctmz25Dd4FsCUeFJeaIhWGBTENcVo5_KD626fRE4DM/edit?usp=sharing