You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggestion: on the v4 docs jQuery is loaded from the jQuery CDN (https://code.jquery.com/jquery-3.5.1.slim.min.js), with a local fallback. It'd be less HTML code and likely always better for performance if it always loaded jQuery locally. It'll save the cost of opening a new TCP connection (DNS resolution, TCP handshake and TLS negotiation). Browsers don't have Cross-Domain caching so there's no advantage in using a 3rd party CDN anymore (as your site is served from a CDN anyway).
Good explainer here (with Bootstrap being used as the example): https://csswizardry.com/2019/05/self-host-your-static-assets/
The text was updated successfully, but these errors were encountered:
So, I don't think I'd like to make this change right now, and add back a 3rd-party file to track and update. If/when we manage to handle all of our 3rd-party assets through npm, we could definitely do it.
What we could do right now is switch to jsDelivr thus one less CDN.
Suggestion: on the v4 docs jQuery is loaded from the jQuery CDN (https://code.jquery.com/jquery-3.5.1.slim.min.js), with a local fallback. It'd be less HTML code and likely always better for performance if it always loaded jQuery locally. It'll save the cost of opening a new TCP connection (DNS resolution, TCP handshake and TLS negotiation). Browsers don't have Cross-Domain caching so there's no advantage in using a 3rd party CDN anymore (as your site is served from a CDN anyway).
Good explainer here (with Bootstrap being used as the example):
https://csswizardry.com/2019/05/self-host-your-static-assets/
The text was updated successfully, but these errors were encountered: