Bug 159611
| Summary: | 5 Second Delay on Page Load in iOS 10 and Sierra | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kevin MacLeod <Kevin> |
| Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | ap, beidson |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | Other | ||
Kevin MacLeod
In both the iOS 10 and Sierra betas and developer previews, Safari occasionally takes between 5 and 6 seconds to start loading webpages.
This delay doesn't occur on every page load, but it is consistently reproducible about 1/5 of the time.
Whether a content blocker is in use, whether I'm on Wifi or cellular, and whether or not JavaScript is disabled seem to have no effect on whether or not this lag occurs.
My own site, https://afterpad.com, exhibits the problem very consistently. The site itself is extremely lightweight, with very minimal CSS and JavaScript, and consistently loaded in less than a second before these latest updates.
I'd be happy to help diagnose what's happening here any way I can.
-Kevin
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Thank you for the bug report!
Could you please re-file it at <https://bugreport.apple.com>? The problem is not necessarily within WebKit, and different teams within Apple may want to contact you with their questions via the bugreport site.
I'll mark this as INVALID because it's not a bug that should be tracked in WebKit bugzilla at this point.
Brady Eidson
I asked Kevin to file it here after seeing him mention this on Twitter because - at the time - I thought it was also seen in Safari Technology Preview.
Kevin, did I misunderstand; Is it not also noticed on Safari Technology Preview?
If you have has been noticed in STP, we can treat it as a WebKit bug.
Brady Eidson
(Even if it truly is only seen on the Sierra beta, I'm not sure it's right to close the bugzilla without further exploration, as it still could very easily be WebKit specific)
Alexey Proskuryakov
Yes, we can always reopen this report if it's found to be a WebKit issue.