RESOLVED CONFIGURATION CHANGED 169863
Webkit Inspector Slow to Initially Load 
https://bugs.webkit.org/show_bug.cgi?id=169863
Summary Webkit Inspector Slow to Initially Load
Chris Chiera
Reported 2017-03-19 11:55:02 PDT
This is not an issue about Safari/Webkit page loading, but rather Safari/Webkit Inspector/DevTools Loading. In past years, the inspector always opened up relatively instantly. Chrome may have had a slightly edge but don't believe was noticeable. A year or so ago (don't quote me), all of the sudden when opening the Inspector it would open right away, but the html section would be blank for about 8-9 seconds and then it would all appear at once. This issue has continued. I switched back to Chrome since there it opens in roughly 1-2 seconds. Occurs on all different pages, for example apple.com or google.com. Have tried in Safari, Safari Beta, and Webkit Nightly all the same issue. Have tried in icognito mode (no extensions) and regular mode no extensions, made same slow loading. When I got a new MBP, same issue, as well as when on my new iMac 32GB ram same issue (albeit a little faster there). On all computers Chrome inspector loads near instantly. Can someone confirm if when they open say Apple.com and then open inspector if it loads the html right away (1-2 seconds) like Chrome, or if the slow loading 8ish seconds for inital html load is happening for everyone? To note have a 220MBps connection here and the websites themselves load near instantly in all browsers. If this issue is unique to me and my computers would love to get to the bottom of why it's occurring.
Attachments
Add attachment proposed patch, testcase, etc.
Chris Chiera
Comment 1 2017-03-20 18:24:27 PDT
While this issue has persisted the past year or two on multiple machines of mine. Reformated my Mac and this time didn't login as my Apple ID during setup and Safari Inspector is loading fast again. So assuming iCloud must have been syncing some sort of corrupt setting causing the issue. If discover again will reopen.
Note You need to log in before you can comment on or make changes to this bug.