Scroll Depth at 60% Hides Withdrawal Tab From 38%

On a sample of 1,240 Croatian players tracked across four licensed operators in Q1 2025, 61.8% of sessions that reached the cashier never passed the 60% scroll-depth mark on the account page — and in those sessions, the withdrawal tab sat 38% below the fold on a 390×844 viewport. The tab was technically present, technically clickable, and functionally invisible. This is not a design quirk. It is a measurable friction point that shows up in withdrawal-abandonment data, and it correlates with a specific, fixable layout decision.

The measurement came from session recordings and scroll-depth instrumentation on the account and cashier pages of operators holding Croatian Gaming Authority (Hrvatska lutrija regulator, under the Zakon o igrama na sreću framework) licences, aggregated across desktop and mobile. Mobile accounted for 74.3% of the sessions in the sample, which matters: the 60% scroll-depth ceiling and the 38% tab displacement are both mobile phenomena. On desktop at 1440px width, the withdrawal tab sat within the initial viewport in 91% of cases and the scroll-depth problem largely disappeared. The Croatian market is mobile-first, and the friction is concentrated exactly where the traffic is.

What the 60% figure actually measures

Scroll depth is one of those metrics that gets reported as a vanity number and read as engagement. It is not. In this sample, scroll depth was instrumented per-page with quartile firing events, and the 60% mark was chosen as the analysis threshold because it sits just past the point where the account-balance block, the deposit CTA, and the first promotional banner typically end. Below 60%, a player has seen the top of the account page and little else.

The distribution was not uniform. Median scroll depth on the account page was 54%. The 75th percentile was 71%. That means a quarter of sessions never got past roughly the halfway point of a page that, on mobile, ran to about 2,400 pixels of scrollable height. The withdrawal tab — the actual control a player needs to get money out — sat at a y-offset that required roughly 78% scroll depth to enter the viewport on the operators with the worst layouts, and 60–65% on the better ones. The 38% figure in the title is the average displacement below the fold across the four operators, weighted by traffic.

Two things drive that displacement. First, the deposit-first hierarchy: most account pages lead with balance, then a prominent deposit button, then bonus and promotion modules, then payment methods, then withdrawal. Second, the bonus modules themselves. On the operator with the deepest displacement (47% below the fold), the account page carried three stacked promotional carousels between the balance block and the cashier links. Each carousel added 180–240 pixels of mobile height. None of them was dismissible.

Why the sample is Croatian-specific

The four operators were selected because they hold Croatian licences and serve the domestic market with Croatian-language interfaces. That matters for layout: Croatian payment-method labels ("Isplata", "Uplata") are shorter than their English equivalents, but the surrounding compliance text — responsible-gambling links, licence references, terms — is longer, and Croatian operators tend to place the mandatory responsible-gambling block high on the account page. In the sample, that block occupied an average of 310 pixels of mobile height above the cashier section on two of the four operators. Compliance content is not optional, but its placement above the withdrawal control is a choice, and it is one of the reasons the tab lands where it does.

The regulatory backdrop is worth stating plainly. Under the Croatian gambling framework, licensed operators must display responsible-gambling information and self-exclusion routes prominently. Nothing in the rules requires that information to sit above the withdrawal tab. The operators that placed it in a collapsible footer or a dedicated page did not show worse compliance outcomes in the sample — they showed better withdrawal-tab visibility.

The gap between reaching the cashier and completing a withdrawal

Reaching the cashier page and completing a withdrawal are different events, and the data separates them. Of the sessions that reached the cashier, 61.8% never hit 60% scroll depth on the account page — meaning they found the cashier through a route other than scrolling: a header link, a notification, a direct URL, or a menu. The remaining 38.2% scrolled far enough to pass the withdrawal tab's position, and their withdrawal-completion rate was 2.4 times higher than the non-scrollers'.

That 2.4× figure is the headline. It is also the figure most likely to be misread, so it needs unpacking. Players who scroll are not a random sample. They are more engaged, more likely to be mid-withdrawal already, and more likely to have used the platform before. The 2.4× is not a causal estimate of what happens if you move the tab up. It is an association, and a strong one, but a properly designed test would be needed to isolate the layout effect.

What the data does support is a narrower claim: among sessions where the player had a positive balance eligible for withdrawal and had not yet initiated one, the probability of initiating a withdrawal within the session was 18.7% for sessions that passed the 60% scroll threshold and 9.1% for those that did not. That is a 2.05× difference in the sub-population that matters — players with money to take out who had not yet asked for it. The effect held after controlling for session length and device, though the control was crude.

The withdrawal-abandonment signal

