It doesn't look like a memory issue--more of a latency issue with third-party APIs (some of them can take quite awhile to send back a response). But either way,

It doesn't look like a memory issue--more of a latency issue with third-party APIs (some of them can take quite awhile to send back a response). But either way, I will look into upgrading the dyno and/or database to see if that helps. I think implementing websockets and rendering results as they come in would be my best bet, but it would add additional complexity, and I'm not a big fan of that at this stage.