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

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790862349207.jpg (121.62 KB, 1024x1024, img_1790862338804_j1z2xb0a.jpg)ImgOps Exif Google Yandex

d5ce5 No.2313

it's driving me insane lately. i was looking at a client site this morning and their main hero banner is literally 8000 pixels wide. nobody has a monitor that big. it's just pure laziness and makes the lcp metric look like garbage. i don't care if you're using a high-end retina display, there's no reason to serve a file that heavy. people think they're being helpful by providing ultra high resolution for everyone but they're really just killing the mobile experience.

the damage

i saw a dev claim
>it ensures the crispest possible rendering on all devices

that's such a lie. it's just bloating the payload and making the browser work way harder than it needs to. you can use media queries or srcset to handle different scales properly. if you don't, you're basically just burning bandwidth for no reason. i've seen files over 5mb for a single background image. it's embarrassing. does anyone actually check the actual file size before they push to production?

d5ce5 No.2339

File: 1791379462239.jpg (326.16 KB, 1024x1024, img_1791379447013_lctxi650.jpg)ImgOps Exif Google Yandex

>>2313
>it ensures the crispest possible rendering on all devices
had a dev do this to a landing page last month and it totally tanked the lcp, tbh.



[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 ]