Web
Audits

Audit results for zing2.app

Results and Sub-scores

ECOS Score and Categories
URL
Date
ScoresTotal ECOS Score v170
Efficient70
Clean39
Open95
Safe75
ECOS Score Display70ECOS Score
Score results compared to audits in the ECOS database.
zing2.app70
Average (arithmetic mean)66
Statistical distributionp9089
p7578
Median61
p2555
p1051
DatasetLast update2/1/26, 6:25 AM
Number of measurement points (n)333
Statistical distribution of audits7066

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 Display70Scores25%ECOS Score Display70Efficiency25%ECOS Score Display39Clean25%ECOS Score Display95Open25%ECOS Score Display75Safe40% (10%)ECOS Score Display67Performance30% (7.5%)ECOS Score Display100Best Practices30% (7.5%)ECOS Score Display44Network50% (12.5%)ECOS Score Display89Accessible50% (12.5%)ECOS Score Display100SEO50% (12.5%)ECOS Score Display100Trust50% (12.5%)ECOS Score Display50Secure50% (3.75%)ECOS Score Display35Requests50% (3.75%)ECOS Score Display53Data Weight50% (6.25%)ECOS Score Display100Webrisk50% (6.25%)ECOS Score Display100IP Check

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

IndexValueWeightingSub-indicators
Scores
70100%
IndexValueWeightingSub-indicators
Efficiency
7025%
IndexValueWeightingData Sources
Performance
6740% (10%)
Best Practices
10030% (7.5%)
Network
4430% (7.5%)
IndexValueWeightingData Sources
Requests
3550% (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
5350% (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
3925%
Open
9525%
IndexValueWeightingData Sources
Accessible
8950% (12.5%)
SEO
10050% (12.5%)
Safe
7525%
IndexValueWeightingSub-indicators
Trust
10050% (12.5%)
IndexValueWeightingData Sources
Webrisk
10050% (6.25%)
IP Check
10050% (6.25%)
  • AbuseIPDB - Checking if IP address is listed with malware or harmful practices
Secure
5050% (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.

Efficiency here not only reduces CPU load but directly improves the user experience.

ECOS Score Display70Efficiency
Score results compared to audits in the ECOS database.
zing2.app70
Average (arithmetic mean)68
Statistical distributionp9096
p7584
Median67
p2554
p1044
DatasetLast update2/1/26, 6:25 AM
Number of measurement points (n)333
Statistical distribution of audits7068

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 conserves the hardware resources of users.

ECOS Score Display67Performance

Best Practices

This indicator checks compliance with modern web standards. This includes security aspects, correct image formats, and the avoidance of outdated technologies. Clean best practices form the foundation for a long-lasting, 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 directly means less energy consumption and faster loading processes worldwide.

ECOS Score Display44Network

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 significantly faster page build, especially with unstable connections.

ECOS Score Display35Requests

Number of Requests
zing2.app
96
Statistical distributionp90177
p75114
Median70
p2540
p1021
DataTime2024
Device TypeMobile
Homepage (root page)
Sources
Benchmark vs. HTTP Archive96
HTTP Requests by resource type and origin
HTTP RequestsShare
Data Type
Script7275%
Fonts44.17%
Images33.13%
Style33.13%
Document11.04%
Other1313.54%
Media00%
Total96100%
Origin
Third Party1717.71%
Self7982.29%
Number of requests by file typeScript (75%)Fonts (4.17%)Images (3.13%)Style (3.13%)Document (1.04%)Other (13.54%)Media (0%)Third Party (17.71%)Self (82.29%)
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 Display53Data Weight

Data Transfer (in kb)
zing2.app
2215
Statistical distributionp909603.52
p754702.96
Median2357.43
p251156.58
p10487.09
DataTime2024-06-01
Device TypeMobile
Homepage (root page)
Sources
Benchmark vs. HTTP Archive2215
Data volume type and origin
Data volume (kb)Share
Data Type
Script57972.83%
Fonts10913.71%
Images435.41%
Style344.28%
Document212.64%
Other81.01%
Media00%
Total795100%
Origin
Third Party28635.97%
Self50964.03%
Data volume by file typeScript (72.83%)Fonts (13.71%)Images (5.41%)Style (4.28%)Document (2.64%)Other (1.01%)Media (0%)Third Party (35.97%)Self (64.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 invisible environmental impacts of digital products transparent and evaluable.

ECOS Score Display39Clean
Score results compared to audits in the ECOS database.
zing2.app39
Average (arithmetic mean)32
Statistical distributionp9097
p7572
Median0
p250
p100
DatasetLast update2/1/26, 6:25 AM
Number of measurement points (n)333
Statistical distribution of audits3932

CO2 Emissions

Greencheck API Results
Sub-areaIndexValue
CO₂How high are the CO₂ emissions of zing2.app?233.307g CO₂ per 1,000 page views.
CO2.js (Green Web Foundation) rating of zing2.appD
Energy sourceDoes the hosting provider of zing2.app 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.

Openness thus promotes an inclusive internet and ensures that information remains equally accessible to every user group.

ECOS Score Display95Open
Score results compared to audits in the ECOS database.
zing2.app95
Average (arithmetic mean)91
Statistical distributionp90100
p7596
Median92
p2586
p1080
DatasetLast update2/1/26, 6:25 AM
Number of measurement points (n)333
Statistical distribution of audits9591

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 inclusive web is an open web that excludes no one through technical barriers.

ECOS Score Display89Accessible

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 openly accessible and visible to the relevant target group on the net.

ECOS Score Display100SEO

Safe

The Safe index evaluates the technical integrity and reputation of a website. It combines infrastructure analysis from AbuseIPDB and Google Web Risk to detect malware or blacklisting with an in-depth audit of HTTP security headers via the MDN HTTP Observatory. This multi-layered approach ensures that both the server's reputation and the implementation of modern encryption and protection standards are verified.

ECOS Score Display75Safe
Score results compared to audits in the ECOS database.
zing2.app75
Average (arithmetic mean)74
Statistical distributionp9090
p7585
Median73
p2563
p1063
DatasetLast update2/1/26, 6:25 AM
Number of measurement points (n)333
Statistical distribution of audits7574

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 Display100Trust

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 negative result guarantees that visitors are protected from 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 Display100IP 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 Display50Secure

HTTP Observatory Reults
HTTP Observatory Score50/100
HTTP Observatory GradeC
TestsPassed5
Failed3
HTTP Observatory Tests
TestPassedModifierResultDescription
Content Security Policy-25csp-not-implementedContent Security Policy (CSP) header not implemented
Strict Transport Security-20hsts-not-implementedHTTP Strict Transport Security (HSTS) header not implemented
Content Type Protection0x-content-type-options-nosniffX-Content-Type-Options header set to 'nosniff'
Clickjacking Protection0x-frame-options-implementedX-Frame-Options header properly implemented
Referrer Policy-5referrer-policy-unsafeReferrer-Policy set to unsafe value
Cookie Security0cookies-not-foundNo cookies detected
Cross-Origin Sharing0cross-origin-resource-sharing-not-implementedContent is not visible via CORS
HTTPS Redirection0redirection-all-httpsSite uses HTTPS

Branding

Website information (collected via an HTTP request without execution of client-side scripts)
Title
Description

Past Audit Data

Summary
Average70
Number of Audits1

Q & A: Interpretation of Results

To what extent does zing2.app follow technical best practices regarding sustainability and security, what is the total ECOS score, and how does the result compare with other sites?
The result is above the median of the comparison values. The score is 70/100.
How efficiently is zing2.app optimized regarding data transfer and loading speed, how does the site perform in the ECOS audit in this regard, and how does it stand compared to the competition?
The result is above the median of the comparison values. The score is 70/100.
What about technical security and privacy protection on zing2.app, how high is the ECOS Safe score, and how secure is the site in direct comparison with other sites?
The result is above the median of the comparison values. The score is 75/100.
To what extent does zing2.app rely on open standards and digital accessibility, how many points does the site achieve in the ECOS Open rating, and how inclusive is it compared to other websites?
The result is above the median of the comparison values. The score is 95/100.
How sustainable is the ecological footprint of zing2.app through optimized resource use, how high is the ECOS Clean score, and how does the result compare to other examined sites?
The result is above the median of the comparison values. The score is 39/100.

Raw Data Downloads for zing2.app

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.