Build logs, code tinkering, and tool recommendations.
View all tags
"No uploads, no backend, therefore secure" is only half true. Removing the server does eliminate a large part of the attack surface, but the risk moves to two places: the visitor's browser and the dependency chain.
"Will adding tools make the homepage slower?" was my own biggest worry. The answer is not to minify harder, but to separate two things: do not pay for a page you never opened, and do not make the first click wait.
A user reported: after compressing, they were not happy with the result and wanted to try another quality, but the button was greyed out, so they had to refresh the page.
My first thought was "user error". My second was "no, this is mine".
jSquash packages mozjpeg, libwebp, and oxipng into browser-ready WASM. The API looks simple: init() then encode(). Wiring it in, I hit three pitfalls.
The laziest image compressor is three lines: createImageBitmap to decode, draw to a canvas, canvas.toBlob('image/webp', 0.75). I built that prototype first, and then found it was nowhere near a "professional compression tool".
This site is hosted on Cloudflare Pages with nothing but build output — no server. Adding an "online tools" section starts with boundaries, not with a tech stack.
A few days of tinkering? Bro, it's the AI era — a few hours, and the Connexion Collective frame is finally up.