title: Force Chrome to close/re-open all TCP/TLS connections when profiling with the Network Panel
body: <p>The Network Panel of Chrome's DevTools is great for seeing how long different requests took to load in. It profiles each request and <a href="https://web.archive.org/web/20160528002723/https://developers.google.com/web/tools/chrome-devtools/profile/network-performance/understanding-resource-timing" rel="nofollow noreferrer">reports how long different parts of the request took, including the time spent making the initial TCP connection and SSL handshake</a>:</p>
  <p><a href="https://i.stack.imgur.com/JRDtP.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/JRDtP.png" alt="" /></a><br />
  <sub>(source: <a href="https://developers.google.com/web/tools/chrome-devtools/profile/network-performance/imgs/resource-timing-data.png" rel="nofollow noreferrer">google.com</a>)</sub></p>
  <p>When I load a page the first time I see the time taken for the initial connection and SSL handshake. <strong>If I immediately reload the page I no longer see any time spent on the initial connection and SSL handshake.</strong> I assume this is because Chrome has held open the TCP connection from the previous requests and is re-using it. That's great for normal browsing, but it makes profiling the initial page load difficult.</p>
  <p>Is there any way I can force Chrome to not re-use any existing TCP/TLS connections and always make new ones?</p>
  <p>If not in Chrome, is there something I can do at the OS level to achieve this? I'm on Windows, if it makes a difference.</p>