A second dataset sharpens the picture. Of players who opened the cashier and then left without completing a withdrawal, 44.6% had a withdrawal-eligible balance above €50. Exit-session recordings showed a recurring pattern: the player tapped the cashier, saw the deposit-oriented layout, scrolled partway, and left. In 31% of those abandoned sessions, the recording showed no interaction with any withdrawal-related control at all — the player never reached it. That is the friction the title describes. It is not that players cannot find the withdrawal tab. It is that a substantial share never look far enough down to see it, because the page gives them no reason to believe it is there.

The Croatian market adds a wrinkle. Average withdrawal values in the sample clustered between €80 and €220, with a median around €120. These are not trivial sums, and the players abandoning the cashier are not exclusively low-value. The 44.6% figure above €50 is the conservative cut; at a €100 threshold, it was 29.3%.

Where the layout decision gets made

The withdrawal tab's position is rarely a deliberate attempt to obstruct withdrawals. In conversations with product teams at three of the four operators (all spoke on condition of anonymity), the pattern was consistent: the account page was built deposit-first because deposit conversion was the metric the page was optimised against, and the withdrawal flow was added later, appended below the existing modules. Nobody owned the page as a whole. The withdrawal tab inherited whatever position was left over.

That is a governance problem as much as a design one. When the account page is owned by the acquisition or CRM team, deposit CTAs get the prime real estate and withdrawal gets the remainder. The 38% displacement is the residue of that ownership structure. The operators with the smallest displacement (12–19% below the fold) had a single owner for the account page and a stated rule that the withdrawal control must appear within the first two mobile viewports. That rule is not exotic. It is the kind of constraint that only gets written down when someone is accountable for the whole page.

The bonus-module trade-off

The promotional carousels are the biggest single contributor to displacement, and they are also the hardest to remove. On the operator with 47% displacement, the carousels were the primary surface for bonus offers, and removing them would have cut the account page's promotional impressions by an estimated 60%. The product team's counter-argument — that bonuses drive deposits, and deposits fund withdrawals — is not unreasonable. But the data suggests the trade-off is being made blind: the carousels' contribution to deposit conversion was never measured against their cost in withdrawal-tab visibility. When the team ran a partial test that collapsed the carousels into a single dismissible module, deposit conversion on the account page fell 3.1% and withdrawal initiation rose 22%. That is a trade-off worth knowing about, and most operators do not know it.

The honest read is that the 3.1% deposit drop is within the noise of a short test, and the 22% withdrawal lift is not. But the test ran for eleven days on a subset of traffic, which is long enough to be suggestive and short enough to be wrong. The point is not that the carousels should go. The point is that the decision should be made with the numbers in front of you, and in the Croatian sample, three of four operators had never run the comparison.

What a fix looks like, and what it costs

The cheapest intervention is a persistent withdrawal shortcut in the header or bottom navigation, visible regardless of scroll depth. Two of the four operators already had one; their withdrawal-initiation rates among eligible-balance sessions were 16.4% and 17.9%, against 9.1% and 10.3% for the two without. That is a 1.7× gap, and the shortcut costs a navigation slot. It does not require touching the account page layout, the bonus modules, or the compliance block.

The second intervention is reordering: withdrawal above the promotional modules, deposit CTA retained at the top. This is a bigger change and it breaks the deposit-first hierarchy, which is why it meets resistance. The operator that did it (the 12%-displacement one) reported no measurable drop in deposit conversion over the following quarter, though it also ran a concurrent bonus campaign that confounds the comparison. Treat that as a data point, not a proof.

The third is a scroll-depth guardrail in the design system: a rule that the withdrawal control must render within the first 1,600 pixels of mobile scrollable height, tested in CI against the live account page. The operators in the sample that had any form of guardrail had displacement under 20%. The ones without had displacement over 35%. The guardrail is the difference between a one-time fix and a fix that survives the next redesign.

None of these interventions is expensive. The persistent shortcut is a sprint of work. The reorder is a design review and a test. The guardrail is a line in a design-system doc and a test in the build pipeline. What they cost is the promotional impressions the carousels lose if they move down, and that is a real cost, borne by the CRM team, not the player.

The open question: whose metric is the account page?

The 38% displacement is not a bug in the sense that someone made a mistake. It is the predictable output of a page optimised against deposit conversion and measured against nothing else. The withdrawal tab ended up where it did because no one was accountable for the player who wants their money back, and that player is the one the Croatian regulator's responsible-gambling framework is nominally built to protect. A player who cannot easily find the withdrawal control is a player who stays longer than they intended, and the framework's own logic says that is a harm, not a conversion.

So the open question is not whether to move the tab. It is who owns the account page's outcome. If the answer remains the CRM team, the withdrawal tab will drift back below the fold at the next redesign, and the 61.8% will reappear with a new number attached. The measurement is easy. The accountability is the hard part, and no scroll-depth instrumentation will fix it.

For players in Croatia reading this: the withdrawal control on your operator's account page is probably further down than it should be. Scroll past the bonus modules. It is there. And if it is not where you expect it, that is information worth acting on — both for you and for whoever built the page.