Streaming Tweets performance issues or just one of the downsides of using an API?

[jisungyoon019]

So I used both nodejs and python tweepy to Stream and listen to my own tweets for "PERFORMANCE" testing.

How did I test it?
First, I set the stream to listen for tweets and the target is... my own tweets, of course.
Next is I run the code and made sure to disconnect the stream once I get a 1 to 2 tweets to make sure I will not hit the rate limit.
NOTE: When a tweet is found/fetched via stream, it will print "FOUND TWEET!" on the terminal/console.
Finally, I start running the the program and test it by posting a tweet via android or web browser and then observe the stream on VISUAL STUDIO IDE for both python tweepy and nodejs twitter-api-v2:
RESULT:
It always take around 5 to 6 seconds right after I tweet, for it to be found. Why is the latency so bad?

ANOTHER NOTE: I tested my ping for Twitter via cmd ping test, it's: 51 ms

Is there a way to get the real-time stream with the best performance latency because I've seen other clients or other api that has better refresh update like super fast and INSTANT.

Hope somebody knows..

[jisungyoon019]

If somebody has a working with best latency using via stream or other ways, please kindly share your script if it's fine and I'll try it as well.
-Script via stream that listens to specific user tweets (with given userId or userName is fine)
-Script via stream that listens to self tweets (with given self userId or self userName is fine)
-Must be V2 endpoint (essential access) lol cause I dont have elevated access..