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 972
Performance : 0.13.0 page load tracking issue #6836
Labels
Comments
manual runs were somewhat inconclusive. only 0.13.0 rc5 with shields down was an outlier for poor performance automation would certainly help so that we can track values over time |
some sites which could stand to load faster : alipay - #3603 |
moving to next milestone since no more work will be done for this one, too risky |
I added |
the milestone was reset to 0.13.3 |
luixxiul
added
needs-investigation
A bug not 100% confirmed/fixed that needs QA to better audit.
and removed
release-notes/include
labels
May 28, 2017
35 tasks
Needs breakdown to more discrete issues. |
all of the prior mentioned PRs have landed, this was only staying open as a string-on-finger reminder of automation work to be done re: page perf. |
luixxiul
removed
the
needs-investigation
A bug not 100% confirmed/fixed that needs QA to better audit.
label
Oct 30, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Did you search for similar issues before submitting this one?
yes
Describe the issue you encountered:
page loads appear to be slower
Platform (Win7, 8, 10? macOS? Linux distro?):
all, primary testing on os x
win coverage needed
Brave Version (revision SHA):
0.13.0 rc5
Steps to reproduce:
try this once with brave and once with chrome
Process 1. default shields, start timer, with one tab, open these sites in order :
a. facebook.com
b. wikipedia.org
c. amazon.com
d. twitter.com
e. qq.com
f. taobao.com
g. linkedin.com
h. outlook.com (log into site and load inbox)
Process 2. shields down, start timer, with one tab, open these sites in order :
a. facebook.com
b. wikipedia.org
c. amazon.com
d. twitter.com
e. qq.com
f. taobao.com
g. linkedin.com
h. outlook.com (log into site and load inbox)
Actual result:
Expected result:
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Is this an issue in the currently released version?
Can this issue be consistently reproduced?
Extra QA steps:
1.
2.
3.
Screenshot if needed:
Any related issues:
The text was updated successfully, but these errors were encountered: