It looks like you're new here. Sign in or register to get started.
Johannes Neumeier said:
@Dave Crossland The base64 encoding doesn't get the benefit of caching; maybe negligible for a "font presentation" stub. But for reducing requests, absolutely.
John Butler said:
We have the bandwidth now to return to bitmap fonts, an idea promoted by Letterror for decades. Is there an existing way to do it on a website?
Roel Nieskens said:Regarding inlining fonts in CSS, caching is indeed not the problem, and there are actually benefits, but you'd need to weigh the pros and cons carefully.
Florian Pircher said:
WOFF2 is now widely supported, so[…] much narrower user agent support but smaller file sizes (WOFF2)is no longer the con it once was. However, base64-encoding data will increase its byte size by about ⅓. So while you will save an additional request, the server now might need to send more data over the wire and do it without the option to do so in parallel.
Johannes Neumeier said:...just had this mental "base 64 no no" sign flashing in my mind.
Seems I needed reeducating about base64 encoded webfonts entirely, thanks!