Testing for this note… we made six attempts to⚡zap this note, using your lightning address starting with "alluringgossamer371589", over a period of about 1 hour. Five of the zaps were successful, but one of the zaps failed. Average zap time was 7439ms (7.4 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) If you wanted to speed up your zap confirmations, you could try receiving zaps with a well-connected, cloud-based Lightning node.
Discussion
I was unaware zap time could be measured. This is insightful, thanks. Is that a hardware issue, or internet speed issue?
Is running a cloud based node custodial?
The word "custodial" is being widely mis-used. A lot of "non-custodial" services are custodial in the sense that you will never be able to recover your funds if their service stops working.... But yes, a cloud node by definition is more custodial.
Listening to Citadel Dispatch, the latest one with nostr:npub19kv88vjm7tw6v9qksn2y6h4hdt6e79nh3zjcud36k9n3lmlwsleqwte2qd mentions there’s variations in channel speeds as well because of trade offs in what channels offer. That may be contributing to the transaction speed as well.
Yes, we've developed a server-side way to measure zap time. In your case, I am guessing your a running Alby Hub on your own hardware, and your internet connection is perhaps not super-low-latency, thus your 7.4 zap time. There could also be other factors. If you wanted to improve this, we'd recommend rizful.com or Alby Cloud. Both of which give you "your own node", but you are dependent on the cloud service to keep it running.