Updated: 03 November, 2026
If you have asked us what we build websites with, the answer is Gatsby. This post explains, in plain English, why we chose Gatsby web design as our approach, what it does differently from a traditional site, and what that means for you as a business owner in Liverpool or Merseyside. You do not need to know any code to follow it.
We wrote the first version of this post in 2021. Frameworks move quickly, so we have rewritten it to stick to what Gatsby's own documentation says today, and to be honest about where Gatsby is and is not the right tool.
What is Gatsby?
Gatsby is an open source framework for building websites and web apps. It is built on React, a JavaScript library for putting pages together from reusable pieces, which Gatsby calls components. Instead of building each page on a server every time a visitor asks for it, Gatsby does most of the work in advance.
Gatsby's documentation describes two stages. At build time, a server process compiles your site into files that can be delivered to a web browser later. At runtime, a JavaScript layer takes over in the visitor's browser once the first HTML has loaded, so a page can still be interactive. The practical result is that a visitor is usually sent a ready-made page rather than waiting for one to be assembled.
Why we chose it
Speed is built into the approach
Gatsby says its architecture is tailored to make performance fast out of the box, and its documentation has dedicated guides on auditing and improving site performance. For us that matters because speed is part of how a site feels to your customers. Google's Web Vitals guidance describes loading, interactivity and visual stability as the areas that make up a good page experience.
No framework can promise a particular score, and how a site performs still depends on the images, scripts and hosting around it. But starting from pre-built pages gives us a sound base to work from. If speed is your main concern, our post on Core Web Vitals explains what is measured.
It suits search-friendly sites
Google's SEO starter guide is clear that search engines need to be able to find, read and understand your pages. Because Gatsby produces ordinary HTML pages, the content is there for crawlers and visitors alike. That makes the essentials, such as sensible page titles, descriptions, headings and links, easier to get right.
To be clear, using Gatsby does not guarantee rankings. Nobody can guarantee those. What it does is remove some technical obstacles so that the usual good practice has a chance to count.
Your content can live in a CMS you are comfortable with
Gatsby uses GraphQL, a query language, to pull data into your pages. Its documentation explains that data from any number of sources is made available in one unified layer. In plain terms, your pages can draw their content from a content management system (CMS), files or other services, and you can edit your text without touching the code.
We cover the trade-offs of this approach in Headless CMS vs Traditional CMS, so we will not repeat them here. If you would like to be able to update your own pages, a CMS website is the place to start.
Reusable components keep things consistent
Because pages are put together from components, a button, header or booking panel is built once and reused. That helps a site look consistent and makes later changes quicker and less error-prone, which is useful as your business grows.
A large community
Gatsby is open source and has a sizeable community and plugin ecosystem, covering things such as image handling and connecting to data sources. That means we are rarely building common features from scratch. We would rather spend your project's time on the parts that are specific to your business.
When Gatsby may not be the right choice
We choose tools to suit the project, so it is worth saying where Gatsby is not the answer:
Very simple sites. If you need a handful of pages and a contact form, a simpler approach may be all you need.
Sites that change by the second. Pages that depend on live data, such as stock tickers, need extra care, though Gatsby can fetch data in the browser when needed.
Mobile apps. Gatsby is for websites. For apps we use React Native, as explained in Why We Use React Native for App Development.
Technology also changes. We keep an eye on the frameworks we use and would tell you plainly if a different tool suited your project better.
What this means for you
You do not need to choose a framework yourself. What matters is that your site is quick, easy to find, easy to update and built to last. If you would like to talk about how we would approach your site, see our web design service or get in touch.
Frequently asked questions
Gatsby is used to build websites and web apps. It builds your pages in advance from React components and data from sources such as a CMS, so visitors are sent ready-made pages.
No. You will normally manage your content through a simple editing screen, if your site has a CMS, and we look after the technical side. You only need to know what you want your site to do.
Nobody can promise rankings, and we do not. Gatsby produces standard HTML pages that search engines can read, which helps with the technical basics, but rankings depend on many things, including your content and competition.
It can be, depending on the size and needs of the shop. We would look at your products, payments and how often things change before recommending an approach. See our e-commerce websites for what we offer.
Often, yes, but it needs planning so that your current page addresses and content are handled properly. Contact us with your requirements and we can advise.





