TheAssassin

I have recently discovered a [new app](https://f-droid.org/repository/browse/?fdid=com.orpheusdroid.screenrecorder) for screen recording, if anyone wants to give it a try, it works quite well.

Sounds good. You could try to reduce the quality of the pictures by using a lossy format with a higher than average compression factor, e.g. JPEG with a 75% quality...

If the responsive layout doesn't show the images (`display: none` etc.), the pics aren't loaded IIRC. I think that can be fixed with just some CSS-fu.

> Also you do not use HTTP/2, this makes a real performance difference. Unfortunately, some other websites I maintain cannot support it yet. Believe it or not, but some outdated...

> http2 can be configured per domain in nginx That's unfortunately not possible. One can configure it per _port_, but not per domain. This is due to a technical restriction...

HTTP/2 doesn't permit some known-insecure (but not critically insecure) TLS configurations. Those are of course not the defaults. Those other people I mentioned did find issues on older Linux distros...

> But as my time is limited, please be patient. I'll try to find it again in my huge rubbish heap of links.

@TobiGr I don't think it'll make a huge difference. With the gzip compression the nginx server applies to the HTTP stream whitespace shouldn't be an issue. It'd only increase efficiency...

Sure thing. Do you have suggestions? Otherwise, I'll try the tools I used to use a few years ago.

The common ones, like e.g., https://github.com/mishoo/UglifyJS. I don't recall what I used for CSS, though.