Hey Waffle, I'll also add that the responsiveness of the web interface is very much down to the performance of the computer running the web browser. The more content rendered on the page, the more the web browser has to compute before the page is updated.
It is going to be related to the single threaded performance of the hardware running the browser.
Either try to avoid going to the now playing screen when you got a big playlist going or consider getting something faster to run the browser on like a newer, faster Android tablet or small laptop.
To compare for you, I've tested adding one genre of about 6550 tracks in my collection to the playlist and opening the now playing screen...
* On a Huawei Mediapad T3 10 with just a 1.4GHz quad core CPU it took 25 seconds to render the screen with that list in the Samsung Internet web browser based on Chromium.
* On my Samsung Galaxy S9 with a Octa-Core 2.8GHz + 1.7GHz processor running the same browser it took 6 seconds.
* On a 6 year old laptop with a 2GHz Core i7 mobile processor running Firefox on Linux it took barely a second.
It is going to be related to the single threaded performance of the hardware running the browser.
Either try to avoid going to the now playing screen when you got a big playlist going or consider getting something faster to run the browser on like a newer, faster Android tablet or small laptop.
To compare for you, I've tested adding one genre of about 6550 tracks in my collection to the playlist and opening the now playing screen...
* On a Huawei Mediapad T3 10 with just a 1.4GHz quad core CPU it took 25 seconds to render the screen with that list in the Samsung Internet web browser based on Chromium.
* On my Samsung Galaxy S9 with a Octa-Core 2.8GHz + 1.7GHz processor running the same browser it took 6 seconds.
* On a 6 year old laptop with a 2GHz Core i7 mobile processor running Firefox on Linux it took barely a second.
