Building a 30-Game Arcade Collection Using PlayKovo Catalog

You can build a good 30-game arcade collection from PlayKovo's catalog by choosing games that are declared for phones, that started in a real browser on both desktop and phone profiles, that are light enough and that cover several genres. This guide shows the rules we used, the 30 games they selected, the groups they fall into and the games we left out, so you can copy the method with your own rules.
Measured on 16 October 2026 with Chrome 155, from a feed snapshot of 90 games. We opened every game, pressed play and recorded the downloaded bytes and the console errors. We did not play the games through, so the quality of play is for you to judge.
Step 1: Write the rules before you pick
Rules stop favorites from crowding out balance. Ours:
- Declared for desktop and mobile in the feed.
- A canvas appeared after pressing play on both desktop and a Pixel 7 phone profile.
- No horizontal overflow on the phone profile.
- Game files under 500 KB in our measurement.
- At most six games per group, so no genre takes over.
- No violent horror and no dress-up, to keep the set suitable for a general audience. Change this to fit your site.
- One or two games should be playable without any explanation.
Applying rules 1 to 3 left 66 candidates out of 90. Rule 4 removed the heaviest, such as two .io games at several megabytes and a runner at over 10 MB. Rule 6 removed the horror and dress-up titles. Rule 5 shaped the groups below.
Step 2: The 30
| Group | Game | Layout | Game files (KB) | Console errors on desktop |
|---|---|---|---|---|
| .io arena (6) | Sumo.io - Push Them Off | Landscape | 40 | 1 |
| .io arena (6) | Wriggle.io | Landscape | 46 | 0 |
| .io arena (6) | Splat.io | Landscape | 43 | 0 |
| .io arena (6) | Bubble.io | Landscape | 44 | 0 |
| .io arena (6) | Hop.io | Landscape | 44 | 0 |
| .io arena (6) | Land Grab 3D | Landscape | 38 | 0 |
| Arcade (5) | Blade Spin | Either | 33 | 0 |
| Arcade (5) | Lane Hopper | Either | 206 | 0 |
| Arcade (5) | Zigzag | Portrait | 210 | 0 |
| Arcade (5) | Stack Tower | Portrait | 205 | 0 |
| Arcade (5) | Digger | Portrait | 21 | 1 |
| Hypercasual (5) | Orbit Keeper | Portrait | 57 | 0 |
| Hypercasual (5) | Helix Jump | Portrait | 222 | 0 |
| Hypercasual (5) | Color Switch 3D | Portrait | 221 | 0 |
| Hypercasual (5) | Giant Rush | Portrait | 297 | 0 |
| Hypercasual (5) | Crowd Rush 3D | Portrait | 300 | 0 |
| Puzzle (5) | Water Sort Puzzle | Portrait | 78 | 0 |
| Puzzle (5) | Arrow Escape: Tap Away Arrows Puzzle | Portrait | 74 | 0 |
| Puzzle (5) | Screw Pop | Portrait | 51 | 0 |
| Puzzle (5) | Arrow Blocks: Tap Away Block | Portrait | 84 | 0 |
| Puzzle (5) | Hexa Stack 3D | Portrait | 254 | 0 |
| Action and adventure (4) | Stolen Sword | Portrait | 22 | 1 |
| Action and adventure (4) | Rainbow Run | Landscape | 16 | 1 |
| Action and adventure (4) | Rocket Dash | Either | 215 | 0 |
| Action and adventure (4) | Sky Isles | Landscape | 153 | 1 |
| Strategy, merge and idle (3) | State Clash – Conquer the Map | Landscape | 137 | 0 |
| Strategy, merge and idle (3) | Wingworm: Merge Cubes | Landscape | 216 | 0 |
| Strategy, merge and idle (3) | Cosmic Clicker – Idle Tycoon | Portrait | 79 | 0 |
| Racing and sports (2) | Party Dash: Knockout Race | Landscape | 218 | 0 |
| Racing and sports (2) | Tideline | Landscape | 202 | 1 |
Numbers from the table: 30 games, median game files 82 KB, 3.8 MB of game files in total. Fifteen are portrait, twelve landscape and three work in either orientation. Six of the thirty logged at least one console error on desktop.
Step 3: Why these groups
| Group | Why it is in | What it does for the collection |
|---|---|---|
| .io arena (6) | Most numerous genre in the feed, very light files | Gives the site "active" games for desktop and landscape phones |
| Arcade (5) | One-tap timing games | Short sessions, easy to explain |
| Hypercasual (5) | One input, portrait | The best fit for a phone held upright |
| Puzzle (5) | Tap or drag to solve | Calm, appeals to a wide audience |
| Action and adventure (4) | Runners and dash games | Variety in pacing |
| Strategy, merge and idle (3) | Different pace and depth | For visitors who like to think |
| Racing and sports (2) | Racing and fishing | Fill genres the catalog has few of |
Step 4: What we left out, and why
| Left out | Reason |
|---|---|
| Desktop-only games (17 in the snapshot) | The collection targets phones as well as desktops |
| The seven games with no canvas found on the phone profile (for example Minesweeper Kovo, Cream 2048, Jewelsback) | Our check could not confirm they started; they may be fine, but test them by hand before adding |
| The heaviest games (games with files above 4 MB) | Rule 4 |
| Two horror games, two dress-up games | Rule 6 |
| Very similar games | If two games feel the same, one stays. Several .io games have near-identical mechanics |
Notice that excluding the games with no canvas is a rule about our measurement, not a judgment about the games. If you test them and they work, add them.
Step 5: Shape the pages
A 30-game set should not be thirty equal pages. We would organize it like this:
- One hub page with seven group headings, each with a short introduction and the games in it.
- Three or four collection pages for needs that cut across groups ("quick one-tap games", "games for a short break", "games for landscape phones").
- A page per game only for the ten you can write something real about. The rest appear on the hub with a name, a device badge and a play control.
Our guide on categories and tags explains why one page per game is not automatic, and collection pages shows how to write them.
Step 6: Load it without wrecking speed
Thirty frames on one page would be heavy. Use posters that start on click, so the hub page costs only its own HTML and images. Our experiment: four frames loaded immediately cost 1.56 MB; click-to-play posters cost zero until clicked. Details are in our page-weight guide.
Step 7: Check before you publish
- Play each game for two minutes on a real phone.
- Confirm that portrait games use a portrait frame (9:16, up to 420 px wide) and landscape games use 16:9.
- Run the monitoring script on the list.
- Read the partner terms: credits visible, ads untouched, removal within three business days of a request.
Step 8: Keep it healthy
| How often | What |
|---|---|
| Daily | Monitor runs |
| Weekly | Review play clicks and one new feed game |
| Monthly | Replace the two least-started games |
| Quarterly | Re-run the selection rules on the current feed, because the catalog grows (90 games on 13 October, 92 on 16 October) |
Three of the thirty, to try
A hypercasual game, an arena game and a puzzle game:
Try it live · PlayKovo catalog
DesktopsupportedMobilesupportedTap to flip your dot around the circle, dodge the spinning purple arc, and sharpen your reflexes. Each tap earns a point. How long can you survive it?
Try it live · PlayKovo catalog
DesktopsupportedMobilesupportedShove your rivals off a shrinking sumo platform in this fast and funny .io brawler. Bump, dash and outsmart the crowd to be the last fighter standing, then spend your coins on hats and…
Try it live · PlayKovo catalog
DesktopsupportedMobilesupportedPour colorful liquids between the tubes until each one contains only a single color. Think ahead, choose every move carefully, and solve satisfying sorting puzzles that become more…
What to change for your audience
- A children's site: drop the brawlers and review every game's description.
- A workplace site: favor quiet, one-input games.
- A gaming site: raise the cap per group and add the desktop-only games.
The method stays the same: rules first, measure, choose, test, maintain.
Related Posts

We Compared 20 Embeddable Games for Small Websites
We opened 20 games from PlayKovo's embed catalog in real Chrome, on desktop and with a phone profile, pressed play and recorded what loaded, what failed and how heavy each was. Here are the results, what the numbers do and do not tell you, and which games we would start with.

Should You Host HTML5 Games Yourself or Use a Game Distributor?
For most websites the answer is a distributor, and bandwidth is not the reason. Here is a neutral comparison of cost, updates, licensing, control and maintenance, with measured game sizes behind the cost arithmetic.

How to Handle Fullscreen Problems in Embedded Browser Games
Fullscreen fails for three reasons: the iframe lacks permission, the browser does not support it for that element, or the request was not a user action. We tested each in Chrome 155 and built a CSS fallback for browsers with no Fullscreen API.