Documentation
The ECOS Web Audit is an analytical tool for the technical assessment of websites. The system consolidates technically measurable indicators into a Composite Index evaluating Efficiency, Sustainability (Clean), Openness, and Security (Safe).
The technical implementation is based on a modular architecture utilizing cloud services for hosting, data storage, and backend functions.
Due to its modular structure, the audit engine or API can be used independently of the web app's code – for example, to build a custom REST API or to connect it to a different frontend.
-
Efficiency (Efficient): This area evaluates the volume of transferred data and the number of HTTP requests. Results are benchmarked against global averages to provide performance context. (PageSpeed Insights, HTTP Archive)
-
Sustainability (Clean): Focuses on the ecological balance of the website. The carbon footprint is calculated based on data volume and the energy mix of the hosting data center. Additionally, the server location is identified via IP lookup. (CO2.js, The Green Web Foundation, AbuseIPDB)
-
Openness (Open): This index measures accessibility and Search Engine Optimization (SEO). The goal is to ensure technical accessibility for people with disabilities and the general findability of information. (PageSpeed Insights)
-
Security (Safe): The rating is composed of infrastructure reputation and implemented security features. While reputation is checked against blacklists, SSL certificates and Content Security Policies (CSP) are analyzed through a proprietary logic. (AbuseIPDB, Google Web Risk API, HTTP Observatory Scoring Methodology)
The four areas are not isolated metrics; they reinforce each other. Efficient programming directly reduces energy consumption through smaller data volumes (Clean). Simultaneously, lean code improves loading times, boosting both accessibility and visibility (Open).
Similarly, robust security standards (Safe) increase infrastructure reliability, while a clean technical foundation ensures maintainability and long-term sustainability. The ECOS audit demonstrates that optimizations in one area usually have positive ripple effects throughout the entire system.
| Index | Weighting | Sub-indicators | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Scores | 100% |
|
The project utilizes a serverless-based tech stack:
-
Framework & Runtime:
ReactandReact Routeras a full-stack framework on theNode.jsruntime. (React, React Router) -
Frontend & Visualization:
Radix UIfor accessible components,d3/visxfor complex data visualizations, andTailwind CSSfor styling. (Radix UI, visx, Tailwind CSS) -
Infrastructure Management:
SST(Ion) as an IaC framework for defining and deploying cloud resources. (SST) -
AWS Cloud Services:
-
Data Storage:
DynamoDBas a highly available NoSQL database. (AWS DynamoDB) -
Compute:
Lambda Functionsfor server-side rendering (SSR) and as scalable computing power for performing audits. (AWS Lambda) -
Web Deployment:
S3for static assets,Route53for DNS management, andCloudFrontas a Content Delivery Network (CDN). (AWS CloudFront)
-
Currently, the REST API only supports GET requests to the ECOS database. These provide audit results and daily updated descriptive statistics. Requests to perform or update audits cannot be made via the API at this time.