The
primary purpose of the program is to measure the 'usage' i.e. total up and download bytes expressed as bytes, KB, MB or GB.
This is useful to verify that your ISP is billing you correctly.
The
secondary purpose is to show the "speed", which may be constant or may vary all over the place depending on: the plan that you subscribe to with your ISP (speed), how many users are sharing the local resources of your ISP, the speed of the 'other end' (some servers are faster, some are slower, it's usually an economic constraint), the number of 'hops' between you and the server at the 'other end', the type of service: copper, fibre and types of cellular: CDMA/2G/3G/4G-LTE (atmospheric conditions if you connect via cellular).
This is moderately useful to compare the actual average speed provided by your ISP to the maximum speed which your ISP says that you should expect but only if you're the only one using the ISP resources and the server supplying data is fast (also using a high speed connection) with no other demands than yours and there are only a few 'hops' between the server and you.
So for many people and situations this isn't really very useful, it's simply interesting to watch when things seem slow to download, you get to see just how slow. But Networx can't explain the root cause(s): ISP, # of users, server, connection (although cellular is a bit special, you get to see the impact of rain and snow which slows things down quite a bit in some cases). Over time you might determine that downloading from a particular site is always slow and therefore expect it, but you can't change it, so...
Just accept it 'as is', don't let it drive you nuts...
J