The loadavg of the Linux system, this node is running on, is unknown while serving unknown connections. This node has had much MB traffic the last 24 hours and even more GB traffic the last 30 days. You can browse some historical data here:
Inter Node Communication Traffic.
This is the traffic issued between IOTA nodes to keep the tangle synced between each node. RX traffic is traffic directed to this node, while TX traffic is traffic directed to other nodes. This view also separates the used communication protocol. However, you can't see by this diagram, which protocol is more effective, because you don't know how many nodes use udp or tcp protocol transport.
Command & Control (JSON) Traffic.
This is the traffic produced by the Light Wallet clients (or other clients). RX is the traffic transporting the JSON request, while TX is the traffic transporting the compressed JSON reply of the IOTA node. I added the spline to the diagram to visualise better how strong the protocol compression is. So, this spline is the traffic all requests would have issed when not compressed.
Some of the neighbours of this node are handled by nelson. Here you can see how many traffic nelson needs to manage up to 20 additional nodes.
Webserver (this page) Traffic.
This is the traffic of this web-page, covering HTTP and HTTPS endpoints alike.
Connected Clients and Load Average.
Here you can see the concurrent connected clients and the load average of the underlying linux system.
You can configure the range shown in the charts here: