WebPagetest Forums

Full Version: Websocket
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
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 ?
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.
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.
(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?

Sorry to bump an old thread but it seems relevant.

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 )
    window.webpagetest.done();
which we could inject to our javascript, but that just seems to work in IE. Any help is highly appreciated.

Thanks!
Reference URL's