This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 974
load time and loading indicator don't appear to measure the same thing #141
Comments
tried the same thing on forbes.com and didn't see any real discrepancy |
This provably means that the load start/ end are being fired more often. Or maybe it's related to us setting state on active tab somewhere instead of current tab. |
I have seen it "flicker" sometimes which makes sense with the multiple start/end firings. As a user my expectation would be that it starts and stops once per page load. |
maybe we should use 'did-navigate' and 'dom-ready' instead of start/stop loading? |
maybe, we want something that fires only once per page. If those fire once per iframe then we want diff ones, probably the ones you suggested. |
there are also a lot of other events that are not currently exposed, but would be easy to make available |
This was referenced Sep 15, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Load cnn.com and time how long the loading status indicator is activated (this is more noticeable if you turn ad blocking off)
Compare to the load time displayed in the url bar
There appears to be a significant discrepancy between them
The text was updated successfully, but these errors were encountered: