More environmentally friendly websites
Every page load consumes energy. We minimise it.
The average web page produces about 0.5 grams of CO2 per page load. That does not sound like much, but globally the internet produces more emissions than aviation.
Kotisivukamu websites are built with technology that significantly reduces the energy consumption of every page load compared to traditional website solutions.
Static website vs. traditional website
Kotisivukamu (static)
- Server computation: None at all. Pages are pre-built files.
- Page size: Typically 50–200 KB
- Delivery: From a CDN edge server close to the user
- Background processes: No continuously running server processes
- Third-party scripts: None
Traditional (e.g. WordPress)
- Server computation: PHP execution and database queries on every page load
- Page size: Typically 500 KB – 3 MB
- Delivery: From a single server (often far from the user)
- Background processes: MySQL, PHP, scheduled tasks, plugins
- Third-party scripts: Often 5–15 (analytics, chat, cookie banner)
Estimated impact
For a small business with 5,000 page loads per month, the difference is about 2–3 kg CO2 per year (Kotisivukamu) compared to 15–50 kg CO2 per year (traditional WordPress solution).
Where does the saving come from?
No server-side computation
A traditional site runs PHP code and database queries on every page load. A static site is a pre-built file that is simply sent to the user. This is the single largest source of energy savings.
Smaller page size
Kotisivukamu websites are typically 50–200 KB, while a traditional WordPress page can be 1–3 MB. A smaller page size means less data transfer and less energy on both the server and the user's device.
Edge delivery (CDN)
The site is served from a global CDN network, so data travels a shorter distance to the user. A shorter network path means less energy in routers and switches.
No constant load
A traditional web host runs database and PHP processes continuously, even when no one is using the site. A static site has no continuously running processes.
In the spirit of honesty
Building the site initially using AI consumes energy. A single build step can consume the equivalent of hundreds of page loads on a traditional site. However, this one-time cost is spread across thousands of page loads over the site's lifetime and becomes negligible within the first few weeks.
The figures above are estimates based on well-known differences between static and dynamic websites. We have not yet conducted precise measurements of our own service. Figures vary depending on site size, traffic and infrastructure used.