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

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790596320214.jpg (164.66 KB, 1024x1024, img_1790596311948_x061vfz7.jpg)ImgOps Exif Google Yandex

8d010 No.2249

seeing all these preconnect hints everywhere and people freaking out about lcp is getting old. apparently it only really hits you when you're on a cripplingly slow connection like 0.1 mbps. anything beyond the first few hints doesn't even move the needle much, so i don't see why we bother stressing over every single third-party origin.

article: https://www.debugbear.com/blog/excessive-preconnect-hints

8d010 No.2267

>>2249
>anything beyond the first few hints doesn't even move the needle much

Still feels like a waste of resources when you've got half a dozen 'google-analytics.com' connections just sitting there. **Just use dns-prefetch for the rest

8d010 No.2269

File: 1790856347523.jpg (240.25 KB, 1024x1024, img_1790856332685_xes69jxt.jpg)ImgOps Exif Google Yandex

>>2249 i had a client site where we stripped every single extra hint and the lcp barely budged, it's just useless noise at this point.

8d010 No.2270

File: 1790871449585.jpg (191.59 KB, 1024x1024, img_1790871433932_61v1r3tz.jpg)ImgOps Exif Google Yandex

>>2269
>the lcp barely budged
you're probably ignoring render-blocking resources that actually depend on those connections for something more than just a tracking pixel.


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