Troubleshooting

Grant browser permission: Click the lock icon (🔒) in your address bar → find the relevant permission (Microphone / Camera) → set to Allow → reload page.

Hard refresh: Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to clear cache and reload fresh.

Try Incognito/Private mode: Extensions can block browser APIs. Open the tool in a Private window to isolate the issue.

Try Chrome or Edge: Both use the Chromium engine and have the most complete Web API support. Switch if you are on Firefox, Safari, or Brave.

Close competing apps: Zoom, Discord, Teams, OBS — these hold exclusive access to mic/camera. Close them fully before running any test.

iOS users — Safari only: Due to Apple's WebKit restrictions, only Safari can access mic/camera on iPhone and iPad. All other browsers on iOS are blocked at the OS level.

Check OS permission: Windows: Settings → Privacy → Microphone/Camera → toggle Allow on. Mac: System Settings → Privacy & Security → Microphone/Camera → enable your browser.

Check browser permission — lock icon in address bar → Microphone → Allow → reload.

Set correct default input: Windows: Settings → System → Sound → Input → choose your mic. Mac: System Settings → Sound → Input.

Raise OS input volume to at least 70%. Right-click speaker icon → Open Sound Settings → Input → Input Volume slider.

Close all audio apps — Zoom, Teams, Discord, OBS. Any of these can claim exclusive mic access and block the browser.

Unplug and re-plug USB or 3.5mm microphone. Avoid USB hubs — plug directly into the motherboard port.

Update audio drivers: Visit your PC manufacturer's support page and install the latest audio driver. On Mac, run System Software Update.

USB Mic: Ensure it is plugged in before opening the browser. The browser enumerates devices on page load — devices connected after loading may be missed. Reload after plugging in.

Bluetooth Mic: Pair the device fully in OS Bluetooth settings before opening the test. Ensure it is in the correct Hands-Free/Headset profile, not just Media Audio mode.

Bluetooth latency: Bluetooth audio adds 100–300ms codec latency. This is hardware behaviour — not a bug in the tool.

Gaming headset mic: Ensure the headset is set as the default input — not just default output. Many headsets have a separate mic device entry in Windows Sound Settings.

Speak loudly directly into the mic — built-in laptop mics have low sensitivity. Get within 15–20 cm.

Disable OS noise suppression: Windows Sound → Recording → Device Properties → Enhancements → Disable all enhancements. This is the most common cause of flat readings.

Enable Microphone Boost +20dB: Windows Sound → Recording → your mic → Properties → Levels tab → Microphone Boost slider.

For the Frequency Analyser — snap fingers or tap near the mic to generate a sharp transient and confirm the FFT is working.

Noise Suppression Test: Disable OS noise suppression before testing to get a baseline reading. Re-enable it to compare the suppressed result.

Echo Test: Use headphones — never open speakers. The echo loop routes output back through your mic if speakers are active.

Audio Latency Test: Plug in wired headphones. Bluetooth headphones add hardware latency that makes the test result inaccurate.

Vocal Range Test: Ensure a quiet room, no background noise, and grant mic permission. Hum a sustained tone starting low and rising to your highest comfortable pitch.

Connect both microphones before loading the page. Reload with both devices already plugged in to ensure both appear in the device selector.

Grant browser permission for each device when prompted — a separate permission event fires for each new device.

If both recordings sound identical, verify the device selector shows two different device names for Mic A and Mic B.

Confirm the volume meter was moving during recording — a flat meter means no audio was captured.

Always press Stop before pressing Play. Recordings are only finalised after the stop event fires.

Check OS output volume and ensure the browser tab is not muted (right-click tab → unmute).

Safari has limited MediaRecorder support — switch to Chrome or Edge for the most reliable recording experience.

Check for a blocked download notification in Chrome's address bar → click Allow.

WebM won't play in Windows Media Player: Install VLC Media Player (free) — it plays WebM/Opus natively.

Convert to MP3: Open VLC → Media → Convert/Save → Add file → select MP3 profile → Convert. Or use cloudconvert.com.

iOS Safari download: Long-press the audio element → Share → Save to Files.

Check browser isn't muted: Right-click the browser tab → look for the speaker/mute icon → click to unmute if present.

OS output device: Right-click speaker icon → Open Sound Settings → Output → select the correct speakers or headphones as default.

Browser autoplay blocked: Click anywhere on the page first, then press the Play / Test button. Browsers block autoplay until a user gesture is made.

Check the physical volume knob or inline control on your headphone cable — make sure it is not turned to zero.

Headphone Test: Use the stereo balance test to verify left and right channels independently. If only one side works, the issue is hardware (cable damage or driver issue).

Crackling or distortion: Lower OS output volume below 85%. Distortion at high volumes is usually driver or hardware clipping, not a tool issue.

