Do you see the same behavior from any other locations? Looks like the CPU is running pretty hot during the test so it is hard to tell if it is really taking that long or if the browser is busy doing something else at the same time.

Second Patrick's observation. Bandwidth is also nil and only spikes up when the woff files finally get pulled. Maybe you have a JS bug? Try shuffling the JS scripts you have right before </body> to see if it shifts this delay gap.

(02-06-2016 07:59 AM)pmeenan Wrote: Do you see the same behavior from any other locations? Looks like the CPU is running pretty hot during the test so it is hard to tell if it is really taking that long or if the browser is busy doing something else at the same time.

Thanks for the reply. Same behaviour where ever I test.

(02-09-2016 06:37 AM)unixy Wrote: Second Patrick's observation. Bandwidth is also nil and only spikes up when the woff files finally get pulled. Maybe you have a JS bug? Try shuffling the JS scripts you have right before </body> to see if it shifts this delay gap.