Web Client

Web client

The website includes the WebSockets test and all presentation of measurements.

Start Page

On the start page, you can find the navigation area and a button to start a new measurement. As the selection of a measurement server is done automatically based on IP address of client, there is no graphical user interface confusing end-users by showing them different servers, which cannot be selected. On the other hand there could be scenarios where end-users should have the right to choose a measurement server. In that case we will deliver such a graphical user interface. Nevertheless this topic has to be discussed in the requirements analysis phase.

Test Page

The test page is shown during a measurement visualizing all values and showing the actual process of the measurement. After finishing the measurement, the end-user will be transferred to detailed results.
The MoQoS Open Nettest is implemented in HTML5 using Javascript with Websockets. This is because other alternatives like Java or Flash will not be supported in the future. Whereas HTML5 and Javascript are already the technologies for the future. One downside is the fact that it is not possible to send UDP-packets. Especially the measurement for Delay variation (sometimes called Jitter) and packet loss will make sense only when using UDP. For that reason these two parameters cannot be measured in browsers. However it is possible to measure TCP Ping Delay Variation, which is not a very significant parameter, but could be a hint for a weak internet connection.
As an alternative there is also a Java client for browsers implemented in MoQoS Open Nettest, which is capable of measuring UDP Jitter and packet loss as well as a lot of many other QoS parameters, too. But as there are a lot of drawbacks of using Java in browsers the decision to use this technology should be discussed in the requirements analysis phase in depth.


The history page includes a list of all past measurements done by this client or synchronized to this client.


If you want to synchronize measurements between two different devices (e.g. a browser and a mobile device), you can request a synchronization code on each of these devices and fill in this synchronization code on the second device. This could be done with more than two devices as well. As a result, you can see all measurement details ever made from all synchronized devices on each single device.

Detailed Results

This page shows all detailed results, which were collected in one single measurement.

Detailed Speed/Throughput Results

This section holds information of median download speed, median upload speed, median latency and signal strength (if available).
Furthermore, it shows all secondary parameters collected during the measurement (e.g. durations, coordinates, autonomous system names, amount of transferred data, etc.)

Detailed Graphs

Detailed graphs showing download speeds, upload speeds, signal strength and latency values over time.


A small map is showing the location where the measurement was done. If client was moving it shows the movement too.

Map View

This page holds a map showing a specific area and on top several layers visualizing the aggregated and/or detailed measurement results.

Base Map

By default, the MoQoS Open Nettest is using Google Maps as the base layer. This includes road view, satellite view and hybrid view. It is possible to use other base maps like bing maps or local base maps.

Heat Map

The heat map layer draws a coloured cloud showing aggregated measurement results. For that reason, speeds are displayed as a range from green to red colour and the amount of measurements changes the opacity value.


Each measurement is displayed as a point on the map. Own measurements are displayed as a triangle. It is possible to click on a point or triangle to see all anonymized results of this single measurement in detail.


Defined areas, could be political districts, squares of free defined size (e.g. 100 x 100 m) of 1 colour and 1 opacity. Colour is defined by the median value (download, upload, signal, latency) of all measurements in that area.


It is possible to filter measurements which are shown on the map by connection technology (mobile measurements, WIFI measurements and browser measurements), by mobile radio technology (2G, 3G, 4G) in case of mobile measurements, by measurement parameter (download, upload, signal strength and latency), by time period (e.g. last week, last month, etc.; free configurable) and by statistical values (e.g. 80% percentile, median, etc.; free configurable)


The search page shows by default a list of the last 100 measurements. Clicking on a single row leads to a detailed view of the results of this measurement similar like described above.

Additionally, there is an advanced search functionality to search and filter specific measurements by choosing various parameters.


The search field provides functionality to search an address to focus and zoom the map.


The statistics page brings some statistical information about averages from different operators and different devices.

Additionally, there are filters to select the country of measurements, a time span, the device type, statistical parameters and location accuracy.

This page should give an overview how the results could be processed statistically. It is no intention to compare operators.

Help Page

The help page supports end-users how to use the system and gives answers to frequently asked questions. Therefore, it is designed like a user manual.


Here you can find a description of who is responsible for the contents.

Leave a Reply