consider decreasing dpi of omega scans to reduce file size

Currently omega scan png's are being rendered at 300dpi. While that's basically the standard minimum for print, it's overkill for web applications.

The recommended image resolution for the web is 72dpi, seeing as almost all monitors can display this without going too low and losing visual quality. Going over this won’t only present a worse-looking image, it will also be bad for SEO, as high DPI also means a larger file size, and as such, longer loading time.

The optimal resolution for images on screen is 72 DPI. Increasing the DPI won’t make the image look any better, it’ll just make the file larger, which will probably slow down the website when it loads or the file when it opens.

The consequences are that, on average the omega scan pngs are 1.5-2.2mb each:

And they represent the dominant source of load time for superevent web views, example:

.

Since O3, there have been improvements to GraceDB's caching framework to reduce server load when rendering web views. However, reducing file sizes for images that get automatically rendered would demonstrably decrease load times for users, and reduce server load and upload times when the files are created.