unacms
use cwebp instead squash.app
https://github.com/unacms/UNA/issues/2984 #2984 Here are the five key points comparing server performance between cwebp and Squoosh.app:
Speed – cwebp runs natively in C/C++ and supports multi-threading, making it dramatically faster on servers than Squoosh’s browser-based WebAssembly engine.
Scalability – cwebp handles batch conversions and automation easily via scripts or CI/CD pipelines; Squoosh is limited to single-image manual compression.
Resource usage – cwebp consumes less memory and CPU since it executes outside a browser sandbox, while Squoosh may slow or crash under heavy loads.
Integration – cwebp fits neatly into web servers (like Nginx/Apache) for automatic conversion; Squoosh has no direct server integration.
Purpose – cwebp is ideal for backend optimization and automation, while Squoosh is best for design-side, visual image tuning
@AlexTr after each upload it can convert to webp mime type that is well compressed , so image is still foo.jpg but mime type is webp without changing the code base
