I recently migrated my blog website from Gatsby v2 to the Astro framework, and I’m thrilled to share that the average desktop PageSpeed Insights score is now 100!
You can see the report here:

Table of contents
Open Table of contents
Why I migrated from Gatsby to Astro
While Gatsby is powerful, my blog was built using gatsby-theme-blog and plugins like:
- Google Tag Manager
- Sitemap
- Manifest
It also had some missing features like pagination, blog tags, and better code snippet support, which I had implemented with custom code.
Astro offered several advantages:
- Faster builds and minimal JS by default
- Built-in support for pagination, tags, and code snippets
- Tailwind CSS integration out-of-the-box
- Lightweight and easy to maintain
This made Astro the perfect fit for my blog’s needs while keeping it highly performant.
How I achieved 100 PageSpeed score
Some key steps that made the difference:
- Minimal JavaScript
- Astro only ships JS when necessary,
reducing render-blocking scripts.
- Optimized Images
- All images were converted to
WebP formatfor faster loading and smaller file sizes.
- Pre-rendered Pages
- All pages are static HTML with Astro’s
SSR, improvingLCPandFCPmetrics.
- Tailwind CSS with Purge
- Only used utility classes that are actually in the HTML,
keeping CSS minimal.
- Third-Party Scripts in Isolation
- All third-party scripts, including Google Tag Manager, were moved to a
worker threadto run in the background without blocking the main thread.
- Extended Features
- During the migration, I also extended several blog functionalities:
- Dynamic page title handling
- Displaying code snippets with proper styling
- WebP image conversion for better performance
- Google Tag Manager executed within the worker thread
How this relates to any stores
Achieving high PageSpeed scores is not only for blogs. In any store, performance directly impacts:
- Conversion rates
- SEO rankings
- Customer satisfaction
My experience migrating a real-world site to Astro while achieving a perfect PageSpeed score reflects my ability to:
- Audit frontend bottlenecks
- Optimize JS, CSS, and images
- Deliver lightning-fast storefronts
To learn more about performance optimization strategies I implement in Magento/Hyvä projects, feel free to connect.
Final thoughts
Migrating from Gatsby to Astro for a content-driven site:
- Reduced complexity
- Enabled native tags + pagination
- Achieved
100 PageSpeed score - Extended features for better SEO, code display, and WebP optimization
This demonstrates that careful framework choices and optimization strategies can make a huge difference.