The marketing team wants another analytics script on a site already loading a tag manager, chat widget and advertising pixels. Each vendor claims negligible overhead, but together they slow the first interaction noticeably on a phone. I'm considering an audit of which events anyone actually uses, then delaying or removing unnecessary third-party code. How do you frame that discussion in terms stakeholders care about, rather than only Lighthouse scores?
Balancing third-party analytics scripts against page speed
- webdev
- balancing
- third
- party
55
3 replies
I’d frame it as a user cost, not a tech purity argument. If the script delays interaction on phones, that means slower form fills, fewer con...
I’d frame it as a user cost, not a tech purity argument. If the script delays interaction on phones, that means slower form fills, fewer conversions, and more support headaches.
Also ask what decision the script changes. If nobody can name the action they take from that data, it’s usually easier to cut or delay.
I’ve had better luck with “what do we lose if this loads 2 seconds later?” than with performance charts. People understand losing a sale fas...