Third-party domains

Third-party domains are a common Core Web Vitals issue. First of all, each third-party domain needs a new connection. That means time is lost on a DNS lookup, a TCP handshake and a TLS negotiation. If you had served those resources from your main domain, the browser could have re-used the connection that is already open (that is why you want HTTP/3: one fast, re-usable connection for everything you control). When that domain serves a font or a stylesheet, the browser cannot render before the connection is ready. The connection setup delays the LCP.

Also, third-party resources are usually out of your control. They can become a SPOF (single point of failure) when their server is slow or down. They can also change in size or behaviour without your knowledge, and your Core Web Vitals change with them. Self-hosting fixes both problems at once. Preconnect only hides part of the connection cost.

How do third-party domains affect the Core Web Vitals?

Passing LCP barely moves across the range: 89% at one end, 87% at the other. This signal does not separate passing sites from failing ones.

The effect is bigger on CLS. With a single third-party domain, 86% of sites pass it. Among the sites with the most third parties, 73% do. Third parties inject ads, embeds and consent banners, and injected content moves the layout after the page looks done.