A look over the raw DDP socket shows you're sending down the entire collection to the client, so in effect everyone downloads the entire 'supporters' collection.
This looks like the bit inefficient. This is because you send down the whole collection (~7000 records - which each looks to be ~100 bytes on the DDP wire), in total nearly 1 mb of data to be downloaded.
So these have to be downloaded first, then the count can be displayed. Why not store the count in a separate collection and only send that down? It should be much faster that way. Unless you're giving the entire list of names on a table or something somewhere it might be better to do this.
The other thing is on your hosting provider you're not letting websockets work so meteor falls back to long-polling (XHR) which is a bit slower to initially connect since there is all this extra overhead. You might want to look at something you have in between, typically a proxy or firewall that isn't configured to let through websocket requests.