3 ms·
For Google Fonts, it's best practice to leave out the protocol and link to '//fonts.googleapis.com/...'. It's unhelpful that their link generator still suggests
by WiseWeasel 10y ago
For Google Fonts, it's best practice to leave out the protocol and link to '//fonts.googleapis.com/...'. It's unhelpful that their link generator still suggests 'http://fonts...' http://fonts...'.
- spiderfarmer 10y agoOr just download them and serve them from your own domain. If you enable HTTP/2 there is little to no advantage of using a third party for hosting fonts.
- bowersbros 10y agoWont they be cached from other peoples websites saving the download?
- spiderfarmer 10y agoNo. Well, maybe, if you're using one of the most popular fonts, but each combination of weights is a seperate CSS file, that's probably a unique combination and only cached for 24 hours. A reason not to use Google fonts is that it's just another tracking tool in their arsenal. For each request, cookies are sent to Google's servers, so they have enough reason to avoid cache hits.
- MarkyC4 10y agonowadays I just use 'https://...' https://...' instead of '//...' because * security * I will immediately know if a server doesn't support https, because the image won't load