Also was on my TODO list.

Updating the screenshot could be later automated with Playwright maybe (or some other headless browser tool)

Once in 10 5 years would be enough :D

I assume the PNG could be compressed (further?) too

related: FreshRSS/freshrss.org#79

I noticed that the original screenshot from freshrss.org is a way smaller WebP (60 KiB instead of 216 KiB, also better quality)
Any reason not to switch to WebP?

I assume the PNG could be compressed (further?) too

This type of screenshot can be exposed to pngquant (lossy) with no perceptible loss in quality at about a third of the size.

I noticed that the original screenshot from freshrss.org is a way smaller WebP (60 KiB instead of 216 KiB, also better quality)

Mind, the blurriness (which I'd rather do without) likely contributes to increasing the filesize in this instance.

I would be fine with WebP too as it is used on the website. Currently I just replaced the exisiting PNG with a new one.

@Alkarex What do you think? WebP is widely supported by all/the most browsers. Any objections?

As stated the screenshot on the website is already WebP. ;-)

I would suggest a screenshot with a bit more information like in the old one (e.g., multiple feeds, some unread articles, some labels...)