| Example walkthrough | A typical scoring run on Lula Bet looks like this. We open a fresh browser, go through the registration flow with FICA documents to the first deposit, note the time taken and any friction. We deposit a small amount via instant EFT, play through a few spins on a tracked slot, trigger a withdrawal, and clock the delay from request to funds hitting the bank. We then open the mobile build on both an Android device and an iOS browser and repeat the critical steps. Every observation goes into a shared sheet with timestamps; the final grade for each criterion is set from those timestamps, not from memory. |
| How we test | We test the operator the way a real South African player would. Testing happens on both a laptop and a phone, with the browser's cache cleared, so cached layouts do not hide a slow page. We register with real FICA documents, deposit real Rand, play real spins and request real withdrawals. We do not take screenshots from marketing material — every image we publish comes from one of these sessions. When the operator pushes a visible change (new header, new promo widget, new payment method), we repeat the relevant part of the test before updating the review. |
| Weights table | The final rating is a weighted average. Payment speed and reliability carry the most weight because that is where the operator wins or loses trust: slow or stuck payouts outrank any bonus. Bonus value is the second-heaviest criterion, with wagering fairness built into the calculation. Game and sportsbook variety come next, followed by mobile experience and finally the softer side — support quality, promotional cadence, loyalty programme. The exact split is published in the table on this page and updated whenever the market standard shifts. |
| Scoring | Each criterion is rated from 1 to 10. A 10 means best in class for South Africa — we would need to see a measurable advantage over at least five established competitors to award it. A 7–8 is solid, broadly in line with what the market offers today. A 4–5 is below average, usually because of a specific friction point. Anything below 4 is a serious issue and will be called out in plain terms on the review page, not softened into a vague remark. |
| Re-review cycle | The brand page is re-reviewed on a fixed schedule. Every three months we run a full pass — fresh deposit, fresh withdrawal, fresh mobile check — and update the rating on the review page accordingly. Between full reviews, if something visible changes (new app build, new promo structure, new payment method) we patch the relevant section without touching the overall score. The date at the top of each page shows when it was last touched. |
| Criteria | The criteria stay the same across every review on the site, so the pages can be compared like for like. They are: licensing and legal status, deposit methods and speed, withdrawal methods and speed, bonus value and fairness of wagering, slot and live casino catalogue, sportsbook coverage and odds, mobile experience on Android and iOS, quality and hours of player support, loyalty and VIP programme, and responsible gambling tools. Each one gets its own grade before the weights are applied. For each criterion we define in advance what a good, average and poor outcome looks like, so the grade is not just an impression. For withdrawals, for instance, a 10 is "full payout within four hours, no extra documents requested", a 7 is "paid within one working day after a quick verification check", and a 4 is "paid within three working days with repeated document requests". Having the yardstick written down keeps two editors scoring the same session the same way. When the market itself shifts — a new mandatory licence, a new default payment method, a new local responsible gambling obligation — we update the criteria list and republish the methodology. Any review that was scored under the previous version is marked as such on the review page itself until it is run through the new rubric. We would rather be transparent about a methodology change than quietly adjust historical scores. |