I agree with Andrei - it seems you have lots of data and many layers you are trying to load at once - each of which adds a bit of overhead on load and consumes memory in the process. And as Andrei mentions other factors may also be coming into play, like the physical location of where these data are located on your network/drives. I'd suggest taking a "divide and conquer" approach and carving up that one large map into several smaller ones. That may also help to figure out if any of those layers in particular is causing the slow load, plus will provide the added benefit of turning what seems to be an intimidating number of choices for a user in your contents into a more manageable number that might be focused on specific workflows or projects.
It also seems from your list of data that you are using local data sources entirely, some of which are quite large. If you can, some of those layers might be better published as a service to increase performance.
