Slow Performance on HTTP PUT Calls via Chrome - performance

Question

I have an ASP.NET Web API that exposes all the verbs - the methods are basically empty.
To run the project, you can do this: spin up a new asp.net web project from VS 2017 - then choose Web API. Once the project is created, do a clean and then rebuild. Open up "ValuesController", put a break point inside the PUT method, and run your project.
Here are the code for the API (controller code - I added a line in PUT method):
public class ValuesController : ApiController
{
// GET api/values
public IEnumerable<string> Get()
{
return new string[] { "value1", "value2" };
}
// GET api/values/5
public string Get(int id)
{
return "value";
}
// POST api/values
public void Post([FromBody]string value)
{
}
// PUT api/values/5
public void Put(int id, [FromBody]string value)
{
var x = "value: " + value;
}
// DELETE api/values/5
public void Delete(int id)
{
}
}
I do not get the same problem or time difference (or they are very negligible) for other HTTP methods (GET, POST, DELETE).
GET timing data:
POST timing data:
DELETE timing data:
PUT timing data via IE:
Now - here is PUT timing data via CHROME:
I also have tried putting my API on a server - so calling the API would be a call to http://test-server-01/api/values/1 etc - but the same issue for PUT persist.
My question: Can anybody explain what is going on? Why is the call for PUT so slow compared to other VERBS? This only happens in Chrome too - I tried making the same calls in IE, resulting in much faster performance.
[UPDATED]
I did some timing gathering using Chrome Dev Tools and I noticed that most of th delay are happening on Slow Time to First Byte (TTFB). Here is a screen shot of one of my timing data:
[UPDATED MORE]
Here are some more timing data between IE vs Chrome without Fiddler. Timing is captured using respective developer tools.
The timing above is pretty much the average of multiple PUT calls in IE and in Chrome. Chrome always ~8 seconds and IE is about ~4 seconds.
As comparison, issuing a POST in IE and Chrome are resulting in negligible difference between them - they all resulting around ~20ms to ~50ms (although Chrome is almost always faster).
Making a DELETE call also similar to POST in result, ranging ~10ms to ~18ms (Chrome is almost always faster).
[UPDATE MORE MORE]
I tried creating an MCVE - but I cannot duplicate the issue on a different machine. I put the solution on a different laptop, run it using VS 2017, hit localhost via Chrome - no delay/poor performance calling PUT. The timing data that I gathered is on par or similar to POST or DELETE.
So it seems this problem is probably isolated to my work machine. Could it be network issue? Proxy? But if it is the case - should not all calls, including POST or DELETE or GET be delayed or getting poor performance as well? Or why is IE performing better for PUT - if the issue is related to network/proxy?
[UPDATE MORE MORE MORE]
I ran the PUT call via curl using bash - very fast, no delay whatsoever from the same machine that gave me 8 seconds with CHROME.