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
Instead of including the files with chaise, we should let a CDN host it for us to improve site speed, especially for popular tools on popular CDNs — like using Google's hosted jQuery.
The text was updated successfully, but these errors were encountered:
I would disagree with making our sites have an unnecessary run-time
dependency which we do not control nor sub-contract.
If we really have an optimization goal for a remote client where the
CDN-based cache helps dramatically, we would need to consider how to
apply the CDN benefit to all our real science assets as part of the
solution. I don't think a few JS libraries or other static files are
worth targeting on their own.
But, if these static assets are a substantial part of the request
latency, we should consider how to solve that from our own hosted
copies. For example: minification, pre-compressed encodings, removing
gratuitous asset references, combining many small assets into a few
larger ones, or introducing asynchronous prefetching so the UX does
something useful prior to fetching everything.
Hmm I didn't think about the dependency control thing 😞
Actually, I was looking at PageSpeed Insights to see how we could speed up Chaise, and its suggestions overlap with a lot of your suggestions as well. Perhaps we could use PageSpeed like a checklist?
Instead of including the files with chaise, we should let a CDN host it for us to improve site speed, especially for popular tools on popular CDNs — like using Google's hosted jQuery.
The text was updated successfully, but these errors were encountered: