2 ms·
I'd say go a step forward and stick to standard web fonts unless what you're doing really calls for something custom. The vast majority of sites don't actually
by ravenstine 6y ago
I'd say go a step forward and stick to standard web fonts unless what you're doing really calls for something custom. The vast majority of sites don't actually need custom fonts IMO. At the very least, don't use garbage like TypeKit.
- ChrisLTD 6y agoWhat's bad about Typekit?
- ravenstine 6y agoIt requires JavaScript and, in my experience, it can be unnecessarily slow.
- josefresco 6y agoThis aligns with my (albeit limited) experience with TypeKit. The only client project where I was forced to use it, was to appease the design agency who insisted on their font package being used. I still see (naked eye) a noticeable lag or hesitation when that website loads.