Submitted by nofue on Thu, 07/29/2021 - 11:00 Nice article, although there's a "load" missing in the first paragraph ("… will load faster …"). In addition, avoiding any link to non-EU servers is mandatory for EU sites. I suggest not to use the CSS as generated, but instead using a "proxy-fontname" -- it's a lot easier to change fonts later. In the same sense I prefer linking the font.css to the main.css instead of pasting the code. F.e. I use to have my font-sets named: basic-font - header-font - callout-font throughout the CSS, and for the font.css I link the actual font to the proxy. I use to keep all fonts-files of a family in the font directory, linking only the fonts I really need for a certain site. This way it's much easier to test certain weights. I also don't like to put font files into the themes folder -- I prefer treating fonts as 'unrelated resources' which can be used by various themes, especially in a multi-site setup. So most of my installations have font's installed in files/fonts. Finally, the sad part of the story is that there are fonts which cannot be downloaded, such as Noto Sans KR (Korean) -- latin fonts in general seem to be fine.