Bluetooth headphones cutting out: Move closer to the audio source. Bluetooth drops at distance or through walls. Try re-pairing the device.

Only one channel working in Headphone Test: Swap the headphone jack to a different port. Try a different pair to isolate hardware vs software fault.

Click the lock icon → Camera → Allow → reload the page.

OS camera permission: Windows: Settings → Privacy → Camera → Allow apps to access your camera + enable for your browser. Mac: System Settings → Privacy → Camera → tick your browser.

Close Zoom, Teams, Skype — these hold exclusive camera access and block the browser from accessing it.

Check your laptop's physical camera privacy shutter — many laptops have a sliding cover over the webcam lens.

iOS: Use Safari. Go to Settings → Safari → Camera → Allow. Chrome on iOS cannot access the camera.

Click the Fullscreen button before running the test. Dead pixels are only visible against a solid colour background — browser chrome must be hidden.

Press F11 (Windows) or use the browser's fullscreen mode to remove the address bar and tabs before testing.

Cycle through all colours — Red, Green, Blue, White, Black. A dead pixel appears as a dot that does not change colour as the background cycles.

Clean your screen with a soft cloth first — dust and smudges can look like dead pixels from a distance.

The Touch Screen Test requires a device with a touchscreen — it will not work on a non-touch laptop or desktop monitor.

Clean your screen: Fingerprint smudges, water, or screen protectors with air bubbles can cause missed touch points.

Windows touch driver: Device Manager → Human Interface Devices → HID-compliant touch screen → right-click → Enable Device.

On Android: check that "Developer Options → Pointer Location" is off — this can interfere with touch visualisation.

Try the test in Chrome on your device — Safari on iOS supports touch events, but some Android browsers may restrict the Pointer Events API.

Press a button on the controller after the page loads. The Gamepad API requires a button press to register the device — simply connecting it is not enough.

Wired connection recommended: Connect via USB for the most reliable detection. Wireless controllers add latency and may have inconsistent browser detection.

Windows — install driver: Xbox controllers are plug-and-play. PS4/PS5 controllers may need the DS4Windows driver. Generic controllers need a manufacturer driver.

Chrome only for Gamepad API: Firefox has limited Gamepad API support. Safari does not support it. Use Chrome or Edge for controller tests.

Check chrome://gamepad-internals/ — if your controller appears there but not on the test page, reload the test page with the controller already connected.

Bluetooth controller: Pair in Windows Bluetooth settings first. For PS4/PS5 over Bluetooth, hold the Share + PS button simultaneously to enter pairing mode.

Stick Drift Test: Place your controller flat on a surface and do not touch the sticks. Any movement shown in the visual indicator confirms drift. If the dot returns to perfect centre, no drift is detected.

Deadzone Test: Move the stick slowly from the centre outward. The deadzone boundary is the point where movement first registers. A large deadzone indicates wear — the stick requires calibration or replacement.

If stick values show constant maximum deflection, the controller may have a disconnected or broken potentiometer — contact your controller manufacturer for warranty service.

Recalibrate on Windows: Search "Set up USB game controllers" → select your controller → Properties → Settings → Calibrate → follow the on-screen wizard.

Vibration (haptic feedback) is only supported on controllers that have rumble motors — DualShock 4, DualSense, Xbox One, Xbox Series. Generic or mobile gamepads typically do not support it.

The Gamepad Vibration API requires Chrome — it is not supported in Firefox or Safari.

Connect via USB — vibration via Bluetooth is not supported by the Gamepad API in most browsers.

Connect your MIDI device before opening the MIDI Test page. The Web MIDI API enumerates devices on page load.

When prompted, click Allow for MIDI device access — this is a separate browser permission from microphone access.

Chrome only: The Web MIDI API is not supported in Firefox or Safari. Use Chrome or Edge exclusively for MIDI testing.

Ensure your MIDI device has a working USB driver installed. Check Device Manager → Sound, video and game controllers — your MIDI device should appear without an error flag.

Click on the test area first to ensure the browser window has focus. Key events only fire when the browser has keyboard focus.

Browser shortcut conflict: Some keys (F5, F11, Ctrl+T etc.) are intercepted by the browser before they reach the page. This is expected — use a dedicated keyboard tester app to test system-level keys.

N-Key Rollover (NKRO): If multiple simultaneous keys are not all registering, your keyboard may not support NKRO. This is a hardware limitation, not a bug.

Wireless keyboard lag: Replace batteries or re-pair the USB dongle receiver if keys register slowly or intermittently.

If a specific key never registers, it may have a hardware fault (damaged switch). Test in a text editor to confirm — if it doesn't type there either, the key is physically broken.

Click inside the test area to give it mouse focus before testing buttons.

Right-click blocked: Some browsers intercept the context menu on right-click. The test should still register the button event even if the context menu appears — dismiss it and check if the button lit up.

