As others have said, profiling is really the only way to find out where the bottleneck is. Here's some help on zeroing in on the problems:
-
First, use something like what @JMichaelTX mentioned above to determine elapsed time. Or you can use my logging macros: MACROs: "Write To Log File", etc., **Updated 2016-12-28. These macros show elapsed time, and since they write to a disk file instead of displaying on the screen, they're fairly transparent.
-
Start by comparing the elapsed time of large sections of you macro(s) first. Then gradually move the start time and end time closer to each other, until you find the problem area.
-
You honestly don't have to know a lot about the macro to do this. Just start somewhere and then start narrowing it down until you find the problems.
If any of this is confusing, think of it like this: Two people go grocery shopping. One takes twice as long as the other. Why?
Compare how long it took each person to drive to the store. If that's about the same, compare how long they spend wandering the aisles. How long does it take them to check out? How long to load up the car with the groceries? Time to drive home?
Hope this helps.