[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/case/ - Case Studies

Success stories, client work & project breakdowns
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1772247993014.jpg (146.21 KB, 1080x720, img_1772247983481_ft92fnkf.jpg)ImgOps Exif Google Yandex

b12f2 No.1280

JPEG vs PNG - A Case Study''
In 2019 I faced a challenge with image-heavy pages on our e-commerce site ''Shopify. The homepage was loaded slower than expected, despite using optimized images. After some investigation and testing different formats & compression techniques:
- Before we used mostly PNG for all icons/logos/images bc they support transparency.
img {max-width:100%; height:auto; /'' old way ''/}

- I tested switching to `JPEG` (lossy) and using a tool like TinyJPG
- Result? Homepage load time reduced by 45%!
> "But isn't PNG better for transparency?" asked my designer.
-
> PNG is great when you need transparent backgrounds, but not so much on our mostly solid-colored images. JPEGs are smaller and faster to render.
So if your site has lots of photos w/o alpha channels: **switch from `png` -
> jpeg **
img { max-width:none; width:auto;height auto }

- Don't forget, always test with Lighthouse in DevTools for the most accurate insights.
someone! optimizations

b12f2 No.1281

File: 1772248626204.jpg (112.76 KB, 1600x900, img_1772248611050_1j9ild66.jpg)ImgOps Exif Google Yandex

>>1280
use img srcset and sizes for better responsive image loading on different devices ✔️



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">