A slow-loading treatment page that drops users
An A/B test intended a 50/50 split, but treatment ended up with 6% fewer users than control, and the SRM check fails decisively. Investigation shows the treatment page loads a heavier script and takes about a second longer to become interactive; some users on slow connections leave before the page (and their assignment) is logged. Treatment shows a +5% lift on conversion.
Explain how this specific SRM biases the measured lift, and what the team should do.
Your answer
Solving needs a free account
Answers, streaks and solutions unlock when you are signed in. Reading the question and the hint stays free.
Discussion
Sign in to join the discussion · reading is open to everyone
💡 Discussion rules
- No full solutions here. Hints and approaches only.
- Complexity, edge cases and intuition are the point.
- Interview experiences are welcome. Respect your NDAs.
Loading discussion…
Learn the concepts
The theory behind this question.
Related questions
The best of fifty backtests looks amazingYour 50/50 split came out 50.2/49.3, is that a problem?Is your 50/50 split actually 50/50? A sample-ratio checkA 24,600 vs 25,400 split on 50,000 users, real or noise?When a 5,050 vs 4,950 split is perfectly fine
All questions →