PERFORMANCE TEST · ADD-ON — optional module

Every game on your site —
ready to play, and ready to spin.

We measure both: time to playable and real spin duration — exactly as players see it.

24/7
Continuously watching
40+
Countries measured
Load + spin
Both halves timed
0
Integration needed
performance pulse reel · preview
PLACEHOLDER
Performance reel — coming soon
Real loads, real spins, frame-timed by computer vision. In production.
measured from
🇵🇹🇩🇪🇬🇧🇧🇷 🇳🇱🇪🇸🇨🇦🇸🇪 +32
what the bot does
  1. 01
    start the stopwatch
    t=0 · navigation begins
  2. 02
    time the load
    stop when the spin button responds
  3. 03
    watch the spin
    frame-by-frame · reels start → reels stop
and measures
  • time-to-playable
    how long until a player can click
  • spin duration
    visually measured, not clock-faked
  • timeouts & drift
    loading failures · slow-session spikes
Why you need this

Spin time is a revenue lever — and a risk one too.

Too slow, you bleed GGR. Too fast, you may fall below a market's legal minimum. And the biggest regressions don't arrive at launch — they creep in weeks later, quietly, from a config you didn't ship.

01
Too slow = bored players

A 9-second spin is a player walking away.

Long spins kill session engagement — players get bored and leave. Even the ones who stay spin fewer rounds per hour, so revenue comes in slower too. Spin duration is a GGR lever, not an animation detail.

02
Small configs, huge blast radius

We've seen 2s spins turn into 20s overnight.

One provider misconfig, one asset-pipeline tweak, one CDN route change — and a cash-cow title is suddenly unplayable in half your markets. By the time support raises a ticket, the weekend is gone. Continuous monitoring catches it within hours.

03
Bugs age into production

Some failures only appear weeks after go-live.

Cache warms up wrong. A region's edge node drifts. A third-party SDK rolls a silent update. Release-day smoke tests pass — then four weeks later the game stops loading in Brazil. We keep watching, so you don't have to trust that day-one green dashboard forever.

04
Too fast can break the rules

Below a legal minimum, spin time becomes a compliance issue.

Some regulated markets — Germany being the well-known example — mandate a minimum spin duration. A provider update that shaves a few hundred ms off the reels stops being a UX detail and becomes a license problem. We catch it the moment it ships.

What the Performance Test does

Load and spin time — measured the way players see it.

Plenty of tools can ping a network request. We do something else: we watch the screen. Performance Pulse measures how long each game takes to load and how long its reels actually spin — frame by frame, via computer vision. That's the half of performance your APM, your CDN dashboard and your aggregator's status page cannot see.

real PlayPatrol performance findings · reel
PLACEHOLDER
Real findings — coming soon
Actual slow loads and stuck spins PlayPatrol caught in production — frame-stamped by vision. In edit.
Real gameplay, not synthetic checks
We open games on your site and measure real player experience — click by click.
True "time-to-play" detection
We stop timing when the game is actually interactive — not when a script says so.
Spin timing on screen
We track reels from start to settle — per game, per GEO.
Failures and timeouts included
Stuck loads, broken spins, unfinished sessions — if players hit it, we catch it.
Detects slowdowns, not just outages
Latency spikes, regional issues, performance drift over time.
Proof included
Video + request waterfall — ready to share with providers.
How it works

Three steps. No SDK, no code, no dev time.

Point Performance Pulse at your casino. We handle devices, geos, scheduling and SLA thresholds from there.

01

Select games & set budgets

Pick the titles you want on patrol — and the two budgets that matter: time-to-playable (e.g. 3s p95 on mobile) and spin duration (e.g. 2–4s per spin).

  • Any HTML5 / Unity / native game
  • Your operator URL, no SDK
  • Per-game or global SLAs
02

PlayPatrol watches, continuously

We launch real sessions on real devices from real countries, every 1–3 days. The bot loads the game, presses SPIN, and computer vision frame-times both the load and the reel animation.

  • Parallel, no queues
  • Technical logs and visual evidence
  • Extra runs after releases
03

Get proof a player would recognise

Breaches arrive with the waterfall, the GEO, the device, the exact stage that ate the load budget — and the video of the spin that stalled. Forward it to the provider responsible.

  • Webhook / Slack / Teams / email
  • p50 / p95 / p99 · load AND spin
  • Jira / Linear export
Coverage · your way

Focus on what matters — your games, your priorities, your markets.

Cash cows. Newest releases. Titles you're promoting this month. Your entire portfolio on rotation. Any combination works — and every title is measured on load AND spin, from every GEO you care about. Two popular shapes shown below, or any custom mix you need.

Or mix any way you like
pick any / pick all / adjust anytime
Cash-cow games
Your top GGR earners
Newest releases
Just added to your site
Currently promoted
In campaigns & tournaments
Entire portfolio
Sampled on rotation
Any custom mix
Build your own list
…measured from anywhere your players are
🇬🇧🇩🇪🇫🇷🇪🇸🇮🇹🇳🇱🇵🇹🇸🇪🇦🇹🇨🇭🇧🇪🇨🇦🇺🇸🇧🇷🇦🇷🇨🇱🇲🇽🇯🇵🇰🇷🇮🇳🇹🇭🇿🇦🇳🇿🇮🇪🇵🇱🇻🇳🇺🇾🇨🇴🇵🇪🇷🇴🇹🇷🇬🇷🇩🇰🇫🇮 + any GEO on demand
Latency is local. A game that's 2s in Frankfurt can be 7s in São Paulo — we time it from both.
What you get back

A timeline a player would recognise.

Two budgets, two verdicts, one report. Every breach ships with timing, video, vision stamps and a repro path — proof you can forward to the responsible provider.

Neon Reels 9000 · Casino C · Brazil (BR)

incident PRF-2214 · detected 2026-04-18 02:14 UTC
● SPIN DURATION BREACH
time-to-playable
4.2s vs 3.0s
+1.2s over · within tolerance
spin duration CV-measured
7.8s vs 4.0s
+3.8s over · reels would not stop
Phase 1 Load — technical timing
Phase 2 · CV Spin — measured by computer vision
Game provider
NeonReels Studio
Your casino
casino-c.br
Device
Galaxy S22 · Chrome 124 · Android 14
GEO / egress
São Paulo, BR · 200.144.19.7
Load verdict
within budget · ok
Spin verdict
CV detected reels still spinning at 7.8s · high
Root cause
result-frame frozen — stop animation never fired
Repro
pp reproduce PRF-2214 --device=s22 --geo=br
Attachments
video.mp4 · har.json · frames/*.png · vision.json
Put it on patrol

Tell us your site. We'll ship a pilot.

Three fields is all it takes. Pilot live within 7 working days — no SDK, no integration, no contract until you've seen the first load-and-spin report.

Ready to see it in action?

Catch the slow seconds a player can see — before they churn on them.

A 20-minute demo on your real casino. No slides. Just your games — loaded, spun, frame-timed on our devices.