Yeah, we actually just didn't have time to properly optimize it. Now we have a link to the no-lag version with performance bug fixes in the description (vercel deployment)
