Audit results for themaybe.org

Results and Sub-scores

ECOS Score and Categories
URL
Date
ScoresTotal ECOS Score v162
Efficient73
Clean19
Open93
Safe62
ECOS Score Display62ECOS Score
Score results compared to audits in the ECOS database.
themaybe.org62
Average (arithmetic mean)68
Statistical distributionp9088
p7580
Median64
p2556
p1051
DatasetLast update9/5/26, 6:57 AM
Number of measurement points (n)831
Statistical distribution of audits6268

How is the score composed?

Visualization of the score composition and weighting of sub-indicators (relative values in brackets)

Composition of the ECOS ScoreECOS Score Display62Scores25%ECOS Score Display73Efficiency25%ECOS Score Display19Clean25%ECOS Score Display93Open25%ECOS Score Display62Safe40% (10%)ECOS Score Display62Performance30% (7.5%)ECOS Score Display100Best Practices30% (7.5%)ECOS Score Display60Network50% (12.5%)ECOS Score Display94Accessible50% (12.5%)ECOS Score Display91SEO50% (12.5%)ECOS Score Display84Trust50% (12.5%)ECOS Score Display40Secure50% (3.75%)ECOS Score Display81Requests50% (3.75%)ECOS Score Display38Data Weight50% (6.25%)ECOS Score Display100Webrisk50% (6.25%)ECOS Score Display67IP Check

Detailed tabular representation of the score calculation and source references for the sub-indicators.

IndexValueWeightingSub-indicators
Scores
62100%
IndexValueWeightingSub-indicators
Efficiency
7325%
IndexValueWeightingData Sources
Performance
6240% (10%)
Best Practices
10030% (7.5%)
Network
6030% (7.5%)
IndexValueWeightingData Sources
Requests
8150% (3.75%)
  • Relative score: Number of HTTP requests (compressed) is put in relation to data from all websites
  • PageSpeed API (Google) - Number of HTTP requests lighthouseResult.audits.network-requests.details.items[].transferSize
  • httparchive.org - Relative frequencies of websites by number of HTTP requests data (2024)
  • Web Audits/GitHub - create_subscore_requests
Data Weight
3850% (3.75%)
  • Relative score: Size of transferred data (compressed) is put in relation to data from all websites
  • PageSpeed API (Google) - Transferred data by type lighthouseResult.audits.network-requests.details.items[].resourceSize
  • httparchive.org - Relative frequencies of websites by transferred data (2024)
  • Web Audits/GitHub - create_subscore_weight
Clean
1925%
Open
9325%
IndexValueWeightingData Sources
Accessible
9450% (12.5%)
SEO
9150% (12.5%)
Safe
6225%
IndexValueWeightingSub-indicators
Trust
8450% (12.5%)
IndexValueWeightingData Sources
Webrisk
10050% (6.25%)
IP Check
6750% (6.25%)
  • AbuseIPDB - Checking if IP address is listed with malware or harmful practices
Secure
4050% (12.5%)

API Sources & Independent Tests

This audit relies heavily on the following APIs. You can run these tests separately here:

Rating Categories

Efficient: Performance & Resources

The Efficient category evaluates how fast and resource-friendly a website works. A high score signals short loading times and a clean technical foundation.

The sub-score is primarily based on Lighthouse metrics for Performance and Best Practices. Additionally, relative benchmarking is performed: transferred data volume and the number of server requests are put in relation to current average values from the HTTP Archive database. This accurately measures how efficiently the site performs compared to global web standards.

Lower CPU load is a side effect — the direct benefit is a better experience for every visitor.

ECOS Score Display73Efficiency
Score results compared to audits in the ECOS database.
themaybe.org73
Average (arithmetic mean)71
Statistical distributionp9097
p7586
Median71
p2556
p1046
DatasetLast update9/5/26, 6:57 AM
Number of measurement points (n)831
Statistical distribution of audits7371

Performance

The Performance score evaluates the speed at which content is loaded and becomes interactive. It analyzes metrics such as the Largest Contentful Paint (LCP) and responsiveness. High performance saves time and reduces battery and CPU load on the user's device.

ECOS Score Display62Performance

Best Practices

This indicator checks compliance with modern web standards. This includes security aspects, correct image formats, and the avoidance of outdated technologies. Following best practices is the foundation for an efficient and maintainable web architecture.

ECOS Score Display100Best Practices

Data Transfer

