Anybody else hating web fonts lately?
It is very frustrating when loading up a website and seeing a mostly blank page because the fonts are still downloading. This is especially frustrating on a slow internet connection or on mobile.
I'm sure that more people will discover and adopt best practices to improve performance and overall user experience over time, but right now I'm noticing this slowdown very frequently. - see http://www.igvita.com/2014/01/31/optimizing-web-font-rendering-performance/ for some notes on best practices
To me, speed is still the most important feature of a website, and it's shocking how bad this experience often becomes when web fonts are added to the equation.
This is one of the biggest problems I have with the current web because of how frequently I'm noticing this.
74 comments
[ 3.2 ms ] story [ 133 ms ] threadI've also noticed that disabling JavaScript has a huge effect on some websites' speed. But other sites don't even work without it nowadays.
I really like typography (calligraphy has been one of my favourite pastimes for many years) but I think its implementation on the Internet is very bad from a usability perspective.
(I suppose you may get web page layouts "jumping" if the downloaded font had very different spacing to the fallback font. EDIT: Ah, just learnt this is called FOUT. http://www.paulirish.com/2009/fighting-the-font-face-fout/ Still, I'd personally prefer FOUT to being unable to read the page.)
I override all web fonts, I just want to use a readable one. There's a noticable trend with embedding icons in fonts. Yahoo mail uses them. This doesn't feel quite right, even if it is a neat hack, and it can be annoying.
How I view Yahoo mail: http://postimg.org/image/unnwg0d9p/
Google use a lot of buttons without text, using icons instead, which a lot of the time are background images. This lends to a lot of mystery meat navigation. Google+ is a bit of nightmare on that front for me.
I don't think my setup is that exotic, all I'm doing is trying to use consistent background and foreground colours, font and text size.
It's amazing how many sites seem to gloss over accessibility.
An instagram page: http://instagram.com/p/ieluJhv-V7/
How it looks to me: http://postimg.org/image/an1jbvf65/
Yup, pretty useless. I've never been able to use/see Instagram pictures without flipping between browsers!
Yes, annoying, can confirm. So I load the page, and all I see are text decorations like underlines, but no text. I have to wait like 1.5-3 seconds, depending on the connection. I mean, seriously, come on!
My personal beef is anything that causes jerky or laggy scrolling. Usually it's caused by parallax and/or fixed fancy header of some sort.
The only parallax effect that I found truly functional was this page: http://www.fiftythree.com/pencil
https://code.google.com/p/chromium/issues/detail?id=336170
https://code.google.com/p/chromium/issues/detail?id=336879
IIRC, Firefox waits a few seconds showing no text. If the font still isn't available, it resorts to fallback fonts and redraws the page if/once the font is actually downloaded.
You know what's annoying? Having to wait.
Waiting is annoying. But at the end of the day, a web without typography freedom is not a web I want, or would value. Especially since I remember what people did when they couldn't have web typography: save it as a one-time use only image.
Sorry, you were saying something about speed?
really? because i spend a lot of time on the web and i've never seen that. You might want to check for problems at your end.
You wouldn't value a web without typographic freedom? That sounds pretty extreme. Are you a designer for whom the web is canvas, rather than a non-designer for whom the web is primarily a source of information?
I've been using the web for twenty years, and typographic freedom is fairly low on my list of priorities. But I'm not a designer.
I've found the font files served by Google fonts are quite large and this is probably because their fonts contain the entire character set. Font Squirrel strips out characters it thinks are not needed.
[1] http://www.interfacesketch.com [2] The font I'm using http://www.behance.net/gallery/ALEO-Free-Font-Family/8018673
There are reasons not to use Google Fonts, but download size is not on that list.
[1] https://developers.google.com/fonts/docs/getting_started#Opt...
[2] https://www.youtube.com/watch?v=sqesm0euf9M
The solution is to make everything as legal as you can, then quietly embed the font files directly into your CSS as data:font urls.
Soon to be fixed! Blink (Chrome, Chrome on Android, Android 4.4+ WebView, Opera) will be implementing new behavior for how webfonts are loaded: http://crbug.com/235303#c17 Basically, you'll only see invisible text for a maximum of 3 seconds (this is the same as Firefox). As Ilya's post also points out, we have strong data on webfont latencies in the wild that supports this behavior.
Further, we're shipping it with Font Load Events so you can customize loading behavior very easily. On the Safari side of things, I've seen WebKit add a radar tracking ticket for font loading behavior, so it seems likely Safari will be updating their style soon as well.
It's great you collected data, but I think the working hypothesis is flawed.
I added a Feedback drawer to the top of my site. Javascript would determine the height of the drawer then set the top position equal to the inverse of it's height. That way the drawer was completely hidden.
However when a font was loaded the height of the drawer changes and then you've got it sticking down over of the top of the page.
These kinds of things are really frustrating. I'd like to see the page not display until the fonts are loaded and I'd like to see Chrome start shipping with some of the more common web fonts included.
A lot of the problem is poorly implemented web fonts that are not optimized, or web designers going crazy and including 6-8 different font/weight combinations. Having half a meg of web fonts download is no different than using way too many images that are not compressed enough.
"Even a few seconds' delay is enough to create an unpleasant user experience. Users are no longer in control, and they're consciously annoyed by having to wait for the computer. Thus, with repeated short delays, users will give up unless they're extremely committed to completing the task. The result? You can easily lose half your sales (to those less-committed customers) simply because your site is a few seconds too slow for each page."[1]
[1] http://www.nngroup.com/articles/website-response-times/
Please experiment this!
You might have lost commits, when the chrome team introduced the Tab-Music-Indicator.
http://www.igvita.com/2014/01/31/optimizing-web-font-renderi...
If you want to define own load behavior: use the upcoming Font Load Events API.
I'm glad there's performance progress, nothing but high praise for Chrome overall. Just weird things to see.
Content is next.
Way way down the list is presentation. Give me ascii text in Courier? That's fine. I'll read that while all the other guff loads in the background.
I was just looking at this today and I agree, 'just give me courier'
I understand the fact that you prefer speed but just speed is not the only solution to effective web design. Typefaces play a very important role in the overall UX of any site.
The web tards would be the first up against my wall.