Self-hosting fonts vs loading from Google

Self-hosting fonts vs loading from Google

Both give you nice type, but the loading path differs. Google Fonts adds a hop to another server first. Self-hosting means the font lives on your own domain, so the browser fetches it without that detour.

The detour can delay text appearing, which shows up as a slower LCP (Largest Contentful Paint).

When each makes sense:
— You want the fastest text and control over caching: self-host, drop the font files in your project.
— You're prototyping or rarely touch the site: Google's link tag is simpler.

Try this: if you self-host, add font-display: swap in your CSS so text shows in a backup font immediately, then swaps when yours loads. No blank wait for readers. This is less work than it sounds, often two lines.