Chrome Version       : 62.0.3202.94
OS Version: OS X 10.12.6
URLs (if applicable) : http://localhost:7777/webClient
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: OK
    Firefox: OK
    IE/Edge: Not tested

What steps will reproduce the problem?
1. On a mac, run a node.js http server via the node.js module 'express' on some port, say 7777, that serves up a web client called 'webClient'.
2. Point Chrome to the URL http://localhost:7777/webClient.
3. If the router that the mac is connected to via wifi is NOT connected to the internet, the loading of 'webClient' can often take up to 10-15 seconds, and Chrome surfaces a 'resolving host' message in the bottom left of the screen, until the page actually loads.
4. If the router IS connected to the internet, this delay never happens.
5. Whenever this delay happens, pointing Safari or Firefox to the same URL always loads the page immediately.


What is the expected result?
That the page should load immediately (assuming the webClient is tiny, which it is in this case).


What happens instead of that?
The page often takes 10-15 seconds to load.


Please provide any additional information below. Attach a screenshot if
possible.
Happy to discuss this more if additional info is required! Thank you!!

UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36