Tap Target Size Test
Measure interactive element bounds in a rendered mobile viewport.
Run the tap target size test
Rendered browser checkWhat tap target size test helps you do
Measure interactive element bounds in a rendered mobile viewport. Two small pagination links close together can cause wrong taps. Increase the clickable area or spacing while keeping the visible label clear.
Prepare a useful input
Example input: https://example.com/ Save the original input alongside the result so another person can reproduce the check and judge whether a proposed change addresses the same page or file.
Read the result before making changes
Geometry is a screening signal; overlapping layers, focus behavior and assistive technology need additional testing. Record the checked URL and observation time. Compare the evidence with the intended page behavior, then verify the affected page again after a change instead of assuming the issue is resolved.
Check spacing and behavior beyond the rectangle
A small visible icon can have a larger clickable button around it, while a large label can have only a tiny linked portion. Inspect the real interactive element bounds, not the artwork alone. Neighboring controls need enough separation to reduce accidental taps, especially in pagination, menus and close buttons. Review exceptions and context rather than treating every flagged rectangle as an identical violation. Test with a narrow viewport and check keyboard focus after changing padding or hit areas. Avoid increasing a target in a way that causes it to overlap a nearby control or obscure important content.
Verify the result and continue
After adjusting a control, test the center and edges of its clickable area. Check neighboring actions for accidental overlap and keep visible focus states intact. A larger hit area should help the intended action without making another button harder to use or changing the document reading order. Continue with the viewport meta tag checker or explore the performance tool cluster.
How this tool works
Measure interactive element bounds in a rendered mobile viewport. A real browser visits the public URL and records the relevant rendered or network evidence. Results represent the sampled visit and are not fabricated field metrics.
What the result does and does not establish
Geometry is a screening signal; overlapping layers, focus behavior and assistive technology need additional testing.
Use this check as part of a repeatable website review. Record what you found, make a specific change and run the same check again.
Browse all toolsContent and technical review workflow