The demonstration is similar to motion detection by checking the pixels of a video image. It seems to display it on canvas and then retrieve the image data of the canvas.
This is slow because it is just slow work - there are many pixels, frames go through quickly, and this is a high processor load. This has been made worse by the fact that Javascript is not always very efficient at this kind of data processing. Therefore, I do not think that slowness is inherent in WebRTC. This is just heavy javascript.
source share