Layout
- Eleven more targets than 5×5—a 44% increase
- Six rows reduce each cell's available width in the same container
6×6 Schulte Table
A 36-target task for examining how a longer sequence and denser cells change the interface beyond the 5×5 reference condition.
Your Time
0.00s
Next
1
Click 1
Task facts
- Number range
- 1–36
- Cells
- 36
- Ordered selections
- 36
Complete this grid
- 1
Select Start and wait for the shuffled grid.
- 2
Select 1 through 36 in ascending order.
- 3
Review completion time and incorrect selections together.
- 4
Repeat only with the same setup when you want a personal comparison.
What is specific to 6×6
A 36-target task for examining how a longer sequence and denser cells change the interface beyond the 5×5 reference condition.
Small-screen behavior
- Phone targets can become noticeably smaller even though the whole grid still fits
- Landscape may improve width but creates a different comparison condition
Mouse and touch
- The pointer crosses a denser field and the total sequence is longer than the fixed speed test
- Check that each target is comfortably tappable before timing a round
Readability
- The layout remains moderate on desktop but begins to expose device-dependent density
Printing
- Confirm margins and scaling rather than assuming a browser preview matches physical output
How to compare this size
- The 44% target-count increase alone prevents a like-for-like total-time comparison with 5×5
- Use a separate 6×6 history series
Choosing a neighboring size
Return to 5×5 for the site's fixed 25-target comparison condition.
Choose 7×7 when you want 49 targets—nearly twice the 5×5 count—and can keep the cells readable.
Your comparison context
These values come only from completed ascending rounds stored in this browser for this exact grid. Choose an input method to narrow the set.
No comparable attempts are stored yet. Complete several rounds with the same grid, device, input method, and rules before interpreting changes in your own history.
Device model, orientation, browser zoom, and display scale are not stored. Confirm those conditions yourself before treating two rows as like-for-like.
Continue with a known comparison context
Use the tracker for filters and medians, or read why total times from different conditions should stay separate.