4 ms·
The trade-off is that while you're cutting down on a large, and generally blocking request, you're losing cache-ability of that CSS. On the next pageview, your
by joshfraser 13y ago
The trade-off is that while you're cutting down on a large, and generally blocking request, you're losing cache-ability of that CSS. On the next pageview, your browser will have to download that font/CSS again. The best way I've found to handle this is inline it, but use JavaScript to cache it in localStorage. That way you can get the best of both worlds.
- d0vs 13y ago> you're losing cache-ability of that CSS. On the next pageview, your browser will have to download that font/CSS again. That is completely false. A CSS file isn't less cacheable if it embeds inline fonts or images.
- untog 13y agoSome mobile browser caches have an upper limit of file size. I know the iPhone did at launch, but I haven't kept up with the limits.
- joshfraser 13y agoYou don't lose cache-ability because it contains a font. You lose cache-ability if you inline it in your HTML (which I believe was what this article was talking about)