Kelvin Gobo Software Engineer | Technical Writer | Football #MUFC

Best practices for loading fonts in Vue

4 min read 1180

Vue Logo

Adding fonts should not negatively affect performance. In this article, we will look at best practices for loading fonts in a Vue app.

Properly declare font-face for custom fonts

Making sure fonts are properly declared is an important aspect of loading fonts. This is done by using the font-face property to declare your chosen font. In your Vue project, this declaration can be done in your root CSS file. Before we get into that, let’s look at the structure of the Vue app:


We can make the font-face declaration in main.css like this:

// src/assets/main.css

@font-face {
  font-family: "Roboto";
  font-weight: 400;
  font-style: normal;
  font-display: auto;
  unicode-range: U+000-5FF;
  src: local("Roboto"), url("/fonts/Roboto/Roboto-Regular.woff2") format("woff2"), url("/fonts/Roboto/Roboto-Regular.woff") format("woff");

The first thing to note is font-display: auto. Using auto as the value allows the browser to use the most appropriate strategy to display the font. This depends on some factors like network speed, device type, idle time, and more.

To gain more control of how the font is loaded, you should use the font-display: block which instructs the browser to briefly hide the text until the font has fully downloaded. Other possible values are swap, fallback, and optional. You can read more about them here.

Something to note is unicode-range: U+000-5FF which instructs the browser to only load the required glyph ranges (U+000 – U+5FF). You also want to use woff and woff2 font formats which are optimized formats and work in most modern browsers.

Another thing to note is the src order. First, we check if a local copy of the font is available (local("Roboto")) and use it. A lot of Android devices come with Roboto pre-installed in which case, the pre-installed copy will be used. If a local copy is not available, it goes on to download the woff2 format if supported by the browser. Else, it skips to the next font in the declaration that is supported.

Preload fonts

Once your custom fonts have been declared, you can tell the browser to preload the fonts ahead of time using <link rel="preload">. In public/index.html, add the following:

<link rel="preload" as="font" href="./fonts/Roboto/Roboto-Regular.woff2" type="font/woff2" crossorigin="anonymous">

rel="preload" instructs the browser to start fetching the resource as soon as possible. as="font" tells the browser this is a font so it prioritizes the request. Also note the crossorigin="anonymous" because, without it, the preloaded font will get discarded by the browser. This is because browsers fetch fonts anonymously so using this attribute allows the request to be made anonymously.

Using link=preload increases the chances that the custom font will be downloaded before it’s needed. This small tweak greatly speeds up load times of fonts and consequently, the rendering of text in your web application.

Use link=preconnect for hosted fonts

When using hosted fonts from sites like Google fonts, you can get even faster load times by using link=preconnect. It tells the browser to establish a connection to the domain ahead of time.

If you were using the Roboto font served by Google fonts, you can do this in public/index.html:

<link rel="preconnect" href="">
<link href="" rel="stylesheet">

This will establish the initial connection to the origin and by the time the browser needs resources from the origin, the connection will have already been established. The difference can be seen in the image below:

Without Link Preconnect

When the font is loaded without link=preconnect, you can see the time it takes to connect (DNS lookup, initial connection, SSL, etc). The results look very different when link=preconnect is used like this:

With Link Preconnect

Here, you’ll notice the time taken for DNS lookup, initial connection, and SSL are no longer there because the connection has already been made earlier.

Roboto Font

Cache fonts with service workers

Fonts are static resources that don’t change a lot so they are good candidates for caching. Ideally, your web server should set a longer max-age expires header on fonts so the browser caches them for longer. If you are building a progressive web app (PWA), then you can use service workers to cache fonts and serve them directly from the cache.

To get started with building a PWA with Vue, use the vue-cli tool to generate a new project:

vue create pwa-app

Select the Manually select features option and then select Progressive Web App (PWA) Support:

Creating New PWA Project in Vue CLI

Those are the only things we need to generate a PWA template. Once it’s done, you can change directory to pwa-app and serve the app:

cd pwa-app
yarn serve

You will notice a file registerServiceWorker in the src directory which contains the default configuration. In the root of your project, create vue.config.js if it does not exist or add the following if it does:

// vue.config.js

module.exports = {
  pwa: {
    workboxOptions: {
      skipWaiting: true,
      clientsClaim: true,

The vue-cli tool generates the service worker with the PWA plugin. Under the hood, it uses Workbox to configure the service worker and the elements it controls, the caching strategy to use and other necessary configurations. In the code snippet above, we are making sure that our application is always being controlled by the latest version of the service worker. This is necessary because it ensures our users are always viewing the latest version of the application. You can check out the Workbox configuration documentation to gain more control of the behavior of the service worker that’s generated.

Next, we add our custom font to the public directory. I have the following structure:


Once you are done developing your Vue application, you can build it by running this command from your terminal:

yarn build

This outputs the results into the dist folder. If you inspect the contents of the folder, you’ll notice a file similar to precache-manifest.1234567890.js. It contains the list of assets to cache which is just a list of key-value pairs containing the revision and URLs:

self.__precacheManifest = (self.__precacheManifest || []).concat([
    "revision": "3628b4ee5b153071e725",
    "url": "/fonts/Roboto/Roboto-Regular.woff2"

Everything in the public/ folder is cached by default which includes the custom font. With this in place, you can serve your application with a package like serve or host the dist folder on a web server to view the results. You can find a screenshot of the app below:

Screenshot in Vue App

On subsequent visits, fonts are loaded from the cache which leads to faster load times of your application.


In this post, we’ve looked at some best practices to apply when loading fonts in Vue applications. Using these practices will ensure that you serve fonts that look nice without compromising the performance of your app.

Experience your Vue apps exactly how a user does

Debugging Vue.js applications can be difficult, especially when there are dozens, if not hundreds of mutations during a user session. If you’re interested in monitoring and tracking Vue mutations for all of your users in production, try LogRocket.

LogRocket is like a DVR for web and mobile apps, recording literally everything that happens in your Vue apps including network requests, JavaScript errors, performance problems, and much more. Instead of guessing why problems happen, you can aggregate and report on what state your application was in when an issue occurred.

The LogRocket Vuex plugin logs Vuex mutations to the LogRocket console, giving you context around what led to an error, and what state the application was in when an issue occurred.

Modernize how you debug your Vue apps - .

Kelvin Gobo Software Engineer | Technical Writer | Football #MUFC

9 Replies to “Best practices for loading fonts in Vue”

  1. Doesn’t work for me. Font files get hashed for me so the link src tags in index.html don’t match after webpack processes those files.

    1. Your font files will get hashed if they are somewhere in the “src” folder. Put your fonts assets in the “public” folder as is in the tutorial and this should work.

    1. Your font files will get hashed if they are somewhere in the “src” folder. Put your fonts assets in the “public” folder as is in the tutorial and this should work.

  2. I changed the “href” path to “../fonts/Roboto/Roboto-Regular.woff2”. Note double dots in front. Not sure, but I think it has to do something with how static / relative files are processed by WebPack.

    1. Your font files will get hashed if they are somewhere in the “src” folder. Put your fonts assets in the “public” folder as is in the tutorial and this should work.

    1. Your font files will get hashed if they are somewhere in the “src” folder. Put your fonts assets in the “public” folder as is in the tutorial and this should work.

    2. Build will fail cause webpack can not find relative file in public folder, ./fonts/Roboto-Regular.woff referred in CSS file, which is in src/assets/
      Solution is to put fonts folder also into assets/ folder, and webpack build will work and font files ase copied into “public” or really dist/fonts on build. Also npm run serve will work too.

Leave a Reply