Well as you know packet loss is an indication of, a bad wire, distance traveled of cable.
Or the physical range, distance between both wireless devices.
Also, dependent, is how the switch works in transfer speed in respect to the Ethernet ports of it 10, 100, 1000. And the physical Ethernet adapter of the client machine is running at.
10,100,or 1000 in speed.
If you get packet loss or a delay. it can be a cable or the transmission speed is to high for a switch to switch quick enough causing packet loss.
As I said sometimes it can be down to the settings of the local machine and its Ethernet or w-fi adapter settings.
As you know a switch can have a set number of Ethernet ports but what are the actual switching values of it in respect to the client machine and the rest of the network. It has to do a convert between the speed of each client and each port.
Delay- packet loss depending on it`s capability.
To fast transmission for it to handle = packet loss.
You can tell this by the amount of Ms it takes across a network.
Via pining a set known IP of the network.
Other than your own machine.
Because when you get packet loss the amount of time it takes for a Ping of an input IP address will increase in ms, this is because it has to re send the packets or requests for them to be resent= Higher ping time or packet response in ms, ms is the total time it took to send and receive all the packets in full. Four out four in=count time ms.
That way you can work out where or what part of the network, is falling down.
Or you can trace route an IP also with a report on Ping and the device or IP causing the high latency or where the packet loss is on part of the Network, if you know the range of IP`s across all of the network.
Each inter connection can be checked for the error. By a trace route.
You have a reference of the IP so then you know what device or part of the network through linking is the problem.
The value in ms is higher, or the request fails at a set given IP in the trace route.
Check cables, device and bridge.