Self-sustaining costs for extension

Hello everyone,(BarryCarlyon, rbartlet, mBeierl) thanks for the answers, I thought about some possibilities, maybe reduce some features or limit the interaction in some way to a group of users (subscribers).
part of the application flow is following in some images, with description

1°: 1st: the first load appears only the button with the red tag with the polls closed, the toastr alert some after 5 seconds

2nd: the second load appears only the button with the green tag with the polls open, the alert toastr disappears after 7 seconds, it only opens the poll if the streamer sends a warning on the socket io

3 ° Once the polls have been opened, simply click on the button to show the map and all votes already counted

4 ° There is a socket listening to each new vote well succeeded to update the votes

Do you all think that this flow is heavy for a twtich application?

One point we all agree on is to use a free cloud service for testing at first, thanks for the help