Tinloof

Our website was first built with Gatsby.js, and our content was managed without a CMS.

Recently, problems affecting our content editing experience piled up and we decided to take care of that.
Tinloof
Tinloof
Check out the live version here

Website updates took too long to be live

Every time we pushed a piece of content, Gatsby had to build all our pages. We don't have many website pages, but we do have a lot of blog posts.

The more blog posts we added the slower our build got. This continued until our builds started failing since our deployment platform was timing out.
Build time

Not having a CMS slowed us down

Since we didn't have a CMS, our content was mixed in with our code.

Changing or producing content meant creating code that had to be reviewed and deployed.

This slowed us down and made us less motivated to produce new content.

10 times faster content updates with Sanity CMS

Thanks to a Sanity CMS integration, we can now create, live preview, and publish any page without deploying a single line of code.

This made our content production 10 times faster and more enjoyable.

14 times faster deployments with Next.js

Just by moving from Gatsby to Next.js, our build became 14 times faster.

We also used this opportunity to migrate from JavaScript to TypeScript to catch errors before they are even deployed and make code more predictable.
Build duration after Next.js

100 Ahrefs Score

We also spent some time improving our SEO scores and have managed to reach 100/100 on Ahrefs.

We focused mainly on image optimization, URL structure improvements, meta and OG tags updates, and dynamic sitemap set-up.
Ahrefs Perfect Score

Final touches

We replaced Google Analytics with Fathom, which is a much simpler analytics platform.

We also made a few minor improvements to improve our Google Lighthouse scores.
100

Performance

100

Accessibility

100

Best Practices

100

SEO