Scoring methodology
This page precisely documents how the three scores shown on the "Our tools" page are calculated and refreshed. No fabricated data, no simulated measurement. Every number comes from a verifiable public source.
Last score update: 2026-04-30T16:17:01+00:00 (UTC).
Score sources
The three indicators come from independent third-party services. The links below lead to their official documentation:
Mozilla HTTP Observatory (security)
Automated audit of HTTP security headers (CSP, HSTS, X-Frame-Options, etc.). Result: a letter grade (A+ to F) and a numeric score that can exceed 100. We cap the score at 100 for the average.
developer.mozilla.org/en-US/observatory
Google PageSpeed Insights (mobile performance)
Lighthouse performance measurement in mobile simulation: load time, Core Web Vitals metrics (LCP, INP, CLS). Score out of 100. We exclusively use mobile performance.
RoastMyUrl (SEO and GEO)
Citability audit by search engines and language models (ChatGPT, Claude, Perplexity, Gemini). Public score out of 100, readable on the service hall-of-fame page.
Average computation formula
For each indicator, we compute a simple arithmetic mean over the domains listed below. The Mozilla Observatory score is capped at 100 (public max is 140) so that the average stays on the same 0-100 scale as the other two.
average = sum(valid scores) / count(valid scores)Domains included in the average
Aggregated scores cover all tools presented on this page as well as the koperateur.com site itself, to measure the ecosystem as a whole.
| Domain | Role | Observatory | PageSpeed | RoastMyUrl |
|---|---|---|---|---|
| 0bla.com | Tool | A+ (140) | 75 | 100 |
| itylos.com | Tool | A+ (140) | 92 | 100 |
| roastmyurl.com | Tool | B (75) | 94 | --- |
| koperateur.com | Institutional site | A+ (140) | 100 | 100 |
Refresh frequency
Scores are automatically refreshed every six hours by a scheduled server-side task. No call is made from the visitor browser, ensuring both performance and privacy.
Privacy and security
Requests to third-party services are made exclusively from our servers, on public API endpoints. No visitor data is transmitted. The Google PageSpeed API key is stored encrypted on the server side, accessible only to the fetch process.