The short answer
Growing delay suggests a pipeline falling behind rather than a fixed network round trip. Record how lag changes with camera count, transport and decode load.
Work through the checks
Show a visible changing clock or a supervised movement in the camera scene, then compare it with the live image. Use the same source and layout for each latency comparison.
Test one camera and one stream before opening a larger camera wall. Keep the camera settings unchanged while you establish whether the first live image is stable.
Observe CPU, GPU, memory and network use in Windows Task Manager with one view, then add views gradually. Record the point where playback begins to lag.
Compare the main stream and a camera-provided substream at the same time of day. The substream often reduces decoding load, but confirm that the detail you need remains visible.
What to verify
If the viewer exposes transport selection, compare TCP and UDP on the same local route. TCP can avoid UDP loss but may accumulate delay; record visible gaps and end-to-end lag.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.