@barcode20 there’s not enough information in your question for me to understand the issue.
It sounds like you might be saying that your web page as a <link> element whose href points to stylesheet that tries to load a webfont from the URL you provided, and that webfont is not available at that URL.
If so, then using this plugin wouldn’t eliminate that problem.
Unless it happens that there’s a theme or plugin loading that stylesheet, which this plugin’s Conflict Detection Scanner could detect, and block. That would stop it from trying to load that asset. It would load Font Awesome a clean way instead. See my comments over here on this other topic about how to use the Conflict Detection Scanner like that.
