been working on a little zine, having a blast doing so, Decker is the future, etc.  i'm testing it out as a playable thing on my itch page and i'm noticing it's like, wayyy slower than how it runs in native Decker. for example, on one card i have a 'sleep[]' function that lasts about 4 seconds longer than it should.

i have a lot of audio clips among everything else, which has made the size of my deck around 1MB. i'm wondering if that's large for a deck and if it could be part of the sluggishness. i dunno! maybe someone's got some optimization tips for me? anyway have a good one

Update: in v1.13 I overhauled web-decker's timing loop. Results should be much more consistent with native-decker. I also slipped in a few minor performance enhancements. The downside is that on slow machines, dropped frames will cause some animation to look choppier, and particularly expensive transition animations like the "Heart Wipe" from Public Transit will only render a handful of frames.