Extra mouse buttons (Side buttons): Browser-level MouseEvent only captures up to 5 buttons. Buttons 6+ are typically handled at driver/OS level and may not appear in browser tests.

Scroll wheel not detected: Ensure the mouse cursor is inside the test area when scrolling — scroll events only fire when the cursor is over the target element.

Click on the clicker area first to give it keyboard focus. Press Spacebar while the area is focused.

Some browsers may scroll the page on Spacebar if a scrollable area has focus. Click the specific clicker region to redirect focus.

If Spacebar key hardware is faulty, no keydown event fires. Test with the Mouse Test or Keyboard Test to confirm key status.

The Mobile Test requires a smartphone or tablet. It will not produce meaningful results on a desktop browser.

Gyroscope/Accelerometer not reading: On iOS, go to Settings → Safari → Motion & Orientation Access → toggle ON. iOS 13+ requires explicit user permission for motion sensors.

Android: Chrome for Android supports DeviceMotionEvent without additional permissions in most versions. If sensors are not responding, try reloading in Chrome.

Select the correct input device inside the app: Zoom: Settings → Audio → Microphone dropdown. Meet: Settings (gear icon) → Audio. Teams: Settings → Devices → Microphone dropdown. Select your microphone explicitly — do not rely on "Default".

Zoom exclusive mode: Zoom → Settings → Audio → Advanced → uncheck "Allow Zoom to adjust my microphone level" and "Suppress background noise". These can conflict with certain microphones.

Microsoft Teams: Settings → Privacy → Microphone — ensure Teams is allowed system-level microphone access in OS privacy settings.

Google Meet browser mic: Meet runs in Chrome — check chrome://settings/content/microphone and ensure Meet's domain is not blocked.

Restart the app after changing audio settings. Zoom and Teams cache audio device selections and may not pick up the new setting without a restart.

Click lock icon → Camera → Allow → reload. See Display Tests (Section 05) for full webcam troubleshooting.

Close any other app using the camera — only one application can access the camera at a time.

If camera feed is black/green: update your webcam driver from the manufacturer's website. A corrupt driver commonly causes a black video feed.

External USB webcam not detected: Plug directly into the PC port, not a USB hub. Reload the page after connecting.

Disable VPN or proxy before running — VPN routing significantly skews speed test results and may cause the test server connection to fail.

Close all other tabs and applications that use bandwidth — streaming, downloads, cloud sync — to get an accurate reading.

Try a different browser — ad blockers and privacy extensions can block the WebSocket or Fetch requests used by speed test engines.

Run the test via a wired Ethernet connection for your true ISP speed. Wi-Fi introduces variable overhead that can lower results by 10–40%.

Run the test 3 times and take the average — network conditions fluctuate moment to moment.

Wi-Fi interference: Move closer to your router. Switch to the 5GHz band if available — it has less interference than 2.4GHz.

Restart your modem and router by unplugging for 30 seconds. This clears cached routing tables and often improves speeds.

If speeds are consistently well below your plan's advertised rate, contact your ISP — this is a network infrastructure issue, not a browser or tool issue.

Reset permission: lock icon → Microphone/Camera → Reset → reload → Allow.

Check chrome://settings/content/microphone — remove mictestpro.com from Blocked list.

Disable extensions in Incognito: chrome://extensions → disable uBlock, Privacy Badger, Adblock one by one.

Enable hardware acceleration: chrome://settings → System → Use hardware acceleration when available → Relaunch.

Clear site data: chrome://settings/siteData → search mictestpro.com → Delete all.

Check edge://settings/content/microphone → remove any block on mictestpro.com.

Set Tracking Prevention to Balanced for mictestpro.com: Settings → Privacy → Tracking Prevention → Exceptions → Add.

Disable "Enhance your security on the web" for this site if it is causing API blocks.

Shield icon → Permissions → Microphone → clear → reload → Allow.

about:config → search media.getusermedia.microphone.deny → set to false.

Turn off Enhanced Tracking Protection for mictestpro.com via the shield icon → disable for this site.

Note: Gamepad API, Web MIDI API, and some Canvas features have limited support in Firefox. Switch to Chrome for gaming/MIDI tools.

Safari menu → Settings for This Website → Microphone/Camera → Allow → reload.

System Settings → Privacy & Security → Microphone + Camera → ensure Safari is toggled ON.

iOS: Settings → Safari → Microphone → Allow. Camera → Allow. Only Safari can access these APIs on iOS.

MediaRecorder on Safari saves as .mp4 (AAC) not WebM. Gamepad API and Web MIDI API are not supported in Safari.

Click the Brave lion icon → toggle Shields OFF for mictestpro.com → reload. Shields block getUserMedia and Canvas API calls.

Shields → Fingerprinting → Allow all fingerprinting for this site. Brave randomises audio API outputs by default, causing inaccurate audio readings.