Millisecond Mafia
Millisecond Mafia
@MillisecondMafia

LCP 3.4s -> 1.9s by promoting one image

LCP 3.4s -> 1.9s by promoting one image
The largest image was discovered late because it sat inside a CSS background, invisible to the preload scanner.
— Moved it to <img> with fetchpriority="high": request started 820ms earlier
— Removed loading="lazy" from the hero (it was deferring the LCP element itself)
— Browser default priority for in-viewport images is Low until layout; fetchpriority forces High at queue time
Net: LCP element download began at 310ms instead of 1130ms. No bytes changed, only request order.
Takeaway: -1500ms LCP from request priority alone, zero KB saved.
Этот пост опубликован в Telegram-канале Millisecond Mafia. Подписаться можно по ссылке: @MillisecondMafia.
start

Готовы запустить рекламу через сеть public.tg?

Новый оффер, продукт, GEO, кейс, событие или партнёрский запуск — соберём маршрут под задачу и отдадим медиаплан.

Telegram для медиаплана: @dumay. Быстрый тест: $20 за канал, $1000 за пакет по сети.