A customer taps Send. The page sits still. It’s easy to blame the button, but the failure could be in the layout, the request, or the feedback the visitor gets after submitting. Here’s a short way to tell those apart.
1. Reproduce the tap on a phone
Open the affected page on a real phone and test it in the same state the customer described. If the button works until a cookie banner or sticky footer appears, check whether that element covers the tap area. For a form, repeat the test with valid and invalid input. If validation blocks submission, the visitor should be able to see which field needs attention.
2. Follow the request
Open the Network panel in your browser’s developer tools, clear the list, then tap the button once. If you expected a request and none appears, check whether validation or a JavaScript error stopped the action. If a request appears, inspect its status and response before changing the front end. Use test data on a staging site when the action sends a real message or creates an order.
3. Verify what the visitor sees
Try both a successful submission and a failed one. A successful request should produce a visible confirmation. A failed request should explain what the visitor can do next and preserve their input where possible. Check that repeated taps don’t create duplicate submissions.
Before closing the issue, repeat the original steps on the phone that exposed it. Write down what was broken and what you verified. That gives the next person a concrete test they can repeat.
Source: Chrome for Developers, Network panel.