Laggy menus typically have little or nothing to do with microservice architectures.
Specifically, every API call that traverses a machine, boundary, necessarily impart, additional latency, and uncontrolled microservices can have a multiplicative effect
Or perhaps I am misunderstanding your comment?
More so for something like a web app like AppleTV where the content is largely static.
There should be zero difference in performance between microservices and monolith in this scenario.
It's the serving of the content that requires coordination across multiple services and most of that should be cached at the serving layer.