198857 2019-06-14 04:12:06 -0700 [GTK] Some site is unbearably slow to load 2023-03-06 11:28:03 -0800 1 1 1 Unclassified WebKit WebKitGTK WebKit Local Build PC Linux RESOLVED WORKSFORME Gtk P3 Normal --- 245783 1 andrea.giammarchi webkit-unassigned bugs-noreply kdwkleung mcatanzaro nekohayo pnormand oldest_to_newest 1544741 0 andrea.giammarchi 2019-06-14 04:12:06 -0700 If I try to load https://twitter.com/WebKitGTK as example, it takes forever, and sometimes it finishes only after reloading it. I am on latest ArchLinux and GNOME 3.32.2, on Intel® Core™ i7-8565U CPU @ 1.80GHz × 8, and Intel® HD Graphics (Whiskey Lake 3x8 GT2), and 16GB of RAM. On Safari, everything is just fine, so I wonder if this issue is specific to the GTK port. Thanks. 1544746 1 mcatanzaro 2019-06-14 06:36:06 -0700 Probably bug #197558. *** This bug has been marked as a duplicate of bug 197558 *** 1544749 2 pnormand 2019-06-14 06:45:10 -0700 That Twitter page doesn't have videos, so unrelated to bug #197558 1544751 3 andrea.giammarchi 2019-06-14 06:53:44 -0700 Not only that, but I have no freezing issues, rather white page and no site whatsoever, it hangs for too long. True that it's hard to find other site with a similar issue, and the issue itself is quite intermittent. 1544999 4 andrea.giammarchi 2019-06-15 02:47:13 -0700 actually, opening https://extensions.gnome.org/ is super slow/problematic too 1939014 5 kdwkleung 2023-03-05 19:25:05 -0800 This issue can no longer be observed in the latest WebKitGTK. 1939105 6 mcatanzaro 2023-03-06 07:41:53 -0800 In my unscientific testing, it takes 4 seconds to load the tweet feed in Firefox but 12 seconds to do so in Epiphany Tech Preview, so that's really not looking very great to me. Andrea, are you still having trouble with https://twitter.com/WebKitGTK? 1939173 7 andrea.giammarchi 2023-03-06 10:47:18 -0800 GNOME Web works fine ... twitter itself had an issue with its Service Worker recently, so I wouldn't out the delay you are observing into WebKitGTK 1939189 8 mcatanzaro 2023-03-06 11:28:03 -0800 OK, let's close this then. Probably fixed sometime between when you reported it and now.