Avada I/O bench · ports + network
Ports and connectivity test
Check browser-visible USB, serial, Bluetooth, camera, microphone, display, battery and network signals without inventing results for hidden physical ports.
Browser diagnostic
Ports and connectivity capability check
Each sensitive check begins with a browser-owned permission prompt. Unsupported capabilities are labeled clearly.
Ports and device interfaces
Browser connectivity report
Internet status
Browser reports an active network connection.
onlineConnection information
This browser does not expose network type, Wi‑Fi signal strength or estimated throughput.
Battery and charging
Not exposed by this browser. Browsers cannot identify the physical charging port or adapter model.
Used-laptop check
Confirm capabilities without false positives.
Physical inspection still matters. Use the browser checks alongside a real cable or device for every port you plan to use.
Plug in a known device
A real USB drive, headset or display is the strongest evidence that its socket works.
Grant access deliberately
Choose only the device you are testing in the browser-owned permission picker.
Compare wired and wireless
Check Ethernet, Wi-Fi and Bluetooth separately because one working radio proves nothing about another.
Inspect for physical damage
Bent pins, loose sockets and corrosion cannot be detected by a webpage.
Ports & Connectivity guide
Read the result like a technician
This page reports only what the browser genuinely exposes, and labels everything else unsupported rather than guessing. That honesty is the point: a false pass on a port you are about to depend on is worse than no answer at all.
How to check ports before you buy
Work through the supported checks first and grant access only to the device you are actually testing in the browser-owned picker. Then finish the job physically: plug a known-good device into every socket you plan to use, check Ethernet and Wi-Fi separately, and pair one Bluetooth accessory. Look at the sockets too — bent pins, a loose shell or corrosion are things no web page can detect and a buyer should never miss.
An empty port is invisible
A browser cannot look at an empty socket. No API reports whether an HDMI, Ethernet, audio or USB port is physically intact, so an unsupported or empty result here is not evidence of a fault — it is the honest limit of what a web page is allowed to know.
Why some checks say unsupported
WebUSB, Web Serial and Web Bluetooth are Chromium-first and require HTTPS. Firefox and Safari do not implement them, so an unsupported label there says something about your browser rather than about the laptop. Use a current Chromium-based desktop browser for the widest coverage.
A known-good device proves the most
Plug in a device you already know works — a USB drive, a headset, an external display — and confirm the operating system sees it. That single action proves more about a socket than any browser API can, and it costs nothing.
Permissions and privacy
The selected device is read locally to display a short result in this tab. Nothing about it is sent anywhere; the page has no endpoint that accepts device information. Network readings are labelled as browser hints because they are rough estimates, not measurements.
Questions
Ports & Connectivity FAQ
Clear answers about permissions, privacy and what a browser can reliably test.
Can a website detect every physical laptop port?
No. Browsers cannot inspect an empty HDMI, Ethernet, audio or USB socket. Supported APIs can confirm selected devices only after you grant permission.
Why are WebUSB, Web Serial or Bluetooth marked unsupported?
These APIs are browser- and platform-dependent and generally require HTTPS. A current Chromium-based desktop browser offers the broadest support.
Does selecting a device send its details to AvadaBD?
No. The selected device object is read locally to show a short result in this tab. The page has no endpoint for uploading device information.
Can this page measure Wi-Fi signal strength?
No standard browser API provides Wi-Fi signal strength. Some browsers expose a rough connection type, RTT or downlink estimate; the page labels those values as browser hints.
