DraftKings Casino review:
9.6 megabytes before the first spin

DraftKings maintains both routes in its casino states: a dedicated DraftKings Casino app, and a casino section inside the main DraftKings app. On a phone the dedicated app is the better product: the lobby is the home screen, not a destination you navigate to past betting markets. The catalog covers slots, virtual table games and live dealer, plus a set of in-house exclusive titles DraftKings builds itself, which most US competitors don't attempt. Live dealer coverage depends on each state's rules, so judge the lobby you actually get, not a national feature list.

The small-screen lobby is dense. Category rails stack vertically, thumbnails are large, and search sits one tap away, so finding a specific slot is quick once the page is up. Getting the page up is the cost: at 9.6MB of first-load transfer, the lobby assumes a connection that can absorb it. On hotel Wi-Fi or a weak LTE cell you will feel those megabytes before you see a single reel.

Our three throttled-4G runs put the browser lobby at 5.9 seconds to load, carrying 9.6MB. For a real-money lobby that is acceptable rather than good: the fastest US operator we timed came in under a second, and 9.6MB is the second-heaviest first load in our US table after FanDuel's 14.2MB. On modern hardware with solid coverage you won't notice; on a throttled or congested connection you will.

The native app is a 195.4MB download requiring iOS 16.2 or newer, the second-strictest floor in our US index after Caesars' 17.0, which quietly excludes anyone on an iPhone that stopped receiving iOS updates a few years back. Store ratings are strong: 4.7 on iOS and a rounded 5.0 on Google Play at our last pull. We report store averages as player sentiment, not as our own finding, and a 5.0 should be read as rounding rather than perfection.

The cashier carries the usual US rails: debit cards, ACH via online banking, PayPal, and Play+ prepaid. Credit cards are commonly declined by issuing banks that code gambling transactions, so debit and ACH remain the rails we'd plan around. We don't quote minimum deposits, fees or payout clocks: they vary by state and by method, and a stale number is worse than none.

One structural point that catches multi-state players: each state license is a separate wallet. A balance deposited in New Jersey is not spendable in Michigan, even though the app and login are the same. Identity verification (name, address, date of birth, last four of your SSN) happens at signup, and the first withdrawal is where incomplete verification stalls, so finish the document checks before you need money out.

We loaded casino.draftkings.com three times in headless Chromium on a throttled-4G profile from our measurement node and report the result alongside app-store metadata pulled fresh at each site rebuild. DraftKings did not block our node, so the 5.9-second and 9.6MB figures are direct observations, current as of the snapshot date on this page. What we did not do: log in, deposit, or measure the native app's own screens; store size and minimum OS come from the listings.