Gatsby: slow builds and heavy JS, per users
Gatsby is a real option for React developers building a content site, not a framework past its prime — the performance defaults, automatic code splitting, image optimization, and prefetching, work without extra tuning. The main trade-off: the GraphQL data layer and the Lerna monorepo structure are extra concepts a solo developer has to learn on top of React itself.
In a GitHub issue, dustinhorton, 2018-07-22 reported that "gatsby develop hangs on source and transform nodes after querying a large WordPress installation (~9000 posts, ~35 pages)" and asked what size is too big for Gatsby to handle. The thread has since been closed after 156 comments; whatever fix came out of it is not in the excerpt.
Two more complaints from GitHub issues point at the build and the output. kuworking, 2020-05-22 wrote about a "significant worsening of lighthouse results when comparing lighthouse v5.6 vs the new 6.0" on their own sites, in a thread that collected 94 reactions. antoinerousseau, 2019-11-19 described "multiple Bugsnag reports from Safari and Mobile Safari" for an error inside the generated production-app.js. Both are closed too.
Gatsby is a React framework under the MIT license, written in JavaScript, and its README promises performance by default and no manual tuning. The repository dates from 2015-05-21 and has collected 55,914 stars. A push landed on 2026-11-11, while 461 issues remain open.
The oldest opinions sit in a Hacker News thread from 2016 and describe the version of that day. xrstf, 2016-07-20 wondered "why I (as the visitor) need to download a 700KB JS blob" when the pages work with JavaScript disabled. kup0, 2016-07-20 put the same worry as arithmetic: "the only important part of the site (the content) is 20KB in size, and that the other 498KB is mostly for developer convenience". greenspot, 2016-07-21 went further with "Over-engineering at its best. React is great but so wrong for an SSG". Not everyone agreed. eschutte2, 2016-07-20 used it for a client's static site that sat next to an existing React app, and said "using React for the static site gave us a consistent way to get composition of components".
More recently, JR-Carroll, 2024-08-12 opened a discussion titled "Is GatsbyJS Officially Dead?", writing "I can't get Netlify to respond" and citing online rumors that the original team had left. Separately, ushakov, 2022-04-19 remarked in a Hacker News reply that "gatsbyjs (React framework) has so many dependencies it breaks GitHub's dependency graph". That is an aside, not a measured review.
What I have is a small, uneven sample: nine mentions across two platforms, most of them years old, which cannot tell you how the current version behaves. Before adopting it, run gatsby develop against your largest content source and read the replies in the 2024 discussion.
Related repositories
Is gatsby worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of gatsby.
