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

Intent To Ship

@intenttoship

Feb 1

Blink: Intent to Ship: Network State Partitioning groups.google.com/a/chromium.org

Malte Ubl

@cramforce

Feb 8

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

Replying to

So stuff like Google Fonts, CDN hosted JS libs etc should be avoided?

Replying to

Google Fonts: self host them CDN hosted JS libs: same

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.

7:50 AM · Feb 8, 2022Twitter Web App

Replying to

and

Push isn't beneficial to sites based around having most of the static assets on a different server from the HTML. It wasn't usable. It's immensely helpful when it's all on one server and you don't have extremely low RTT from centralizing the web around a few CDN providers...