More like FIXING by REMOVING the target feature
I also vote for placing Font Awesome in your theme/plugin and properly enqueueing it.
Using a CDN for Google Web fonts is one thing – if they don’t load, you have a system fallback.
If Font Awesome icons don’t load, you’ll get a bunch of unknown characters since they’re not in the standard unicode set.Sidenote: loading jQuery from a CDN is your choice if you’re managing your own site (though then you have to manually keep it up to date), but if you are releasing a theme or plugin publicly you should NEVER do that – it would be very irresponsible (and also isn’t allowed by ThemeForest)
For jQuery in WP, i agree, using CDN version is bad practice as WP has built in jQuery library. But for HTML templates i think CDN version is better (for caching and other benefits). However, if you want to be on safe side you can always include local jQuery version as fallback. Same goes for CSS.
But yes, one can simply use local files for the sake of simplicity
I do not know whether the use of a CDN is ok in this case, what if the template you bought a few thousand times and CDN stop working? This is not a large file, it is better to have it locally.
The answer is same i think, what if google fonts api site goes down? as most of the templates/themes here use those fonts. Although, in this case file size is only 20 KB, its not much, it goes down to ones own choice. However, speaking generally, there are many advantages of using CDN version: Why should I use Google’s CDN for jQuery?
It’s simple to do without a plugin:
1) upload the css and font files to your theme folder2) Add the CSS to WP head by using the enqueue_style function (link)
We can actually strip out step one by using CDN link to CSS file. e.g.