Here, the data load is evaluated in comparison to the global average (HTTP Archive). The total size of transferred bytes and the number of server requests are measured. Less data traffic means less energy consumption and faster loading times worldwide.

ECOS Score Display60Network

Number of Requests

Every requested file creates communication overhead between the browser and the server. We put the total number of requests in relation to the median of the HTTP Archive database. Fewer requests mean less overhead and a faster-loading page, especially on slow or unstable connections.

ECOS Score Display81Requests

Number of Requests
themaybe.org
33
Statistical distributionp90177
p75114
Median70
p2540
p1021
DataTime2024
Device TypeMobile
Homepage (root page)
Sources
Benchmark vs. HTTP Archive33
HTTP Requests by resource type and origin
HTTP RequestsShare
Data Type
Images1648.48%
Script1236.36%
Fonts26.06%
Style13.03%
Document13.03%
Other13.03%
Media00%
Total33100%
Origin
Third Party3296.97%
Self13.03%
Number of requests by file typeImages (48.48%)Script (36.36%)Fonts (6.06%)Style (3.03%)Document (3.03%)Other (3.03%)Media (0%)Third Party (96.97%)Self (3.03%)
Transferred Data Volume

The total size of the website in kilobytes is measured. This value is compared with average values from millions of websites (HTTP Archive). A low data load saves bandwidth for the user and reduces the energy required for global data transfer.

ECOS Score Display38Data Weight

Data Transfer (in kb)
themaybe.org
3447
Statistical distributionp909603.52
p754702.96
Median2357.43
p251156.58
p10487.09
DataTime2024-06-01
Device TypeMobile
Homepage (root page)
Sources
Benchmark vs. HTTP Archive3447
Data volume type and origin
Data volume (kb)Share
Data Type
Images107061.21%
Script40423.11%
Fonts21612.36%
Style392.23%
Document181.03%
Other10.06%
Media00%
Total1748100%
Origin
Third Party173098.97%
Self181.03%
Data volume by file typeImages (61.21%)Script (23.11%)Fonts (12.36%)Style (2.23%)Document (1.03%)Other (0.06%)Media (0%)Third Party (98.97%)Self (1.03%)

Clean: Ecological Footprint

The Clean area measures the ecological sustainability of digital operations. The focus is on the CO2 balance resulting from hosting and data transfer.

The calculation is performed using the co2.js library and considers two essential factors: the estimated energy consumption per page view and the share of renewable energy in the power grid of the respective server location (Grid Intensity).

A high score shows that the website is operated with minimal CO2 emissions and relies on environmentally friendly infrastructure. This makes the hidden environmental impact of digital products visible and measurable.

ECOS Score Display19Clean
Score results compared to audits in the ECOS database.
themaybe.org19
Average (arithmetic mean)41
Statistical distributionp90100
p7578
Median35
p250
p100
DatasetLast update9/5/26, 6:57 AM
Number of measurement points (n)694
Statistical distribution of audits1941

CO2 Emissions

Greencheck API Results
Sub-areaIndexValue
CO₂How high are the CO₂ emissions of themaybe.org?299.019g CO₂ per 1,000 page views.
CO2.js (Green Web Foundation) rating of themaybe.orgE
Energy sourceDoes the hosting provider of themaybe.org use renewable energy?Yes
Documents

Open: Accessibility and Discoverability

The Open category evaluates how accessible and discoverable a website is for both humans and machines. Transparent structures and open standards are the decisive criteria here.

The score consists of two central Lighthouse audits: Accessibility and SEO. A high value guarantees that content is fully usable for people with disabilities and that technical hurdles do not hinder visibility in search engines.

This supports an inclusive web where content is equally accessible to all users and technologies.

ECOS Score Display93Open
Score results compared to audits in the ECOS database.
themaybe.org93
Average (arithmetic mean)92
Statistical distributionp90100
p7598
Median94
p2588
p1081
DatasetLast update9/5/26, 6:57 AM
Number of measurement points (n)831
Statistical distribution of audits9392

Accessibility

This score indicates how usable a website is for people with disabilities. Aspects such as contrast ratios, screen reader compatibility, and logical structures are evaluated. An accessible web excludes no one through technical barriers.

ECOS Score Display94Accessible

SEO

The SEO score checks technical discoverability by search engines. It ensures that content can be correctly indexed and that metadata is present. Good SEO makes information findable for the people who are looking for it.

ECOS Score Display91SEO

