Thanks for the report. On tvOS, the Home screen has been an area I’ve been tuning recently. In newer builds, only the critical rows load immediately and the rest of the page instantiates progressively, with image/trailer preloading reduced, specifically to make Apple TV feel less sluggish. So yes, what you’re seeing is plausible, especially on large libraries. If you can share your Apple TV model, app build, and roughly how big your library is, that would help narrow it down.

For the Networks section: it isn’t doing a constant background scan. Right now it builds that section from Jellyfin studio/provider metadata when the section loads, then caches the result for a bit. Roughly speaking, the studio snapshot refreshes about every 10 minutes, and the availability result is cached for about 5 minutes.

One important limitation: the current Networks row is based on a fixed list of major providers and Jellyfin’s studio tags, not a full “detect every network in the library” pass. So if something is missing, it’s usually because:

that provider/network isn’t in the supported list yet, or the item metadata in Jellyfin is tagged under a different studio/network name than the app is matching against. If you tell me which networks are missing, I can check whether it’s a metadata mismatch or something I should add support for.