Why we built OmegaPix — the problem that every image-heavy WordPress site has
Every image-heavy WordPress site has the same problem. Someone uploads a 4MB JPEG from their phone or from a stock photo site. WordPress generates a few thumbnails. The original sits in the media library untouched. That image loads for every visitor, on mobile and desktop both, and it adds two to four seconds to the page load time. Multiply that by 20 images on a product page and you understand why so many WordPress sites are slow no matter what else you do.
We had been fixing this problem manually for clients for two years. Optimize images, convert to WebP, set up lazy loading, implement proper srcset. The tools to do it piecemeal existed. What did not exist, or did not exist in the form we needed, was something that handled all of this automatically and consistently without requiring ongoing manual attention.
So we built OmegaPix.
What it actually does
OmegaPix is a WordPress plugin that handles image optimization end-to-end on upload and on an ongoing schedule for existing media. New images get converted to WebP automatically. Oversized images get resized to a defined maximum dimension. Metadata gets stripped. Lazy loading attributes get added correctly. The media library queue gets processed in the background without affecting site performance.
The part that matters most for our clients is the batch processing of existing media. A client site that has been running for three years might have 1,500 images in the library, almost none of them optimized. Running a manual optimization pass on that library is hours of work and it needs to be repeated when new images are added. OmegaPix does it automatically on a schedule.
What we learned building it
We spent the first six weeks building the wrong thing. The initial version tried to handle too many edge cases up front: responsive images with complex art direction, multiple CDN configurations, integration with page builders. It was slow and complicated and we had not proven the core value yet.
We stripped it back to the essentials. Upload a file, optimize it, convert it, store it. Everything else was secondary. The version that worked was much simpler than the version we had originally designed, and it worked better because it was simpler.
Building OmegaPix taught us something we probably already knew but needed to feel: scope creep is not just a client project problem. It happens to your own work too, maybe more, because there is nobody to push back on you.