Bug 223513
| Summary: | chromestatus.com very slow to load | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sam Sneddon [:gsnedders] <gsnedders> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, bfulgham, koivisto, simon.fraser, webkit-bug-importer, zalan |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | https://www.chromestatus.com/features | ||
Sam Sneddon [:gsnedders]
Locally, with r274641, we end up with three frames >1s, with 15.69s spent in layout between them. This is massively worse than page load in Chrome or Firefox.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
I cannot reproduce us being massively slower with a recent macOS beta. It's clearly slower than Chrome, but only by ~1 second until the page is fully rendered.
Radar WebKit Bug Importer
<rdar://problem/75885779>
Sam Sneddon [:gsnedders]
(In reply to Alexey Proskuryakov from comment #1)
> I cannot reproduce us being massively slower with a recent macOS beta. It's
> clearly slower than Chrome, but only by ~1 second until the page is fully
> rendered.
Caused by a content blocker extension, seemingly. Followed up on Radar until we decide whether it's a WebKit or a Safari issue.