Our Game Review Methodology

Safety is non-negotiable. Before we evaluate anything else, every game must pass our security checks. Browser games run inside your browser's sandbox, but that does not mean all games are created equal when it comes to security practices.

What we check:

• ✓HTTPS enforcement — Every game must be served over a secure connection. Games served over plain HTTP are automatically rejected, as they expose players to man-in-the-middle attacks and data interception.
• ✓Third-party script audit — We review the external scripts and network requests each game makes. Games that load suspicious third-party scripts, attempt to set tracking cookies beyond standard analytics, or make unexpected outbound connections are flagged and removed.
• ✓Content safety scan — All games are evaluated for age-appropriate content. We maintain a family-friendly platform, which means games with graphic violence, explicit content, or predatory monetization (such as deceptive in-game purchases) are not accepted.
• ✓Iframe sandboxing — Games are embedded using strict iframe sandboxing attributes that prevent them from navigating the parent page, accessing local storage outside their origin, or running scripts that could affect the rest of the site.

Our site-wide security headers (HSTS with preload, X-Frame-Options, X-Content-Type-Options, and strict referrer policies) provide an additional layer of defense for every page and every game session.

Over 60% of our traffic comes from mobile devices. A game that only works well on desktop is a game that fails more than half our audience. Every game is tested for mobile compatibility across multiple dimensions.

Our mobile testing criteria:

• ✓Touch input support — Games must respond correctly to touch events, not just mouse clicks. We verify that tap, swipe, and multi-touch gestures work as expected on both iOS Safari and Android Chrome.
• ✓Viewport scaling — The game canvas must adapt to different screen sizes without cropping critical gameplay elements or requiring horizontal scrolling. We test across phone (375px), tablet (768px), and desktop (1280px+) breakpoints.
• ✓Orientation handling — Games should either support both portrait and landscape modes or clearly indicate their preferred orientation. Games that break or become unplayable when a device is rotated need to handle orientation changes gracefully.
• ✓Performance on mid-range devices — We do not test on flagship phones alone. Games must maintain a playable framerate (30fps minimum) on mid-range devices from the past two to three years. A game that only runs smoothly on the latest hardware excludes too many players.

Games that fail mobile testing but perform well on desktop are still considered for inclusion, but they are clearly flagged so players know to expect a desktop-optimized experience.

Browser games live or die by their load times. If a game takes more than a few seconds to become interactive, players leave. We set strict performance thresholds that every game must meet.

• ✓Initial load under 5 seconds — On a standard broadband connection, the game must reach an interactive state within 5 seconds. Games with excessively large asset bundles that push load times beyond this threshold are flagged.
• ✓No excessive memory usage — Games that consume more than 500MB of browser memory risk crashing tabs on lower-end devices. We monitor memory usage during gameplay and reject games that leak memory or allocate resources carelessly.
• ✓Stable framerate — Consistent performance matters more than peak performance. A game running at a steady 30fps is preferable to one that spikes between 60fps and 15fps. We evaluate framerate stability over sustained play sessions, not just the first 30 seconds.

A game can be safe, fast, and mobile-friendly and still not be worth playing. The final phase of our review evaluates the gameplay experience itself. This is the most subjective phase, but we apply consistent criteria to keep the bar high.

• ✓Clear mechanics — Players should understand how to play within the first 30 seconds, either through intuitive design or clear instructions. Games that drop players into confusing interfaces with no guidance are penalized.
• ✓Engagement loop — Good games have a satisfying core loop that makes players want to try one more time. We evaluate whether the game provides meaningful progression, escalating challenge, or replayability that goes beyond a single session.
• ✓Visual and audio polish — While we do not require AAA production values, games should have a cohesive visual style and audio that enhances rather than detracts from the experience. Placeholder assets, broken animations, or ear-splitting sound effects are signs of an unfinished product.
• ✓Bug-free core experience — We play-test each game for at least several minutes to catch game-breaking bugs: infinite loops, broken level transitions, unresponsive controls, or softlocks that force the player to refresh. Minor cosmetic issues are acceptable; broken gameplay is not.