Every time you reset, the rendering slows down on the next run. For me, second replay is half the speed of the first, and it gets worse from there. You can fix it by refreshing the page or re-uploading the replay.
Two thoughts:
As a quick fix, should be easy to just do a hard refresh when someone hits the reset button?
I haven't looked at the code, and I'm not a JS dev, but to me this strongly suggests that there's some unnecessary data accumulating over time as successive frames are rendered (e.g. an array that always gets pushed to, never overridden or emptied). If that's true, then fixing the underlying problem should improve the performance of the visualiser quite a bit.
To reproduce:
Every time you reset, the rendering slows down on the next run. For me, second replay is half the speed of the first, and it gets worse from there. You can fix it by refreshing the page or re-uploading the replay.
Two thoughts: