3 ms·
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 in
by heretogetout 4y ago
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.
- modeless 4y agoSorry, not since cache partitioning. https://developer.chrome.com/blog/http-cache-partitioning/ https://developer.chrome.com/blog/http-cache-partitioning/ Privacy killed the shared cache.
- SquareWheel 4y agoAnd 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.
- mikeiz404 4y agoYou 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/ https://www.localcdn.org/
- SquareWheel 4y agoIt looks like it's only "officially" supported on Firefox, but I'll give it a try. Thanks.
- mritzmann 4y agoFor data protection reasons, this has not been the case for a long time. Both for Firefox and Chrome.