Strategies to handle lag with a slide that has nearly a hundred buttons?

I had attempted something similar with the checkboxes in my first iteration of this and encountered the same lag issue (though correct me if I'm misunderstanding).

At first, I placed checkboxes by these buttons to show if a question was flagged by the user, and button states were used to only show if the user had either seen or answered the question. Boolean variables and triggers were used to tell these objects if the user had opened, answered, or flagged any of the question slides. In this first iteration, I had 150 objects in the slide, 75 buttons with 75 checkboxes. My second iteration (described in the post above) was an attempt to see if I could reduce this lag by just using button states to display this information and removing the checkboxes to cut the number of objects in this slide in half. I was hopeful at first, noticing the lag wasn't as bad as my first attempt, but it failed once I started implementing states.

The good news about this second iteration is that managing objects is more straightforward due to reduced clutter, and I can alleviate lag by selectively hiding buttons using the timeline's "show/hide" toggle. This workaround isn't a definitive solution, as lag persists most of the time I'm building out this slide, and I have to manually hide each button since using "Hide all" doesn't work well with objects in scrolling panels (and everything is inside a scrolling panel unfortunately).

I do appreciate your response.