Create an Icons component, served from that replaces the current implementation. A good starting point is this article by Sarah Drasner:

We have three libraries and five extensions. They all hope that font-awesome has been loaded AND that an icon sheet lives at . Those are odd assumptions, and they can lead to issues when we host at non-root URLs.

The suggested change, linked to above, allows for animation-ready SVG icons that are accessible, less error prone, and significantly more flexible.