Review Methodology

Example walkthrough

A worked example makes the method clearer than a weights table on its own. Imagine a review of the welcome bonus.

The editor opens an account with Philippine documents, deposits 2,000 PHP via GCash, and claims the welcome offer at the stated match percentage. The bonus credit is recorded against the deposit, screenshots are taken, and the wagering requirement is written down in the units it actually appears in on the cashier — a figure of "35x bonus" is very different from "35x deposit plus bonus".

The editor then plays the bonus balance on the slot categories permitted by the terms, tracking the wagering counter at regular intervals until it is cleared, paused by a terms-violation, or exhausted by losses. If the wagering is cleared, a withdrawal is requested through the method we deposited with, and the time to receipt is recorded.

The outcome — bonus value in real pesos, achievable or not, withdrawn or not — feeds the bonus score. The experience of claiming it, the clarity of the terms page, and any friction along the way feed the UX and support scores separately. The final score is the weighted combination of each dimension, published with the date of the test and refreshed on the next cycle.

Weights table

The four dimensions below are weighted into the overall score. The percentages are not sacred — they reflect what we think matters to a Philippine player today — and they are reviewed each year.

Payments carries the largest weight because the moment an operator either does or does not pay is the moment that defines the entire relationship with a player. The bonus weight is substantial because terms that look generous on the landing page are often the ones that disappoint most when the wagering hits. Support is weighted lower than user experience because support is invoked only when experience fails — but a bad support score pulls the overall grade down hard.

Criteria

Each dimension is scored against a defined checklist rather than a general impression.

• Bonuses. Match percentage, maximum bonus amount in PHP, wagering requirement expressed in a common unit, game weighting, maximum bet while bonus is active, expiry window, max cashout, terms clarity.
• Payments. Methods available to Philippine players (GCash, Maya, bank transfer, card), minimum and maximum deposit and withdrawal per method, declared versus measured processing time, KYC friction, withdrawal pending period, fees if any.
• User experience. Page-load time on mobile over 4G, lobby filter quality, search accuracy, clarity of the cashier flow, friction of registration, mobile app presence and quality.
• Customer support. Channels available (live chat, email, phone), hours covered, language support for English-speaking Philippine players, first-response time measured in minutes, quality of answers to canned test questions about bonuses and payouts.
• Game catalogue. Count and quality of slot studios, live-dealer studios streaming into the Philippines, availability of sportsbook sections if any.

Scoring

Each criterion inside a dimension is scored from 0 to 10. A 10 means "we could not find anything to improve"; a 0 means "this is either missing or actively broken". The dimension score is the arithmetic mean of its criteria, and the overall score is the weighted mean of the dimension scores.

The overall score is published as a single number with one decimal place, from 1.0 to 10.0. We avoid half-point euphemisms ("8.5 out of 10 — recommended!"); a score below 6.0 is not a cautious recommendation, it is a warning.

How we test

Testing is done from Philippine IP space using devices that match the devices a typical reader uses — a mid-range Android handset, an iPhone that is two or three generations behind the current one, and a laptop on a residential broadband line. The editor opens a real account, completes KYC with genuine documents, and deposits with a Philippine payment method.

All figures are recorded with timestamps and a source — a cashier page screenshot, a chat log, a bank notification. When a figure cannot be sourced to a live artefact, it does not appear in the review.

Re review cycle

A review is not finished when it is published; it starts its maintenance cycle on the same day. Bonus pages are re-checked monthly. Payment method pages are re-checked whenever reader feedback suggests a change. The full dimension-by-dimension review is refreshed twice a year. Each page carries a visible "last reviewed" date so that readers know how fresh the figures are.