At the beginning of his post, he introduced the advantages of Google fonts, including ease of use, rich font library, etc., which is why more than 42 million websites are still in use. However, at the cost of performance, many users have feedback on the cost of multiple requests. If you still want to keep your speed up, the best way to do this is to download the Google fonts you’ve already used and host them locally. < / P > < p > this is not a new practice, it has been advocated for many years. Even Google recommends that others host their own fonts when it comes to performance at the I / O Developers Conference in 2018. In essence, even with all the font and CSS optimizations, Google Fonts is no faster than self hosted fonts. < / P > < p > SIA wrote an article that compared the performance of Google fonts and self hosted fonts without CDN impact. < / P > < p > if the best performance is self hosting fonts, what makes developers believe that Google Fonts is close to self hosting? Google Fonts is designed to be distributed on global CDNs and can take advantage of caching. Users request fonts through the CDN, and it is likely that they have downloaded font resources from other sites. However, since the release of chrome 86 in October 2020, cross site resources such as fonts can no longer be shared on the same CDN. This is because the browser cache is partitioned (Safari has been in use for many years). Safari does care about privacy. It has bypassed this cross site tracking attack for years. And finally there was chrome. Other chrome based browsers should follow up. < / P > < p > whether it is cached on the CDN or not, the Google fonts resource is re downloaded for each site. Obviously, self managed fonts get better performance, and the old performance parameters are no longer valid. SpaceX beat blue origin and Northrop Grumman to win a $316 million air force contract