![]() |
Websocket - Printable Version +- WebPagetest Forums (https://www.webpagetest.org/forums) +-- Forum: Web Performance (/forumdisplay.php?fid=3) +--- Forum: Testing Tools/Services (/forumdisplay.php?fid=6) +--- Thread: Websocket (/showthread.php?tid=13263) |
Websocket - milkanast - 09-29-2014 05:46 PM I choose the option of: Fully Loaded The Fully Loaded time is measured as the time from the start of the initial navigation until there was 2 seconds of no network activity after Document Complete. This will usually include any activity that is triggered by javascript after the main page loads. How did you detect 2 seconds of inactivity when between the age and the server I have an open web-socket ? RE: Websocket - pmeenan - 10-01-2014 11:04 PM WebPagetest sits between the browser and the network stack and watches for any reads/writes. If you have an open websocket but it is idle it won't trigger the activity monitor. RE: Websocket - shawn.siefkas@meredith.com - 04-27-2016 01:52 AM What if the socket isn't necessarily idle by design (i.e. push based messaging)? This seems to block test completion in some of our use cases. Is there a way to blacklist or ignore web socket connections during a test? Sorry to bump an old thread but it seems relevant. RE: Websocket - krauer - 07-19-2016 05:34 PM (04-27-2016 01:52 AM)shawn.siefkas@meredith.com Wrote: What if the socket isn't necessarily idle by design (i.e. push based messaging)? This seems to block test completion in some of our use cases. Is there a way to blacklist or ignore web socket connections during a test? Currently we are facing the same issue. The test does not finish because of the open socket. Is it possible to finish the test manually? I read something about Code: if( window.webpagetest ) Thanks! |