GIS app loading very slow through F5 LTM

Right now there isn’t enough information to identify the cause. A 50-second delay alone isn’t enough to determine whether the issue is on F5, the network, or the backend application.

I would start by isolating where the delay occurs: DNS lookup, TCP/SSL handshake, F5 processing, or backend server response. On BIG-IP you can check the virtual server and pool member statistics, and run a tcpdump on both clientside and serverside. That usually shows quickly whether the delay happens before reaching the server or while waiting for the server response.

It’s also helpful to compare direct access to the server vs through F5, and check the browser developer tools waterfall to see which step is taking the time.