Blog
Every developer has hit this wall. You have a clear performance issue — in this case, a website serving heavy JPEGs instead of optimized WebP images. You know exactly how to fix it: add a script to the server that auto-converts images on upload.
Then you talk to the DevOps team. Or the security team. Or the “compliance” committee.
“We need a security review."
"That’s not in the current sprint."
"Wait for the next server migration.”
Suddenly, a three-hour fix turns into a three-month waiting room. Most people just give up and wait.
I didn’t want to wait. If I couldn’t touch the server, I would touch the only other part of the stack I controlled: the browser.
I built a Chrome extension.
Instead of trying to fix the image pipeline on the backend, the extension intercepts the upload process in the browser. When a user drags an image into the CMS, the extension catches it, converts it to WebP locally using the browser’s own capabilities, and then sends the optimized version to the server.
The server doesn’t know anything changed. It just receives a smaller, faster file. No security review for the server was needed because the server code remained exactly the same.
This isn’t just about images. It’s about a shift in mindset.
In traditional web development, we are taught to solve problems where they “belong.” Backend problems get backend solutions. But in a corporate environment, the “correct” place is often the most restricted place.
Chrome extensions, userscripts, and edge functions are the “guerrilla warfare” of modern development. They allow you to ship value to the user without getting bogged down in the bureaucracy of the core infrastructure.
The client didn’t care that the images were being converted in the browser instead of the server. They cared that their PageSpeed score jumped 20 points in 48 hours instead of four months.
By thinking around the blocker instead of pushing against it, you deliver results while everyone else is still filling out Jira tickets.
If you are stuck waiting for a “proper” fix that might never come, look for a side door. The browser is a powerful environment. If you can’t change the engine, you can still change the fuel.
At ilf.studio, we specialize in finding these “side doors” to deliver performance and features when the traditional path is blocked.
ilf.studio — AI-native web studio, Gdansk, Poland.