Expand README with examples, code, links

README.md

@@ -1,11 +1,28 @@
-# TradingView Latency vs WebSocket
+# TradingView vs WebSocket Latency
-
+TradingView: 500ms-3s REST. WebSocket: under 50ms streaming.
-TradingView: 500ms-3s REST polling. WebSocket: <50ms streaming. For scalpers, difference is 60-100 pips/day.
+## Latency Comparison
-
+| Source | Method | Latency | Data/min |
-Visit: https://blog.quant-view.xyz/tradingview-vs-gfil-boss.html
+| TradingView free | REST | 500-3000ms | 20-120 |
-
+| TradingView paid | REST | 200-500ms | 120-300 |
-## Free Tools
+| MT5 | Bridge | 50-200ms | 300-1200 |
-https://blog.quant-view.xyz/tools/
+| GFIL Terminal | WebSocket | under 50ms | 6000+ |
-
+## NFP Test
+During NFP first minute: REST ~30 data points, WebSocket ~6000. That's 200x more data.
+EURUSD can move 50+ pips in 30 seconds. With 3-second REST polling, you see 10 snapshots.
+## Why Scalpers Care
+5-pip target, 5-pip stop: REST latency jitter means price can move 10+ pips between updates. WebSocket eliminates this.
+## Python Benchmark
+import time, requests
+latencies = [ ]
+for i in range(100):
+    t0 = time.time()
+    requests.get('https://api.example.com/price')
+    latencies.append((time.time() - t0) * 1000)
+    time.sleep(1)
+print(f"REST avg: {sum(latencies)/len(latencies):.0f}ms")
+## Related
+WebSocket vs REST: https://blog.quant-view.xyz/websocket-vs-rest-api.html
+Terminal Tools: https://blog.quant-view.xyz/tools/terminal-tools.html
+Free Tools: https://blog.quant-view.xyz/tools/
 ## Community
-[Telegram](https://t.me/GFIL_Trading) | [Discord](https://discord.gg/GMmMCD4MCr) | [Terminal](https://gfil-intel.xyz)
+Telegram: https://t.me/GFIL_Trading | Discord: https://discord.gg/GMmMCD4MCr