I'm not convinced about that...
At the Avalon freeroll at 32RED i get a lot more spins than on a GSOS freeroll, also Avalon, on another MG casino. I've got a very fast laptop and a "lag-free" internet connection.
I believe there has even been a topic on this a while ago about "delaying spins" on MG based casino's (Tourneys only).
I busted MGS a couple of years ago, they sneaked in some "crippleware" with an update. Before this, I was tweaking away, and had managed to get the slots to run just as fast as in normal play, with one second or less between spins. After the update, and with the same tweaks, I found that once you started spinning faster than 3 seconds apart, the server held back the results for these spins for about 6 seconds before sending it out, and continued to add this 6 second lag until you allowed 6 seconds before spinning again, at which point the "crippleware" switched off.
Further experiments showed that the trigger point for this "crippleware" is just below 3 seconds, so once you have managed to tweak your system to achieve this, there is no point in going any further.
The update early this year then made things worse, and everything has slowed down, not just the tourneys, this CAN be countered by a hardware upgrade, one that can handle the newly "megabloated" client, and it's ENORMOUS demand for video processing compared with earlier clients.
I would suggest maxing out the RAM, and getting a decent Full HD graphics card with a decent chunk of on board RAM, otherwise the video processing has to share RAM with the OS and software, and may even have to use the paging file, which being on the hard drive, is much slower than RAM.
It may even be worth getting a new PC, one that would support "gaming", in order to satisfy the present demands of the MGS client. I have noticed that hardware has moved on a great deal in the last 3 years, with very much faster RAM, and solid state drives - useful as the main "C: Drive" on a PC because it loads software much faster.
Another approach would be to cut back on background tasks to see whether this makes an improvement to tourney performance.
Remember, the target is 3 seconds between spins, the "crippleware" enforces this lower limit. My system can achieve this, but needs the occasional re-tweak, in one case because it was too FAST