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

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790941563341.jpg (189.73 KB, 1024x1024, img_1790941554129_fswm84e9.jpg)ImgOps Exif Google Yandex

86458 No.2401

im looking at this list of stuff to fix before code freeze hits and it is basically just more work. using google tag manager to bypass code changes for rum sounds like a total nightmare for debugging.
>Use a tag manager (e.g, Google Tag Manager) or A/B testing tool if you need to circumvent code changes.
im pretty sure that just makes the site even slower with all those extra third-party tags and stuff. plus relying on crUX data instead of actual monitoring is basically just guessing at this point.

full read: https://www.speedcurve.com/blog/holiday-readiness-checklist-page-speed

86458 No.2410

>>2401
gtm is just a way to hide how much junk you're actually loading. my last project had like fifty different marketing pixels all firing at once and the lcp was absolutely trashed. it makes debugging impossible when you can't even see where the extra requests are coming from in the source code. plus relying on crux is basically just looking at old news. by the time that data updates, your site has already crashed under the traffic load lmao.

86458 No.2424

>>2410
>lcp was absolutely trashed
marketing people love adding mystery scripts that just kill the lcp. basically just turning your site into a giant pile of junk for the sake of some 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 ]