Change CDN from multiple options to single and consider using JSDelivr instead

If CDN option is enabled, and you use a JSDelivr as the single provider for all the scripts, you should also do prefetch loading: https://gist.github.com/cliffordp/629735962aebec0afd16feebaaef8da0

If you decide not to use JSDelivr, you could add extra items to that array, such as adding this as well:

$hints[] = [
	'href'        => 'https://use.fontawesome.com/',
	'crossorigin' => 'anonymous',
];

Hi @cliffpaulick,

Thanks for your support on our theme. Please let me check your suggestions and I will apply it on our theme. Expect the changes to the theme sooner or later.

Awesome, thanks!

Glad to see this happened, and so quickly. Thanks so much!

FYI: I noticed wp-bootstrap-starter-fontawesome-cdn handle used even when CDN is not active – just a tweak to the handle name as it shouldn’t have “cdn” in it at all (to be consistent with the other handles you have).

Hi @cliffpaulick,

Thanks for the corrections to make the changes consistent. Expect the changes to the theme sooner or later.

I’m so happy jsDelivr and preloading for it and FontAwesome are part of this theme now! ??

One thing you might want to consider for the jsDelivr links is version aliasing so you don’t have to update the jsDelivr links for each minor version update.

Example from https://www.jsdelivr.com/package/npm/popper.js?path=dist%2Fumd&tab=collection —
use https://cdn.jsdelivr.net/npm/popper.js@1/dist/umd/popper.min.js
instead of https://cdn.jsdelivr.net/npm/[email protected]/dist/umd/popper.min.js

See how the @1 instead of @1.15.0 works?

You still have to update the theme each time an asset is updated because of the self-hosted files, but it might be something to consider if the CDN option is enabled. If you do add it, I’d recommend you mention it working this way at the Customizer option text.

Thanks again!

Hi @cliffpaulick,

Thanks for this information. Expect the changes to the theme sooner or later.

thanks a lot