To find buttons that do not work, you have to click them in a real browser and watch what happens, because most modern buttons are driven by JavaScript rather than a plain link a crawler can read. This free scan loads your page on desktop and at phone width, clicks the main call to action, follows navigation links, and records any JavaScript error or failed request along the way. A button that is visible but leads nowhere, or one covered by another element on a phone, shows up in the report with a screenshot.
What it checks
Main call to action
The primary button is found, checked for being visible above the fold, and clicked to confirm it leads somewhere instead of sitting there doing nothing.
Navigation links
Menu links are followed and their responses checked, so a menu item pointing at a deleted page or a server error is caught.
Covered and hidden buttons on mobile
Invisible overlays, cookie banners and chat bubbles often sit on top of a button at phone width. The phone screenshots are reviewed for exactly this.
The error behind the button
When a button fails because a script crashed, the console error and the file it came from are listed, which is usually what a developer needs to fix it.
Dead links on the page
Up to about thirty links on the page are requested, and any that return a 404, a server error or time out are listed.
How to read your results
- A button flagged as leading nowhere on phone only, but fine on desktop, almost always means something is covering it. Look at the phone screenshot around the button.
- A console error that appears as the page loads can break every button that depends on that script. Fix the first error first; later ones often disappear with it.
- Dead links are quick wins. Update or remove them before looking at anything subtle.
What an automated check can't tell you
- The scan clicks the main call to action and navigation, not every single button on a long page. A paid report covers more pages, and the manual test covers whole flows.
- It will not place an order or complete a payment, so a checkout button that fails at the final step needs the manual test.
- Buttons that only exist after logging in are out of reach.
Want to see a full report before you scan? Here's a real sample report.
Frequently asked questions
What is the difference between a broken link checker and a broken button checker?
A link checker reads the href address in each link and requests it. A button that opens a menu, submits a form or adds to a cart often has no address at all; it runs JavaScript. Only clicking it in a browser shows whether it works.
Why does my button work on desktop but not on my phone?
Usually something is on top of it at phone width: a cookie banner, a chat widget, a popup or an invisible element from the theme. Less often the button sits outside the screen because a section is wider than the phone.
How do I find buttons that do nothing myself?
Open the page in a private window with the browser console open, click each important button, and watch for red errors or nothing happening. Then repeat in Chrome’s device mode or on a real phone.
Rather have a QA engineer test it by hand?
An automated check covers what a visitor sees on load. For logged-in flows, checkout, or a launch that has to go right, I'll test the site by hand.
- Up to 10 key pages tested by hand, not a scan
- Every flow a customer uses: forms, sign-up, checkout, booking
- Real mobile and desktop browsers
- A written report in plain language, with screenshots
- A 15-minute call to walk you through it
- 10 years of professional QA experience
Tell me about your site and I'll reply personally, usually the same day.
No payment now. I'll confirm scope and price first.
Related fix guides
Other free tools: Free mobile-friendly test · Contact form tester · JavaScript error checker · Free website bug checker · AI website tester
Built by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.
Sources: WordPress.org support: button not clickable on mobile · MDN: Using the browser console