-
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
perf(www): low-hanging fruit for reducing gatsbyjs.org bundle #21470
Comments
Thanks for letting us know, i'll be changing our bundle strategy so it might solve this problem partially. .org is a mess though 😛 |
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. Thanks for being a part of the Gatsby community! 💪💜 |
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. Thanks for being a part of the Gatsby community! 💪💜 |
Recently @pieh took a bundle analyzer off a recent build of gatsbyjs.org:
I noticed a couple of things that stood out as unnecessary that we should probably fix:
8-double-work.svg
used in a recent blog post, is included for some reasonlayer-model
, which pulls inlayer-icon
. We need to figure out another solution so that these components don't clutter up the bundle.algolia-styles
can probably be lazy-loaded. Even though the search form is included in every page, a lot of these styles involve the actual dropdown and can be loaded later.The text was updated successfully, but these errors were encountered: