undefined | Better HN

0 pointsheretogetout4y ago0 comments

If the font is already in your browser cache (which it might be if they're hosting it on a common CDN) web pages should load with the correct font right away instead of either loading blank areas or a default fallback font before switching to the correct font, causing jank.

The best solution here is to use standard fonts that are available in all browsers, of course.

0 comments

4 comments · 2 top-level

modeless4y ago· 2 in thread

Sorry, not since cache partitioning. https://developer.chrome.com/blog/http-cache-partitioning/

Privacy killed the shared cache.

SquareWheel4y ago

And it's such a niche privacy issue too. I would gladly take a shared cache over cache isolation. Especially for something used on as many sites as Google Fonts is.

mikeiz4044y ago

You may be interested in the LocalCDN extension [1] which tries to solve the privacy vs speed issue for common resources by intercepting known remote resource requests and returning a local copy.

1: https://www.localcdn.org/

1 more reply

mritzmann4y ago

For data protection reasons, this has not been the case for a long time. Both for Firefox and Chrome.

j / k navigate · click thread line to collapse