I once wrote an HTTP API in node (no framework) and within 50 request, not even simultaneous, the server was toast. The memory leak struggle is real.

So as long as node doesn't buckle under the weight of a few lines of bad code, then I would recommend opening top or htop in terminal, sorting it by memory use and hitting refresh a bunch of times in your browser. Or setup 20 tabs to refresh every 2 seconds. Or very 30 seconds and come back in a few hours to make sure no slow leaks are happening. Or use a number of purpose-built stress testing applications to send a lot of traffic to your site so you can see where your failure point is.