This is a very poorly engineered solution. My company's app deals with a much higher volume of traffic. As you can see when you click the 'login' several 'outside' application servers are contacted before the authorization mechanism. This, in itself, will undoubtedly bring things to a halt. They need a solution which can, dynamically, scale out their, 'stats', load static content first, load preferred content second, and then load all the crap advertising third. "Spinning up additional servers, is a crock of bull statement". And if it IS true, it's an indication they have NO idea what they're doing.
Another annoyance is that I find myself having to login in after every viewing of past content. For example, if I want to watch two past football games in a row, they force me to log in again.
This solution is horrible.