Diagnostic tool

Speed test: the connection you use with BeebeeBoard

BeebeeBoard runs in the browser, so the quality of your line shows on every screen. This test measures it in under a minute: it installs nothing, it does not require you to be signed in to BeebeeBoard, and you can repeat it as often as you need.

Run the test

This is the Ookla Speedtest, the one running on our subdomain. Press GO and stay on the page until the four numbers appear: download speed, upload speed, ping and jitter.

The test connects to Ookla's servers and does not go through BeebeeBoard's: the result stays on your screen and never reaches us. Ookla, for its part, records the IP address the measurement comes from, as its own notice inside the box says. If you need the result for support, take a screenshot of it.

How to read the result

Four numbers, four different things. The big one in the middle is only the first.

Download

How fast data reaches you. You feel it when the calendar opens, on a record full of attachments and in document previews.

Upload

How fast data leaves you. This is the number that counts when you upload medical reports, attachments and invoices: it is almost always much lower than the download.

Ping

The time a packet takes to go and come back. It is not speed, it is responsiveness: a high ping makes the interface feel slow even on a fast line.

Jitter

How much the ping swings from one measurement to the next. It matters for continuous things — a video consultation, a signature on a tablet — where an unsteady line shows more than a slow one.

We do not publish a minimum threshold: it depends on how many people share the same line and on what they are doing at the same time. The comparison that really helps is with yourself — the same test, from the same place, from when everything was fine.

If the numbers are low

Before concluding that the line is slow, five checks in the order worth doing them.

  • Repeat the test three times a few minutes apart. A single measurement may have landed while someone else was downloading.
  • Try a cable. Wi-Fi loses far more than it seems, especially if the router is in another room or behind a load-bearing wall.
  • Look at what the network is doing. A backup in progress, a system update or a video call take up the line exactly while you are measuring it.
  • Turn off the VPN. If you are on a VPN, a proxy or a guest network, the test measures the intermediary too, not just your line.
  • Try a second device. If only one of them is slow, the problem is not the office line.

If the test looks fine but BeebeeBoard is still slow

Then the line is not the cause, and the three we see most often are these.

  • The browser. BeebeeBoard is developed and tested on the last two versions of Chrome and Edge, on the last two versions of Firefox and on its ESR, and on Safari 10 and later. If yours is behind, the unsupported browser page explains how to update it, browser by browser.
  • Blocked WebSockets. BeebeeBoard uses them to keep what you are looking at up to date. Some corporate firewalls and some antivirus products block them: the line is fast, but the screen looks frozen.
  • Browser extensions. Open BeebeeBoard again in a private window, where they usually do not load: if the slowness goes away, one of them is the cause.

If the problem is still there after these checks, write to us attaching the screenshot of the test: knowing which numbers we start from saves us having to ask you for them.

Frequently asked questions

No. The test runs on Ookla's infrastructure: the subdomain is ours in name only, the measurement data does not pass through our servers and we do not see it. If you want us to see it, send us a screenshot.

The whole path: the device you open this page on, the Wi-Fi or the cable, the router and the line, up to the nearest server. That is why the same line gives different numbers from two different rooms.

Because the bandwidth is shared among whoever is using it at that moment, and the path to the server changes. A single test says nothing; three tests close together say something.

BeebeeBoard exchanges data when you open a screen or save, not continuously like video streaming: what weighs most are the attachments, that is, the upload. More than peak speed, what counts is stability, which in the test is the jitter.

When something changes: a new router, a move to another room, a different contract, or the day the software starts feeling slow. Outside those cases, measuring every day adds nothing.