: Pros and cons of the Google font API I am currently using a font from the google font directory on my website. I don't fully understand how it works, but it seems like when someone opens
I am currently using a font from the google font directory on my website. I don't fully understand how it works, but it seems like when someone opens my site, their browser is told to go and fetch the font from Google. (correct me if I'm wrong).
Now, what I'm wondering is, what are the pros and cons of this over just specifying a font family the old-school way? Presumably doing it the google font directory way has the advantage that they'll definitely see the font I want them to. (as long as the font directory is up).
But does this way have disadvantages? Maybe using fonts that are stored locally speeds up the site loading?
More posts by @Bethany197
1 Comments
Sorted by latest first Latest Oldest Best
Using local fonts will definitely be faster then loading fonts from Google fonts or from any remote website. However, you are limited to whatever fonts the user has on their system and the fonts available on each system (Windows, Mac, Linux) will vary.
If you absolutely must use a certain font on your pages then the Google Font API is the way to go. However, if you don't absolutely need it, use CSS to list multiple fonts and allow the system to fall back to whatever font it has. So if the user doesn't have that fancy font they the system can fall back to a similar one.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.