Of the many ways you can measure performance on the web, be it initial page load time, runtime efficiency of a web app, or server response times, one of the most well-known is the Lighthouse score. We improved the scores we were receiving on the Gatsby homepage by 22.8 points. Here's how we did it.

Third-party JS are often “death by a thousand cuts” for site performance. When building the StriVectin site, Elevar employed a number of creative solutions to mitigate this impact and still get solid performance.

Gatsby sites are optimized to be smaller, sleeker and faster. When built and deployed in Gatsby Cloud they also use fewer data center resources, thanks to Incremental Builds. This efficiency is not just good for developers — it's also good for the environment!

Looking for a sleeker, faster website, the guitar giant lays down a Gatsby front end.

As Gatsby continues to be used for building larger and more complex sites, we are constantly asking our users and the community how we could improve. Among professional Gatsby developers, we tend to hear less about specific bugs and feature requests and more about qualities they want and need in their site -- faster load times, shorter publish times, and so on.

How JAMstack specialists Jambaree rebuilt Real Cedar's website to perform five times faster while adding a host of new functionality, using headless WordPress powered with Gatsby.

Gatsby helps developers build blazing fast websites. But how fast is build time for the actual website itself? And how can one developer advocate help reduce build times for thousands of others? The Kentico Kontent DevRel team got to work, looking for the answers.

Raleigh Bicycles online presence had a need for speed. The original Raleigh website suffered from slow pageloads and was prone to crashing during traffic spikes, with few options for developers to improve it. Oberon used Gatsby to create a modern and performant site to help Raleigh's customers get wheels.