Tunnelling in QlikView basically makes the packets encapsulated (and then de-encapsulated) in an http connection, and that usually results in worse performances.
Also, when you don't tunnel you talk directly to the QlikView Server, while tunnelling forces you to go through the QlikView WebServer, which, of course, adds more strain to the system.
Resolution:
Verify if the Access Point's server connections are set to Always Tunnel, as documented on the Server Connections, Qlik Help.
If so, you might want to ensure that direct connections to the QlikView Server on port 4747 are allowed, and disable the tunnel setting.
This will relieve the two services (QVS and QVWS) from having constant communication with each other, reducing the strain that might result from the process.