Bug 247748 – [SOUP] Network requests take very long time to complete on cnn.com

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: WebKitGTK

[Michael Catanzaro]

Created attachment 463480 [details]
Epiphany

I'm going to attach two screencasts. In the first screencast, I load cnn.com in today's Epiphany Tech Preview and time how long it takes. It needs about 33 seconds to finish loading.

In the second screencast, I load cnn.com in Firefox 106.0.1 and time how long it takes. It mostly finishes loading more or less instantly, almost before I'm able to start the timer, but let's say it required 3 seconds to load. (I accidentally took this screencast with uBlock Origin enabled, which might be a better adblocker than Epiphany's adblocker, but I repeated the test with it disabled and it didn't make much difference.)

So we seem to be 10x slower, which seems excessive. This issue is certainly not limited to cnn.com, but that seems like a good test case to us.

[Michael Catanzaro]

Created attachment 463481 [details]
Firefox

[Michael Catanzaro]

Created attachment 463482 [details]
Network timings in web inspector

This screenshot shows that WebKit is spending all its time in network requests. Everything else happens more or less immediately.

I also notice that the web inspector's timeline export feature is broken (the button is insensitive).

[Michael Catanzaro]

I'm not sure, but I suspect this may be related to bug #247057.

[Kdwk]

I'm not able to reproduce this on one of my machines with WebKitGTK 2.39.4. On my 2015 MacBook Pro with dual-core i5, cnn.com takes about 6 seconds to load only (still very slow but not 33 seconds long), FireFox takes around 2.5 seconds on the same machine.

However, my i7-9700 took 20 seconds to load cnn.com fully, although the website is usable and looks fully loaded long before that.

[Michael Catanzaro]

(In reply to kdwkleung from comment #4)
> However, my i7-9700 took 20 seconds to load cnn.com fully, although the
> website is usable and looks fully loaded long before that.

I just recorded 19 seconds, which matches your experience here.

I tried to take a second recording to see when the web page became usable, but the web inspector itself hung. I guess the inspector web process is unresponsive.

[Michael Catanzaro]

Much more detail in bug #251336.

*** This bug has been marked as a duplicate of bug 251336 ***