Methodology
What the badge actually means
A trust mark is only worth what stands behind it. This is the full method, including the checks we do not perform, so nobody has to guess. A report only ever contains the checks that actually ran on your site, and it names them — if a check is not named in your report, it did not run.
The four checks, and what each one stops short of claiming
Revenue Leak ScanRequests that fail while your homepage loads.
- ✓Every failing request recorded with its full URL, not just a count
- ✓Refusals aimed at our crawler separated out and never reported as your breakage
- ✓Failures on your own domain separated from your platform vendor's
- ✓Each one reproducible by you with a single curl command
Dead Weight FinderThe single largest file your homepage loads.
- ✓Named with its URL, its size and its type — one file, not a score
- ✓Page totals are measured but never quoted: on a site that streams video the total overstated the real transfer by 3.4x
- ✓Compared against a measured market median of 1.9 MB across 1,222 sites
- ✓Confirmable with one curl command against the file itself
Time-to-Play TestSeconds to a usable Register button on a slow mobile connection.
- ✓Run on a phone-sized viewport with the connection throttled to a named profile
- ✓The button is never clicked — we measure readiness, not create accounts
- ✓The throttle settings are stated so you can repeat the measurement
- ✓If our detector finds no button we report that as unmeasured, never as missing
Licence MatchYour licence number, looked up in the regulator's own register.
- ✓The number is read from your own page, not from a third-party list
- ✓Checked against the regulator's register, including the approved-domain list
- ✓No public record is reported as unconfirmed — never as unlicensed
- ✓Certificates expire and get reissued, and we say so rather than implying fault
What we do not verify
Published deliberately. A seal that implies more than it checks is worse than no seal, and this is the line we hold when something goes wrong at an operator carrying our badge.
RTP and whether individual results are fair
Proving this needs millions of spins or direct data from the provider. No verification service on this market genuinely does it, and we will not imply that we do.
Where the games actually come from
We tried. Operators serve game content through their own domains and unbranded CDNs, so the studio behind a game cannot be established from outside. We record which studios a site names and the date it named them. We do not verify the claim.
Anything behind a login
Every check runs as a first-time visitor with no account. Deposits, withdrawals, KYC and account settings are invisible to us, so we say nothing about them.
Whether an operator can pay a large win
Solvency is not visible from outside, and we do not test withdrawals. Nothing we publish is a statement about whether a jackpot gets paid.
That an operator will never treat a player badly
The badge reports four measurements taken on one day from outside the site. It is a record of what we measured, not a character reference.
Verified-at-Send
Every finding is re-run against the live site on the day it is sent or published, and anything that no longer reproduces is removed rather than left in. Findings go stale — one site fixed an issue between our sweep and our checking it a day later. The verification page always shows the date it was last run, so nobody has to guess how old the result is.
How a badge gets suspended
If a complaint arrives or the crawler sees something abnormal, the operator gets 48 hours to respond privately before anything changes publicly — that protects against false reports from competitors. If the problem is real, the badge comes down and the verification page is updated with the facts. We do not remove pages for payment, and there is no fee that makes a finding disappear.