Improve the content data flow

Contetn data is currently transmitted using MJPEG encoding and high compression rates. This allows for fast forwarding, but low quality for static content and it's not fast enough for video content.

For static content need to refine option with lower compression rate.
For video (or another content maybe) WebM or h.265 are conceivable.

So thanks your help.
Gabor

No files, tests, or entry points are named. Start by locating the MJPEG encoding and content transmission flow, then clarify separate quality and speed requirements for static and video content before evaluating lower compression, WebM, or H.265; done means an agreed implementation scope and measurable improvement for both cases.

Written by the indexing model from the issue text.