Audit results for fandom.com

Results and Sub-scores

ECOS Score and Categories
URL
Date
ScoresTotal ECOS Score v154
Efficient48
Clean0
Open87
Safe80
ECOS Score Display54ECOS Score
Score results compared to audits in the ECOS database.
fandom.com54
Average (arithmetic mean)67
Statistical distributionp9088
p7579
Median62
p2555
p1051
DatasetLast update6/6/26, 7:25 AM
Number of measurement points (n)673
Statistical distribution of audits5467

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 Display54Scores25%ECOS Score Display48Efficiency25%ECOS Score Display0Clean25%ECOS Score Display87Open25%ECOS Score Display80Safe40% (10%)ECOS Score Display61Performance30% (7.5%)ECOS Score Display73Best Practices30% (7.5%)ECOS Score Display7Network50% (12.5%)ECOS Score Display82Accessible50% (12.5%)ECOS Score Display92SEO50% (12.5%)ECOS Score Display100Trust50% (12.5%)ECOS Score Display60Secure50% (3.75%)ECOS Score Display0Requests50% (3.75%)ECOS Score Display14Data 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
54100%
IndexValueWeightingSub-indicators
Efficiency
4825%
IndexValueWeightingData Sources
Performance
6140% (10%)
Best Practices
7330% (7.5%)
Network
730% (7.5%)
IndexValueWeightingData Sources
Requests
050% (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
1450% (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
025%
Open
8725%
IndexValueWeightingData Sources
Accessible
8250% (12.5%)
SEO
9250% (12.5%)
Safe
8025%
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
6050% (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 Display48Efficiency
Score results compared to audits in the ECOS database.
fandom.com48
Average (arithmetic mean)69
Statistical distributionp9096
p7584
Median69
p2555
p1044
DatasetLast update6/6/26, 7:25 AM
Number of measurement points (n)673
Statistical distribution of audits4869

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 Display61Performance

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 Display73Best 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 Display7Network

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 Display0Requests

Number of Requests
fandom.com
211
Statistical distributionp90177
p75114
Median70
p2540
p1021
DataTime2024
Device TypeMobile
Homepage (root page)
Sources
Benchmark vs. HTTP Archive211
HTTP Requests by resource type and origin
HTTP RequestsShare
Data Type
Images6430.33%
Script7133.65%
Other5927.96%
Fonts41.9%
Style104.74%
Document31.42%
Media00%
Total211100%
Origin
Third Party15071.09%
Self6128.91%
Number of requests by file typeImages (30.33%)Script (33.65%)Other (27.96%)Fonts (1.9%)Style (4.74%)Document (1.42%)Media (0%)Third Party (71.09%)Self (28.91%)
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 Display14Data Weight

Data Transfer (in kb)
fandom.com
8185
Statistical distributionp909603.52
p754702.96
Median2357.43
p251156.58
p10487.09
DataTime2024-06-01
Device TypeMobile
Homepage (root page)
Sources
Benchmark vs. HTTP Archive8185
Data volume type and origin
Data volume (kb)Share
Data Type
Images246058.74%
Script122929.35%
Other3307.88%
Fonts882.1%
Style571.36%
Document230.55%
Media00%
Total4188100%
Origin
Third Party377090.02%
Self4189.98%
Data volume by file typeImages (58.74%)Script (29.35%)Other (7.88%)Fonts (2.1%)Style (1.36%)Document (0.55%)Media (0%)Third Party (90.02%)Self (9.98%)

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 Display0Clean
Score results compared to audits in the ECOS database.
fandom.com0
Average (arithmetic mean)36
Statistical distributionp9099
p7574
Median24
p250
p100
DatasetLast update6/6/26, 7:25 AM
Number of measurement points (n)592
Statistical distribution of audits036

CO2 Emissions

Greencheck API Results
Sub-areaIndexValue
CO₂How high are the CO₂ emissions of fandom.com?833.842g CO₂ per 1,000 page views.
CO2.js (Green Web Foundation) rating of fandom.comF
Energy sourceDoes the hosting provider of fandom.com use renewable energy?No
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 Display87Open
Score results compared to audits in the ECOS database.
fandom.com87
Average (arithmetic mean)91
Statistical distributionp90100
p7597
Median93
p2587
p1081
DatasetLast update6/6/26, 7:25 AM
Number of measurement points (n)673
Statistical distribution of audits8791

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 Display82Accessible

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 Display92SEO

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 Display80Safe
Score results compared to audits in the ECOS database.
fandom.com80
Average (arithmetic mean)74
Statistical distributionp9090
p7585
Median73
p2563
p1062
DatasetLast update6/6/26, 7:25 AM
Number of measurement points (n)673
Statistical distribution of audits8074

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 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 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 Display60Secure

HTTP Observatory Results
HTTP Observatory Score60/100
HTTP Observatory GradeC+
TestsPassed4
Failed4
HTTP Observatory Tests
TestPassedModifierResultDescription
Content Security Policy0csp-implemented-with-no-unsafeContent Security Policy implemented with no unsafe directives
Strict Transport Security-20hsts-not-implementedHTTP Strict Transport Security (HSTS) header not implemented
Content Type Protection-5x-content-type-options-not-implementedX-Content-Type-Options header not implemented
Clickjacking Protection0x-frame-options-implementedX-Frame-Options header properly implemented
Referrer Policy-5referrer-policy-not-implementedReferrer-Policy header not implemented
Cookie Security-10cookies-without-secure-flagCookies set without Secure flag
Cross-Origin Sharing0cross-origin-resource-sharing-not-implementedContent is not visible via CORS
HTTPS Redirection0redirection-all-httpsSite uses HTTPS

CrUX Reports: Real User Experience

The CrUX Reports (Chrome User Experience Report) provide valuable insights into the actual performance of a website from the perspective of real users worldwide.

Unlike lab tests, this data reflects real conditions: varying hardware, network speeds, and browser configurations. Since these metrics are a key ranking factor for Google, they show immediately how the website performs in the everyday life of visitors.

The analysis is carried out on two levels to evaluate both the specific subpage and the quality of the entire domain (Origin).

CrUX Page

This indicator shows performance data for the exact URL tested. It provides information on how specific content and functions of this individual page are experienced by real users in everyday life. This is useful for checking whether improvements to a specific page have had the expected effect.

CrUX results
IndicatorScore (CrUX)Score (linear)ValueDistribution (CrUX API)
OverallFAST80
Cumulative Layout Shift (value)fast1000CrUX Performance Distribution0.00.20.40.60.81.0Percentile0102030ms
Experimental Time to First Bytefast96579CrUX Performance Distribution0.00.20.40.60.8Percentile05001000150020002500ms
First Contentful Paint (in ms)fast951304CrUX Performance Distribution0.00.20.40.60.8Percentile01000200030004000ms
Interaction to Next Paintfast94176CrUX Performance Distribution0.00.20.40.60.8Percentile0200400600ms
Largest Contentful Paint (in ms)fast961710CrUX Performance Distribution0.00.20.40.60.8Percentile0100020003000400050006000ms

CrUX Origin

The Origin score aggregates user experience data across the entire domain. This provides a comprehensive overall picture of the technical quality of the website infrastructure. It helps determine whether performance issues affect the whole site or only specific pages.

CrUX results
IndicatorScore (CrUX)Score (linear)ValueDistribution (CrUX API)
OverallFAST80
Cumulative Layout Shift (value)fast990CrUX Performance Distribution0.00.20.40.60.81.0Percentile0102030ms
Experimental Time to First Bytefast95610CrUX Performance Distribution0.00.20.40.60.8Percentile05001000150020002500ms
First Contentful Paint (in ms)fast951354CrUX Performance Distribution0.00.20.40.60.8Percentile01000200030004000ms
Interaction to Next Paintfast93180CrUX Performance Distribution0.00.20.40.60.8Percentile0200400600ms
Largest Contentful Paint (in ms)fast961733CrUX Performance Distribution0.00.20.40.60.8Percentile0100020003000400050006000ms

Past Audit Data

Summary
Average54
Number of Audits1

Q & A: Interpretation of Results

How does fandom.com score in the ECOS audit, and how does it compare to other websites?
With a score of 54/100, the result is in the bottom 25% of audited websites.
How efficient is fandom.com in terms of loading speed and data transfer?
With a score of 48/100, the result is in the bottom 25% of audited websites.
How secure is fandom.com, and how does it compare to other websites?
The result is above the median of the comparison values. The score is 80/100.
How accessible and discoverable is fandom.com for users and search engines?
The ECOS score is 87/100. The result is in the lower half of the examined websites.
What is the carbon footprint of fandom.com, and how clean is it compared to other sites?
The ECOS score is 0/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

Raw Data Downloads for fandom.com

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.