Luban is generating unoptimised/slow c-codes

As you can see from the below image, when I generate a g-code from an image file, it’s generating a path which is really really slow at cutting/engraving. It will do a tiny bit of work on the far left, then move all the way to the right to do a tiny bit, then move all the way back to the left for the next tiny bit.

Is there no way the g-code generator could group together pieces based on location rather than reading from top to bottom & left to right? It’s more than doubling the time it should be taking to cut as my SM2 is spending more time moving back and forth than actually cutting!