Transitioning from WordPress to Astro: Performance, Cost, and Sustainability Benefits

For years, WordPress served as the platform of choice for blogging, but a transition was needed to better align with contemporary values, both environmental and financial. This post outlines the motivations behind the move to an Astro application deployed on Azure Static Web Apps.

While WordPress has been a powerful blogging tool with extensive features and a vibrant community, the decision was made to shift. The blog now operates as a static web application built with Astro and published on Azure Static Web Apps. The reasons for this change are multi-faceted.

Social and Ecosystem-Related Considerations

Over 15 years, WordPress has undergone significant evolution, introducing features like the Gutenberg editor and seamless automatic updates for its core system and plugins. While these updates initially simplified blog management, they have recently introduced new risks.

Concerns within the WordPress ecosystem have emerged regarding actions by its co-founder, which some observers suggest are undermining the platform's stability and community spirit. Automatic updates, despite their convenience, imply that the server's running code could be altered at any time, a level of unpredictability that became unacceptable.

The WordPress community, including prominent figures like Joost de Valk (Yoast), has been a significant strength. However, recent controversies involving leadership and community members have reinforced the decision to explore alternatives. While these community dynamics were a contributing factor, they were not the sole motivation for moving away from WordPress.

Environmental Benefits of Static Sites

Operating a WordPress blog necessitates a server and database running continuously, 24/7. Even during periods of inactivity, these resources remain operational. Beyond the virtual machine (VM) itself, continuous operation extends to storage, virtual networks, and backup services, leading to substantial annual energy consumption.

Consider the estimated annual power usage for a typical "Standard B2ls v2" VM:

• Average Power Usage: 50W
• Annual Power Consumption: 50W \u00d7 24 hours/day \u00d7 365 days/year = 438 kWh/year
• Equivalent Carbon Emissions: 438 kWh/year \u00d7 0.475 kg CO\u2082/kWh = 208.05 kg CO\u2082/year (based on an average for The Netherlands)

These figures highlight how an always-on VM significantly contributes to both energy consumption and a larger carbon footprint.

By transitioning to a static web app, the website's energy consumption and environmental impact are substantially reduced. With Astro, compute power is primarily utilized only during content generation when blog updates occur. The static web app then serves pre-generated content, eliminating wasted server resources during idle times, offering an efficient alternative to continuous VM hosting.

Financial Advantages of Static Web Apps

While WordPress itself is free, the associated Azure resources incur costs. Hosting a WordPress site requires a perpetually active VM, storage, networking, and backups, which accumulate expenses over time.

A breakdown of previous Azure expenses for the WordPress setup revealed:

• VM Cost: \u20ac28.91/month
• Storage and Networking: \u20ac11.21/month
• Total Annual Cost: \u20ac481.44/year

Switching to Azure Static Web Apps has eliminated these recurring costs. Static web hosting is not only more environmentally friendly but also considerably more economical. The solution now operates on Azure's Free tier, which includes SSL certificates and custom domains without charge, making it ideal for a personal blog.

Furthermore, a previous annual expense of approximately \u20ac59 for WP Rocket, used for optimization (minification, gzip compression, caching), has been eliminated. Azure Static Web Apps now provide gzip and Brotli compression inherently, while Astro automatically handles output minification. This means no additional plugins are required, streamlining operations and reducing costs further.

The positive outcomes are evident, with Google Lighthouse scores now consistently achieving 4 x 100 (performance, accessibility, best practices, SEO), provided heavy embeds like YouTube videos are avoided.

The Investment in Transition

The adoption of Astro was a new endeavor, requiring time and effort to build a blog that mirrored the previous site's functionality. While not every feature is available "out of the box," the platform's flexibility proved invaluable. Blog posts are now authored locally using Visual Studio Code, and the entire blog can be run in seconds by executing npx astro dev.

Future posts will delve into the specifics of the Astro setup, web components, and how previous WordPress plugin functionalities were replaced.

Ultimately, this transition has been highly successful. The blog is now faster, cheaper, greener, and no longer constrained by WordPress update cycles or ecosystem concerns. Those considering a similar shift are encouraged to share their experiences.