Performance Optimization on Eifel42

Lighthouse Score 100

Thu, 09 Oct 2025 00:00:00 +0200

This summer, I embarked on a journey to revise the layout of my blog. An update to my Hugo theme customization led to a significant increase in the complexity of the CSS structure. As a result, I faced layout breaks and received disappointing scores on Google’s PageSpeed Insights. Today, I proudly celebrate my achievement: my personal blog now boasts a perfect score of 100 points in both mobile and desktop categories. Determined to make a change, I gradually refactored my site to improve its Lighthouse score.

One of the most valuable lessons I learned is that optimizing website performance strengthens both security and architecture Lighthouse - Best Pratices. Throughout the optimization process, Software Architecture in Stream shared a truly inspiring Web Performance session.

Performance (Mobile)

Performance (Desktop)

EU Website Evidence Collector moves to code.europa.eu

Sun, 31 Aug 2025 13:00:00 +0200

Introducing the Free GDPR Compliance Helper

The European Union has introduced an excellent resource: a free GDPR compliance tool. → Discover the tool. To use it in a DevOps pipeline is mentioned here: → Explore Automating GDPR Checks.

Hosting Update

The Website Evidence Collector has transitioned from GitHub to the EU’s GitLab-based platform at code.europa.eu. This move not only enhances long-term accessibility but also aligns with the European Commission’s commitment to open-source initiatives.

New Download (v3.7.0)
EDPS - website-evidence-collector v3.7.0 - downloads

Wishing you a successful and (cookie-free) deployment experience!

European Union provides a GDPR compliance tool Website

Sat, 13 Jan 2024 20:14:39 +0100

Website Evidence Collector

The European Union announced a tool for GDPR compliance checks for websites. This tool can be used manually, in an automated deployment process, and security vulnerability checks. It can be an easy and cost-efficient approach for small and medium companies (Mittelstand).

Carbon Footprint of static and dynamic websites

Mon, 01 Jan 2024 14:05:12 +0100

Why Hugo?

The decision to switch from WordPress to a static website engine like Hugo was easy.

Once, my provider complained about the version of PHP and wanted to charge me extra for running an older PHP version.
Furthermore, a modern and beautiful WordPress site requires a lot of time.
Another time, the My SQL database had problems, and I lost my settings and content.
During the years, I got a lot of attack attempts from all over the world. E.g., the Kali Linux distribution contains a free, open-source vulnerability scanner for WordPress (wpscan).
At least run such a system; you need more diligence on the European GDPR.

In conclusion, you need a lot of time for administration and extra knowledge to run WordPress. I grew up as a software developer developing web-based information systems and found running WordPress too complicated for my use cases.

Hugo lets me concentrate on the essentials. Like now, I can quickly write something in Markdown. You can store the text file and all modifications in a Source Repository like GitHub. The access times to my content have improved considerably.

Intention

The CO2 emissions of a static website seem many times lower. It may be a small step to save the planet, but if it suits your business or use cases, it can help.

Microsoft Copilot

Disclaimer: The following section is entirely AI-generated.
USE CASE: demonstrate and compare modern AI Assistants.

Question

Please compare the co2 food print static website to wordpress

Microsoft Copilot Answer

The carbon footprint of a website depends on various factors, including the design, the number of page views, and the efficiency of the underlying technology.

An average website produces 4.61 grams of CO2 for every page view¹. For websites that have an average of 10,000 page views per month, that makes 553 kilograms of CO2 per year¹. According to the Website Carbon Calculator, the average web page they test produces approximately 0.5 grams of CO2 per pageview². That translates to 60 kg of CO2 per year for a website with 10,000 monthly pageviews².