2) set your caching in assets and images to preserve bandwidth
3) test if your db is the bottleneck.
Eg. Some applications have their performance log in a response header ( db: 20 ms, logic : 10 Ms, total: 50 ms)
Definitely start profiling and try to up you bandwidth depending on your current online users.
I just finish setting up CDN a few minutes ago. And my bandwith is 2M now.
Have you found the bottleneck and has the experience improved?
I don't know the specifics of your app. But minimizing assets could also reduce bandwidth, it's mostly done by default. So that's what's why i didn't mention it before.
According to my cloud server's monitor, there is a big chance that the slowness is due to bandwith too crowded. I want to see if there is more slowness report or if I can experience slowness again, before I spend time to learn profiling.
But I guess sooner or later I'll have to do that. Now that I know what is in my armory, I feel more at peace :)
Perhaps it's a good time to mention that I've implemented health checks for a lot of applications.
It returns healthy when everything is okay ( eg. Select 1; on the db) and unhealthy when something is off ( eg. Hard drive 80% occupied, CPU at 80% or memory at 85% ) and returns failure when....
If could be just a library in nodejs and adding an endpoint.