Quote:
Originally Posted by qualiteam
I'm sorry, but I don't see what problem you want to fix there by switching to a different font provider
|
No problem. Let's agree to disagree
We did say
"it's a minor issue compared to others if we are being honest"
Quote:
Originally Posted by qualiteam
...besides you don't like Google
|
For various factual reasons to be fair. Those that do, simply
don't know, what they don't know when it comes to Google
Quote:
Originally Posted by qualiteam
Browsers cache Google's font files (for a year), and cache the "wrapping" CSS file for a day - this is pretty enough for fast site loading. It may be a good idea to cache some static files forever, but in case of fonts supplied by any third-party provider it is good to have the fonts updated with newer versions released by the supplier
|
Yes to all of this. However, it's not caching per se. It's the 'leverage browser caching' that's the issue we're referring too. Have a look in Stack Overflow or Mobile First Design or anywhere similar. There's no 100% achievable / manageable solution
IF Google Fonts are used. The real irony is that this will show as an issue on Google's own PageSpeed Tests and the relevant section within PageSpeed Tools.
Meanwhile, if other fonts are chosen... well