Pixeldrain Speedtest

How does this work?

The speedtest measures the maximum download speed from pixeldrain's servers to your computer. This speed is not affected by the daily download limit for free users.

What do the numbers mean?

The first number is the download speed in bytes per second. This is useful for estimating how long a file download will take.

  • 1 kB = 1000 bytes
  • 1 MB = 1000 kB
  • 1 GB = 1000 MB
  • etc..

The second number shows the download speed in bits. This is usually the speed your ISP advertises to you. This number is equal to the first number multiplied by eight, because there are eight bits in a byte.

The third number shows the latency to the pixeldrain servers. This is dependent on how far you are removed from the closest pixeldrain server. The lower the latency the faster your downloads will be, generally. The number shows request latency and not ping latency. HTTP requests have some overhead which means this latency number shows multiple round trips instead of one.

The last number shows how much data the speedtest was able to transfer in the duration of the test. The standard test is six seconds and the long test is twelve seconds. The long test might be slightly more accurate than the short one, but it uses more bandwidth.

Why is the speed different from other speed tests?

Most speed tests have servers in datacenters which are located very close to your home. They are also connected directly to your ISP which means that the ISP does not have to pay for the bandwidth because it stays within their network.

Pixeldrain does not have this luxury. Because our budget is very small we are only able to afford the cheapest bandwidth available. This means that the data has to travel further and is more likely to be throttled.

How do I read these results?

If the speed is a lot slower than your usual downloads it can mean two things.

  1. Your ISP is limiting the connection speed to pixeldrain's servers
  2. The pixeldrain servers are overloaded

Number two is usually not the case, when that happens I will tweet about it. Unfortunately there is nothing I can do about the first scenario. I might be able to get more servers and better bandwidth if the site gets many more subscribers, but for now that's out of reach.