Improve performance of large number of Global External API requests

[bobbybosler]

Hello,

Loving the new updates. Appreciate you guys so much!

I’ve got a page (theegeneration.org/stats) that makes a lot of individual API requests. Each data point and chart on the page is its own request, and as such I’m experiencing some issues with page load speeds, especially when none of these requests are cached because it’s been a while since someone has accessed the page. Not only that, but if I increase the number of episodes to something like 20, some of the requests begin returning NaN (not a number) instead of the values one would expect.

I switched all of them over to the Global External API system, hoping it would improve the performance, but it really hasn’t. I’m wondering what my options are for improving the performance of these requests and also how I can ensure that I don’t get the NaN error.

[charlie]

Unfortunately we don’t really have a solution for this. Ideally this is something handled by CS through a “Deferred HTML” system where any element could be set to render after the page has loaded. Sort of like a UI where it shows a loading icon, then finally displays the content. Splitting the requests to different pages is the only way I could think to do this right now. Thanks for the input, great looking page btw.