FanDuel Casino review:
the 14-megabyte lobby problem

The catalog itself is the standard full house for a major US operator: a deep slots shelf, virtual blackjack, roulette and other table games, and a live dealer section. FanDuel maintains a dedicated casino app in its licensed states in addition to the casino section of its main app, and as with DraftKings we consider the standalone app the right choice on a phone: no sportsbook chrome between you and the lobby.

Layout on a small screen is conventional and workable: horizontal category rails, big thumbnails, search reachable in one tap. We don't publish game counts we haven't crawled, and the shelf differs by state; Connecticut's lobby is legally distinct from New Jersey's even inside the same app. What we can say from our runs is that the lobby's weight comes largely from imagery, so scrolling deep into the shelf keeps pulling data long after first paint. A search-first habit helps: typing three letters costs less data than scrolling three rails of artwork.

The headline numbers deserve context. 13.16 seconds and 14.2MB is what a mid-tier phone on congested mobile data experiences, because that is what our throttled-4G profile imitates. It is nearly ten times BetRivers' 0.68-second first load and more than double DraftKings' 5.9 seconds, measured the same way on the same node in the same rebuild. This is a heavyweight lobby, and no store rating changes that.

The native apps tell a friendlier story. The iOS download is 203.3MB with a minimum of iOS 15.0, a more forgiving floor than DraftKings' 16.2 or Caesars' 17.0, so older iPhones stay in the game longer. And the 4.8 App Store average is the best iOS score in our US set, which suggests the app experience on capable hardware lands better than our worst-case browser timing implies. Both things are true at once: players like it, and it is heavy.

FanDuel's cashier runs the rails you'd expect from a US state-licensed operator: debit cards, ACH through online banking, PayPal, and Play+ prepaid. As everywhere in this market, credit cards exist on paper but die at the issuing bank often enough that we don't count them as a plan. We print no minimum deposits, no fee tables and no payout clocks, because those figures move by state and method and we can't re-verify them at every rebuild.

The structural rules of the US market apply in full: five separate state wallets behind one login, physical presence inside the state required for every wager, and identity verification against your SSN records before the first withdrawal clears. Do the document step at signup rather than at cash-out; that is where every US operator's queue actually forms.

We loaded casino.fanduel.com three times in headless Chromium on a throttled-4G profile from our measurement node; FanDuel served our node the real lobby rather than a geo-shell, so the 13.16-second and 14.2MB figures are direct observations, not estimates. App-store metadata (ratings, download size, minimum OS) was pulled at the same rebuild and carries the snapshot date shown on this page. We did not log in or measure post-login screens.