Conversation

Chromium is looking to ship full network state partitioning. We have already lost the HTTP cache shared between sites; with this things like H2/H3 connections H3 TLS resumption, & DNS cache are also partitioned. This substantially increases the perf impact of 3P resources.
Quote Tweet
Blink: Intent to Ship: Network State Partitioning groups.google.com/a/chromium.org
2
55
I think everybody got the memo by now, but the time for third party resources is done for the web; especially if they are close to the critical path. If you continue to need to make 3P requests redirect them through a quick edge function hosted on your favorite CDN
7
34
Replying to and
This also works far better with HTTP/2 and HTTP/3 since it multiplexes over one connection and builds up throughput. It's unfortunate Chromium is phasing out push at the same time. It's primarily beneficial when all your resources are first party especially when self-hosting it.
1
1