Mine was a Chrome browser on a Mac. My benchmark was counting seconds from when I said something and heard it coming thru the site on the speaker (lag).
Ahh. Ok, the delay you experience hearing your own voice through the site is not the delay that the model is experiencing. Your stream is sent to the model through webRTC. The delay for webRTC is practically non-existent. What you see on the site is either HLS or Nano, and both have transcoded options so there is a delay. What you are really experiencing is the delay between the model to you. That can be up to 7 seconds with HLS. While the delay from transcoded streams is annoying, it is what keeps the play from being choppy.
The vendor analyzed your stream from a recent C2C session. There was a point where you lost bandwidth and there was packet loss (which the model would have experienced while viewing your stream). This would have added to your issues. Keep in mind that when you are doing Cam2Cam you are downloading and uploading at the same time. So hypothetically, if your bandwidth can handle 2000 Mbps and your outbound stream is 700 Mbps, then for video to run smoothly, the stream you view should be no more than 1300 Mbps. The average model bitrate on the site is 1819 Mbps. So during Cam2Cam sessions, select the lower resolutions for the model's stream so you aren't competing for bandwidth. Keeping below your bandwidth threshold should improve your overall Cam2Cam experience.
Quote