Performance issues
-
Over the past month or so, I’ve noticed that the performance of the Vivaldi browser on iOS has been, sub optimal, taking multiple seconds sometimes to open a web page from search results, returning to the search results, opening new tabs, opening a tab after closing all tabs, and other tasks. All of these seem to lag the browser in some way.
Devices used: iPhone 13 Pro, 3rd gen 11 inch iPad Pro
iOS version: 17.5
iPadOS version: 17.5
Vivaldi version: 6.7.3335.57 -
I have also reported issues regarding the adblocker. Comparing it to brave that also has built in ad blocker, it feels like night and day.
Vivaldi's adblocker still makes the phone extremely hot and lags. This is prominent when the status of the adblocker is ”applying new blocking settings” as my image. And this happens unfortunately everytime a filterlist maintainer updates its filterlist and Vivaldi applies them. This is not a bug per se, since it is good that the filterlists are up-to-date. However, I don’t think the execution of the adblocker on iOS is good to be honest, especially knowing that other browsers like brave and arc search don’t have this issue. Imagine someone having a lot of filterlists enabled, this will trigger the ”applying new blocking settings” very often, causing the phone to get hot.
-
Oddly enough I have had few issues with the TestFlight version of Vivaldi except for the occasional crash.
It looks good and pages load quickly enough for me and respond when needed.
6.7.3335.38 (Official Build) stable (64-bit)
iPad, 9th gen. -
@HealingCross67
I think I read somewhere that it isn’t on their roadmap to use chromium on iOS as it is to costly to maintain 3 different browsers.
-
@Veddu
I believe that deep down (not only at Vivaldi) there is a hope that with the EU mandate that apple will switch to chromium worldwide instead of having two browser engines to maintain.
Not sure how realistic that is considering apple’s deep pockets. -
@IwIanuel
I have not added any additional filterlists. I have the defaults enabled only + running NextDNS.
The issue I have explained before is that everytime a filterlist maintainer updates its filterlist Vivaldi is applying them hence making the phone hot.
This can be replicated just by disabling and enabling the adblocker on a website and you will feel how hot the phone gets when it is re-applying the adblocker settings.
-
@IwIanuel
Thanks for sharing! I will give these a try!
-
@IwIanuel
I disabled easylist and easyprivacy, since NextDNS already have them. I have not added the brave filterlists but I can feel the difference in performance when they are disabled in Vivaldi.
-
@IwIanuel said in Performance issues:
@Veddu No, Vivaldi adblocker works fine. The problem is everyone (look like you also) forget that iOS only allowed 50.000 rules limits, and that's also the reason it makes the phone heating up.
That's why I suggested the team splitting fillers like Adguard did, to bypass 50.000 rules. For now, if you uses filters that surpasses 50.000 rules it will not just kill your phone but adblocker not work either. Recommend using the filters that optimize for mobile.
Here, I have some. Official filters from Brave:
Included:- Brave first party: https://raw.githubusercontent.com/brave/adblock-lists/master/brave-lists/brave-firstparty.txt
- Brave iOS specific: https://raw.githubusercontent.com/brave/adblock-lists/master/brave-lists/brave-ios-specific.txt
- Brave unbreak: https://raw.githubusercontent.com/brave/adblock-lists/master/brave-unbreak.txt
Yes, only 3 filters and not even close to 10.000 rules but works like charm.
I just tried this on a fresh install on my iPhone Xr, and it makes a massive difference in performance. So far it looks like it's blocking all the ads I need.
Thanks for this tip! I hope the devs see this and maybe implement an iOS specific filter list.
-
This post is deleted! -
Brave uses som kind of AWS lambda based crawling system for evaluating which EasyList and EasyPrivacy rules are the most useful in order to shrink the filterlist for iOS in addition to the filterlists mentioned by @IwIanuel.
More info about it can be found here on their github.
Not sure if Vivaldi have the Manpower to implement something similar for iOS. For now I guess the best way in terms of performance is to use the brave filters mentioned above in combination with a NextDNS profile (Even though the sponsored ads still shows on Google and Reddit) or substitute the default easylist filterlist for iOS optimized one.
-
@Veddu Thanks for the links and additional info! I just tried that optimized iOS filter list, and noticed it did start to make my phone a little warm, it took quite a bit longer to apply ad blocker settings than the Brave list. But I will give it some more time to see how it behaves. It still was significantly less time to load the lists versus the default lists included with the browser.
-
Actually I found another one that works better for me. Adblock plus Easylist minified.
This also removed the sponsored ads and didn’t cause any performance issues. Try that one Instead and see what you think.
-
@Veddu That one seems to do the trick. Just added it, and it imported fairly quick, and not noticing the phone getting warm while using it! Thanks!
-
Good to hear. I also tried to import it on the desktop to see the rule count, and it was 10530 rules whereas 19 of them were unsupported.
-
Just wanted to add that I changed the default fanboy annoyances filterlist to the optimzed one and that works better.
