-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
feat(gatsby-plugin-google-analytics]: DNS prefetch google analytics domain in head #11714
Comments
@m-allanson do you remember if there was reason we added this just for gatsbyjs.org and not to google analytics plugin directly? |
I have no idea why I did it like that 😅 It seems like a good idea to add it to the google analytics plugin though. It's something that gets highlighted during a Lighthouse audit. Looking at the audit for gatsbyjs.org: Does google analytics (GA) always connect to google.com too? That could be worth investigating, and adding if it's a domain that GA always connects to. |
I found all these in source:
but only I can make a PR for that and add these two domains. I would use relative protocol It's also worth looking into this aspect in |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Keep open |
Anyone working on this? I'll pick it up if not. |
@dougwithseismic Thank you for wanting to contribute, sadly we already have support for it and it was added in #12826. I'll be closing this one for that reason. |
Summary
I saw that gatsby website is doing this:
https://github.com/gatsbyjs/gatsby/blob/master/www/gatsby-ssr.js#L10
And I'm wondering if it's a good idea to do it by default in gatsby-plugin-google-analytics.
Motivation
Maybe things will go a little faster with that approach.
The text was updated successfully, but these errors were encountered: