Contra - A professional network for the jobs and skills of the futureOptimizing a Next.js Logo to Improve Lighthouse Performance
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
A small implementation detail was quietly hurting the performance of my own website.
The MKP Digital logo looked completely normal in the browser. Under the hood, however, the original 296 KB PNG was being embedded directly in the code as a Base64 data URI.
That turned roughly 296 KB of image data into almost 395 KB of inline data, while also preventing the logo from behaving like a normal, independently cacheable static asset.
I replaced the implementation with a proper static PNG import through Next.js and reduced the image itself from 296 KB to 187 KB.
The production results after the change:
Mobile Lighthouse Performance: 76 → 94 Median LCP: 5.51s → 2.99s Logo size: 296 KB → 187 KB Base64 source: ~395 KB → removed
That is a 46% reduction in median LCP and a 37% smaller logo asset.
No redesign. No major rewrite. The website looks exactly the same.
It was simply a case of finding one inefficient implementation and fixing it properly.
Performance issues are not always caused by something complex. Sometimes a seemingly insignificant asset is enough to make a measurable difference.
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started