We are having huge problems trying to run a Code Club on Saturday mornings at our local library in the UK. Logging on to the Scratch website and then navigating to the current project can take anything up to half an hour. At our session this morning one student was waiting almost the entire hour to get to his Scratch project so didn't achieve very much.

I assume this is a result of hundreds of Code Clubs across the UK and Europe all trying to access the site at the same time. It is rather sad that an educational website doesn't have the capacity to cope with surges like this.

Can anyone suggest anything that could be done to our (rather old) laptops to speed up the access? They are all running Windows 10. Could there be anything in the setup that could be slowing down Scratch access? We also use https://projects.raspberrypi.org on these laptops and the response is not great, but it is lightning fast by comparison to Scratch.

We are now moving towards using Offline Scratch, but the problem is that students will save their code on one laptop and may not necessarily remember which machine they were using by the time of the next session.

Grateful for any advice.