Loading Time

What part of a map now exactly increases the loading time?
I tried using both optimizers but still, the loading time keeps being a pain.

A large map with many doodads/trees tends to be heavy on the loading time ithink.

Would a map lag with many memory leaks? I think, but I'm not sure...

Memory leaks have nothing to do with loading times.

Loading times are the sum of everything which has to be loaded/created on start up. Initialisation triggers, preplaced objects, object data used at start up, etc..

I don't even have a terrain yet...
I have a lot in the header though, is there a way to let them "load" later?
Also, I use nothing but Cumstom Objects...
Like, I never use a standard one.

Loading them on start up is much preferable to lag spikes loading them later.

Er, do my thousands of "custom objects" affect this loading time?
Only few units are put on the map, with some buildings, but that's it...
Is it better to "modify" standard objects?

If you have many arrays and set them to initialize 8192 values it will affect loading time. Also if you have a lot of preplaced units.

Custom objects have the same effect as modiffied standard objects

It's mainly caused by a large number of objects in the object editor and also wts strings.
That's the part of the loading bar before it reaches ~60%

The part after 60% is caused by trigger/variable initialization.

Widgetizer will help to reduce the first mentioned part of the loading.

And actually modifying blizz objects instead of using customs will make the loading slightly faster but not that it's worth it.