Every UiKitDataInputTests journey takes 10-25 s where the other kit pages take 3-5 s #1240

Measured on full run 37909582434 (2026-10-09), job browser E2E 3/4:

• UiKitDataInputTests: 56 journeys, 808 s — 10 s at the least (The_native_select_reports_its_pick, Pressing_a_tick_moves_the_thumb_to_it), 14 s on average.
• UiKitDataGridTests, same job, same fixture, the same OpenAsync (docs → sidebar link → main h1): 9 journeys at 3 s each.
• The other shards: 63 journeys in 5.7 min and 123 in 6.6 min, so 3-5 s each.

So something about the Data input page costs about ten seconds per journey before the journey's own work. Not yet looked into: whether it is the page's first render in WASM (26 example groups, calendars and pickers among them), the navigation to it, or a wait in the tests. If it is the render, a reader of rask.sh/docs waits for it too.

Why it matters beyond the suite: that class was the whole run's time (full ≈ 20 min), and a nightly package waits for the whole run. The class is now dealt over two shards, which hides the cost and does not remove it.

What to find out: where the ten seconds go (a Playwright trace of one journey says), and then either the page or the tests.