-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Brave Extension increases page load times by ×10 #17538
Comments
cc: @antonok-edm |
@da2x I'm not able to reproduce your issue. I do see some overhead, but certainly not 10x. For comparison, I get 74ms for Scripting when running with Shields disabled. If you're seeing 500-700ms then something definitely sounds wrong, but I'll need more information to look into it further. |
I get the same result on my much faster gaming desktop computer, but I get 500–700 ms on my Lenovo laptop from 2018. I can reproduce it on my desktop by throttling the processor. Intel i5 7200U with relatively slow 1GHz RAM. |
Related to #17906? |
@Tonev possibly. It would also be good to check if it's affected at all by brave/brave-core#9995 |
To resolve this the following issues should be done: |
@da2x we significantly optimized Brave Extension in Nightly, would be great if you could test that. |
Pls reopen if this happens again |
Steps to Reproduce
(Compare to Edge or Chrome with no extensions.)
Actual result:
content_cosmetic.bundle.js
(a script inserted by the bundled Brave Extension) increases the page load time by ×10.Even for simple pages, page loads go from 30–50 ms to 500–700 ms. (Times excluding networking overhead.)
For more complex pages served from a local file (no network overhead), the Lighthouse performance score drops from 98 to low 60s.
Expected result:
No compromises on performance. (Or, at least only tiny ones.)
Reproduces how often:
Every time.
Brave version (brave://version info)
1.28.105 Chromium: 92.0.4515.13
Version/Channel Information:
stable
Other Additional Information:
no.
no.
no, it’s Brave specific.
The text was updated successfully, but these errors were encountered: