Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimization: Preconnect to required origins #4171

Closed
rfultz opened this issue Nov 5, 2020 · 0 comments · Fixed by #4449
Closed

Optimization: Preconnect to required origins #4171

rfultz opened this issue Nov 5, 2020 · 0 comments · Fixed by #4449

Comments

@rfultz
Copy link
Contributor

rfultz commented Nov 5, 2020

Background

Looking to optimize the site's performance and that of the homepage specifically, the Lighthouse tool in Chromium browsers has made some suggestions. Some of these will have repercussions throughout the app so we're going to make them their own tickets.

Recommendation: Preconnect to required origins

Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. details

Overview

We could add <link rel="preconnect" elements to the <head>.

Benefit (the 80 of 80/20)

Minimal to significant

Effort (the 20 of 80/20)

Minimal

Complications

  • Adding preconnects that we don't need could technically slow the site but probably not noticeably for humans
  • Would like to avoid adding (and maintaining) tags in multiple places
  • Would need to remember to maintain the list as we add and remove third-party options (e.g., API routes, GA, GTM, CDNs, fonts, map tiles)

Related tickets

This was referenced Nov 5, 2020
@rfultz rfultz self-assigned this Mar 2, 2021
@rfultz rfultz added this to the Sprint 14.1 milestone Mar 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant