Gatsby Guides

What makes Gatsby sites so fast?

Your team probably doesn’t have the time for 40 item performance checklists, so Gatsby bakes these improvements in at the framework level.

“To paraphrase Tolstoy, all fast websites are alike, but all slow websites are slow in different ways.” — Kyle Mathews, creator of Gatsby

Making fast websites is hard.

With the complexity of web technology stacks today, it’s easy for performance to suffer death by a thousand cuts. Is your site slow because of your e-commerce backend? Your caching configuration? Your Javascript? The answer is yes.

Moreover, site performance isn’t just a technological challenge. It’s also an organizational challenge. If one team owns the CMS, another owns the UI and another owns the app server, coordinating around performance improvements becomes difficult.

To paraphrase Tolstoy, all fast websites are alike, but all slow websites are slow in different ways.

The good news is that there are established patterns for improving website performance, no matter what your initial setup looks like. The bad news is that front-end performance checklists are 40 items long (example).

Your team probably doesn’t have the time for a checklist that long, and that’s okay. Our approach is different — Gatsby bakes these performance improvements in at the framework level. We nerd out about performance, so you don’t have to.

As a result, people use adjectives for Gatsby sites like “disgustingly fast.” Users report speedups between 3x and 10x after migrating a website to Gatsby.

Ready to Get Started?