WebSocket Blocking: Latency Impact on LendingPad Performance

 If you're experiencing unexpected latency in LendingPad—where user actions like opening loans, saving conditions, updating underwriting status, or navigating screens feel sluggish, the culprit may be WebSocket connections being blocked by your network infrastructure. 

 The Problem: WebSocket Connections Blocked by Your Proxy

When your network infrastructure (reverse proxy, firewall, security gateway, or content delivery network) blocks or does not properly pass WebSocket connections to LendingPad, the application automatically falls back to HTTP long polling.

This is standard SignalR behavior designed to ensure the application remains functional. However, long polling comes with a significant performance penalty.

Symptoms:

• Basic actions feel sluggish (1-3 second delays)
• Real-time updates don't appear (require refresh)
• Slowness increases during busy periods
• Network shows continuous transport=longPolling requests

 Solution

Tell your network team to add this domain to proxy bypass:

prod.lendingpad.com

If bypass isn't possible, configure the proxy to allow WebSocket:

• Forward Upgrade and Connection headers unchanged
• Support HTTP 101 (Switching Protocols) responses
• Do not strip or filter these headers