This recent post has a good description of the things which can affect Inbound commands and cause delays.
I do see a lot of delays on commands going back a while, and I am currently checking with ADC on possible other cases in the area to determine if it is a carrier issue, but from the linked post there are a few things locally to check:
"One common local cause of inbound delay is a cellular network extender. If you use a network extender for the same carrier as your module, it will detrimentally affect the inbound commands. In the case of Verizon, the module’s “phone number” can be typically added to the extender’s white-list, which will resolve the issue. If you or a close neighbor use a network extender, this may be the problem.
Another issue which can occur with 2GIG Panels relates to Z-wave commands getting backed up. Firmware 1.17 allows for a Z-wave command queue which helps resolve an overload of Z-wave commands adversely affecting the module.
Other common physical issues which can cause signal trouble are high voltage interference if the module antenna is in the wall resting near a house voltage line. Perhaps the most common issue comes from older 2G antennae being used for CDMA and HSPA modules. This should not be done. If you are using the smaller, roughly 1/2 inch x 2 inch antenna that was used with a 2G module, you’ll typically notice a lot of issues."
Overall, in order to generally improve latency, the Go!Bridge is the best solution. Extended delays beyond one minute or so are aberrant though, and likely caused by the one of the above reasons or the carrier tower.