Forem: waqas buzdar

I built a 100% Privacy-First Image Converter using Alpine.js & Tailwind

waqas buzdar — Sun, 15 Mar 2026 16:16:31 +0000

As developers, we often need to convert images or optimize them for performance. But I always hated uploading my private project images to some random cloud server just to convert them to WebP or PNG.
I wanted a tool that:
Runs locally: No backend, no storage, no uploads.
Privacy-First: Everything happens inside the browser.
Fast: No server lag or network latency.
So, I built WebPConvert.pro.
It uses standard browser APIs to handle image processing. No heavy libraries or backend infrastructure needed. It’s been a great exercise in understanding how much we can actually do on the client-side without relying on a server.
If you’re a developer who values privacy and site speed, check it out and let me know what you think! Would love some feedback on how to improve the compression engine.

How I Optimized My Client-Side Image Tool to Hit a 99/100 Google PageSpeed Score

waqas buzdar — Thu, 26 Feb 2026 17:12:54 +0000

Google loves fast websites, but achieving a near-perfect score while keeping a tool functional is a challenge. Today, I’m happy to share that my project, WebPConvert.pro, officially hit a 99/100 Desktop Performance Score.
Here’s a quick breakdown of how I did it and why I built it:
The Challenge: Privacy & Speed
Most online converters require you to upload your files to their servers. This is slow and risky for privacy. I wanted to build a 100% Client-Side tool where images never leave your browser.
How I Optimized for 99/100 Score:
Eliminated Render-Blocking Resources: I moved heavy JavaScript libraries (like Alpine.js and the compression engine) from the

to the bottom of the .
Lean HTML/CSS: Used Tailwind CSS but kept the implementation lightweight to ensure the "Converter Box" renders instantly.
Lazy Loading Logic: The heavy lifting (image processing) only kicks in when the user interacts with the tool, keeping the initial load lightning-fast.
The Tech Stack:
Alpine.js: For lightweight reactivity.
Tailwind CSS: For a modern, responsive UI.
Browser-Image-Compression: To handle local processing.
The result? Instant conversions, total privacy, and a score that Google loves.
Check out the live tool here: WebPConvert.pro
I’d love to hear your feedback on the performance or the UI!

I built a 100% Client-Side Image Compressor & WebP Converter (Zero Server Uploads)

waqas buzdar — Tue, 24 Feb 2026 15:16:51 +0000

Hi DEV Community! 👋
As web developers and bloggers, we compress and convert images daily. But I noticed a huge privacy issue: Most free image converters force you to upload your files to their servers.
I didn't want my private or client images sitting on a random server. So, I built a solution: WebPConvert.pro.
Here is why it's different:
🔒 100% Privacy: The entire conversion (WebP ↔ PNG/JPG) and compression happen client-side in your browser using JavaScript.
⚡ Lightning Fast: Since there are no server uploads or downloads, it's instant.
📉 SEO Friendly: Great for compressing images to boost your website's PageSpeed.
I built the frontend to be super lightweight and fast. I am currently trying to get some initial users and would absolutely love your feedback on the UI and performance!
🔗 Try it here: https://webpconvert.pro
Let me know what you guys think or if you have any feature requests! 👇