[Jonas_ba]

Indeed, actually right now our trackers represent quite a big chunk of the website size, but we made sure that they are all async loaded so they don't impact the site that much. It's something that we are aware of and pushed a bit for internally but since we are still evaluating tools and learning, we decided to keep them for now. I'm sure that once we have the right one, we'll decrease that part quite a bit :)

[jacquesm]

I've gone down this same optimization route for some of my sites and disabling trackers was one of the biggest contributors. If you have to have trackers consider loading them only on a small percentage of your users to get you a statistically relevant sample. This will at least give the bulk of your users a vastly better experience. You'll need to scale the percentage of users you do put the trackers on with your traffic.

[boreas]

That's an interesting idea. Seems like it would be hard to get a representative sample though if the trackers themselves affect the user experience.

[ronpeled]

My team just completed a similar performance optimization for a massive ecommerce site. The 3rd party javascript libraries are a huge penalty in performance. The second you get those out of the way and loading async or after page loads, you can start breathing again.

Most 3rd party tools should seriously start evaluating how they offer JS inclusions into web pages.