Now here’s an interesting thing 8.3.9 to 9.0.4

[suzywong]

Regular readers may recall that I have mentioned (some might say “whinged”   ) previously that the time taken to load the TAG screen on my iThings has been the order of many seconds - sometimes up to 50 seconds. Kent tracked it down to the “Lazy Loading” setting in iOS, and suggested a way forward. And that worked well enough and the tag screens would load in about 5 seconds. IOS on the iThings is up to date at V17.5.1.

Now, two of my (RPi 3B) streamers now run 9.0.4 while the other two run 8.3.9, which gave me an opportunity to compare the two. And I’m happy to report that 9.0.4 loads in 1-2 seconds, whereas 8.3.9 remains at 5.

Nice! 

[Tonewheelkev]

Regular readers may recall that I have mentioned (some might say “whinged”   ) previously that the time taken to load the TAG screen on my iThings has been the order of many seconds - sometimes up to 50 seconds. Kent tracked it down to the “Lazy Loading” setting in iOS, and suggested a way forward. And that worked well enough and the tag screens would load in about 5 seconds. IOS on the iThings is up to date at V17.5.1.

Now, two of my (RPi 3B) streamers now run 9.0.4 while the other two run 8.3.9, which gave me an opportunity to compare the two. And I’m happy to report that 9.0.4 loads in 1-2 seconds, whereas 8.3.9 remains at 5.

Nice! 

So....what setting do you use for Lazy load?

[swizzle]

Regular readers may recall that I have mentioned (some might say “whinged”   ) previously that the time taken to load the TAG screen on my iThings has been the order of many seconds - sometimes up to 50 seconds. Kent tracked it down to the “Lazy Loading” setting in iOS, and suggested a way forward. And that worked well enough and the tag screens would load in about 5 seconds. IOS on the iThings is up to date at V17.5.1.

Now, two of my (RPi 3B) streamers now run 9.0.4 while the other two run 8.3.9, which gave me an opportunity to compare the two. And I’m happy to report that 9.0.4 loads in 1-2 seconds, whereas 8.3.9 remains at 5.

Nice! 

So....what setting do you use for Lazy load?

Last I looked (a while ago) native lazy load didn’t work right in iOS WebKit so you should use native lazy load: no. There was no real difference in speed between the two options (when it works). All things being equal native would be preferable as it’d be one less thing for Tim to maintain but c’est la vie.

[suzywong]

So....what setting do you use for Lazy load?

Both “Lazy image loading” and “Lazy iframe loading” are OFF

[Tonewheelkev]

Both “Lazy image loading” and “Lazy iframe loading” are OFF

Thanks!!

[swizzle]

So....what setting do you use for Lazy load?

Both “Lazy image loading” and “Lazy iframe loading” are OFF

Turning those off in iOS settings isn’t ideal as you’re turning them off for all web content where it might be useful. Moode has a setting in preferences > appearance called “native lazyload” which accomplishes the same thing by ignoring the browser feature check and using the original lazyload code.

[Tonewheelkev]

So....what setting do you use for Lazy load?

Both “Lazy image loading” and “Lazy iframe loading” are OFF

Turning those off in iOS settings isn’t ideal as you’re turning them off for all web content where it might be useful. Moode has a setting in preferences > appearance called “native lazyload” which accomplishes the same thing by ignoring the browser feature check and using the original lazyload code.

The only setting I've turned off....is the one in Moode prefs....is that correct?

[HarryY]

I had that same issue when I was using the browser on my Samsung Smart TV.

I discovered that the metadata for one album was corrupt and once I fixed that the
speed jumped up substantially; it went from about 30-45 seconds to about 5 seconds.

With the latest release v9.0.5 it's now about 2 seconds so I'm very pleased with it.

[swizzle]

So....what setting do you use for Lazy load?

Both “Lazy image loading” and “Lazy iframe loading” are OFF

Turning those off in iOS settings isn’t ideal as you’re turning them off for all web content where it might be useful. Moode has a setting in preferences > appearance called “native lazyload” which accomplishes the same thing by ignoring the browser feature check and using the original lazyload code.

The only setting I've turned off....is the one in Moode prefs....is that correct?

Yes. When the browsers started supporting native lazyload a few years ago we added a web feature check in the code to prefer native if available but somewhere along the way iOS WebKit started not working properly. Since I’ve only ever seen the problem on moode and it’d be hard to get them to test as it requires a raspberry pi, etc. it was easier for Tim to add the preference which bypasses the web feature check.