It should be fixed by now.

Thanks for the feedback. We are aware of the latency issue and we are looking into improving it. Though, in the meantime, this will be the expect latency for this API.