The com loop time is the PING time, plus the host task response.
So, that means you always have network delay showing up in that PAC Term inspect com loop time number. No matter what charts are running or what they are doing, there is the distance between the PC running PAC Term and the controller.
ie, my buddy in Australia, when I PAC Term inspect his controller, it is always ~200ms.
If your charts have delays, if you only have a few charts and you are not doing a lot with the host task (com handles, PAC Display, OPC, groov etc) then you may well see a com loop time less than your delays in any chart.
To see your best com loop time - ONLY do this if it safe to do so - stop your charts. There is a button right there in that PAC Term inspect box, what this will do is give PAC Term 100% (roughly) of the host task and so you will see your network delay and not a lot else (PAC Display and groov aside).
The fun part for you as a programmer is if you have say 200ms com loop time, and 20ms when you stop the charts.
If you see this, you know your network PING times are good, but there is something in your strategy that is bogging things down.
Remember, adding delays speeds things up.