Safe

The Safe score evaluates the technical integrity and reputation of a website. It combines infrastructure checks from AbuseIPDB and Google Web Risk with a security header audit from the MDN HTTP Observatory. This covers both the server's reputation and the implementation of modern encryption and protection standards.

ECOS Score Display62Safe
Score results compared to audits in the ECOS database.
themaybe.org62
Average (arithmetic mean)74
Statistical distributionp9090
p7585
Median73
p2563
p1062
DatasetLast update9/5/26, 6:57 AM
Number of measurement points (n)831
Statistical distribution of audits6274

Trust & Reputation

The integrity of the domain is checked against global databases such as Google Webrisk and AbuseIPDB. This ensures that the site is not known for malware, phishing, or fraudulent activities. This forms the essential basis for digital trust.

ECOS Score Display84Trust

Google Web Risk

This indicator matches the URL against Google's lists of dangerous web resources. It checks whether the site is known for phishing, social engineering, or the distribution of malware. A clean result confirms that visitors are not exposed to malicious content.

ECOS Score Display100Webrisk

AbuseIPDB Check

Here, the reputation of the server IP is checked. AbuseIPDB collects reports on malicious activities such as spam or DDoS attacks. A clean score confirms that the website's hosting environment is not associated with criminal activities.

ECOS Score Display67IP Check

Mozilla HTTP Observatory

The MDN HTTP Observatory is an analysis tool by Mozilla designed to evaluate a website's security header configuration. It helps developers correctly implement modern security standards like CSP, HSTS, and CORS to mitigate risks such as cross-site scripting and clickjacking. (HTTP Observatory Scoring Methodology)

ECOS Score Display40Secure

HTTP Observatory Results
HTTP Observatory Score40/100
HTTP Observatory GradeD+
TestsPassed3
Failed5
HTTP Observatory Tests
TestPassedModifierResultDescription
Content Security Policy-25csp-not-implementedContent Security Policy (CSP) header not implemented
Strict Transport Security0hsts-implemented-max-age-at-least-six-monthsHSTS implemented with max-age of at least 6 months
Content Type Protection-5x-content-type-options-not-implementedX-Content-Type-Options header not implemented
Clickjacking Protection-20x-frame-options-not-implementedX-Frame-Options header not implemented
Referrer Policy-5referrer-policy-not-implementedReferrer-Policy header not implemented
Cookie Security-5cookies-without-samesite-flagCookies set without SameSite flag
Cross-Origin Sharing0cross-origin-resource-sharing-not-implementedContent is not visible via CORS
HTTPS Redirection0redirection-all-httpsSite uses HTTPS

Past Audit Data

Summary
Average62
Number of Audits3

Q & A: Interpretation of Results

How does themaybe.org score in the ECOS audit, and how does it compare to other websites?
The ECOS score is 62/100. The result is in the lower half of the examined websites.
How efficient is themaybe.org in terms of loading speed and data transfer?
The result is above the median of the comparison values. The score is 73/100.
How secure is themaybe.org, and how does it compare to other websites?
With a score of 62/100, the result is in the bottom 25% of audited websites.
How accessible and discoverable is themaybe.org for users and search engines?
The ECOS score is 93/100. The result is in the lower half of the examined websites.
What is the carbon footprint of themaybe.org, and how clean is it compared to other sites?
The ECOS score is 19/100. The result is in the lower half of the examined websites.

Embed Your Audit Badge

Customize your badge below, then copy and paste the generated code into your website.

Color Theme

How "System" mode works: The badge automatically matches your website's styling. It first looks for popular dark/light CSS classes (like .dark or .light-theme) on your page. If none are found, it adapts based on the user's system preferences via CSS media queries.

Code Format

Note: The HTML format fits most use cases, including WordPress, Wix, and standard HTML pages. Choose React if you are pasting the code directly into a React component's JSX.

Size
ECOS Audit: 62 of 100

Raw Data Downloads for themaybe.org

Download raw audit data and ECOS statistics as JSON.

Data can also be accessed programmatically via the REST API. Details can be found in the documentation.

  • Basic Audit Scores: Compact JSON response with the 5 main scores.
  • Full Audit Detail: Detailed analysis results including all technical individual checks.
  • Audit History: Temporal development of scores across all previous measurements.
  • ECOS Benchmark Statistics: Descriptive statistics and percentile distribution of the entire ECOS database.

License: CC-BY-SA 4.0.