You are right, there are errors (in yellow) in Chrome. I should have specified. The only reason I’m suspicious that they are related to the lag is that if I monitor the console while I modify a block, the page becomes unresponsive the moment the console starts logging these warnings, and becomes responsive again the moment the last warning has logged.
There are 855. Yeah, I know, it’s a lot lol. The code all executes just fine on my device, it’s just a pain to make modifications. I would have significantly less blocks if I could address components programmatically (as far as I know, this is only possible with variables).