Field-testing methods and progress
Starlink Australia review and real-world testing
This Starlink Australia review page explains how DigArt plans to assess everyday performance, connection stability, power use and installation conditions. Explore the testing method and the evidence still needed before we publish results.
What our Starlink Australia review will assess
Everyday performance
We plan to compare download, upload and latency measurements at different times. This approach helps show variation instead of relying on one unusually fast test.
Connection stability
We will record interruptions, packet loss and obstruction events. In addition, practical video calls and uploads will help show how those events affect everyday tasks.
Off-grid energy use
We will measure idle, typical and peak power consumption. Then we can use those observations to explain battery-runtime estimates and their limits.
Installation conditions
We will document dish placement, mounting, cabling and sky access alongside the results. Otherwise, readers cannot judge how closely the setup resembles their own.
How we plan to test Starlink
-
Document the complete setup
First, record the hardware model, service plan, mount, height and power supply. Also, note the router arrangement, cable route and surrounding obstructions. Describe the environment without publishing a private address.
-
Repeat performance measurements
Next, collect download, upload and latency samples during morning, afternoon and evening periods. Record the test server and connection type so readers can distinguish Ethernet results from Wi-Fi results.
-
Try everyday applications
Run video calls, streaming sessions, uploads and normal work tasks. For example, note whether a call drops or an upload needs restarting. Record test duration as well as any failures.
-
Measure power and energy
Use a suitable meter to record typical consumption and observed peaks. Identify the measurement point and any conversion equipment. This helps explain which losses the readings already include.
-
Track changing conditions
Record weather, app warnings and any changes to the installation. If we move the dish or change the power supply, we will note when that happens. Then we can separate results from different setups.
-
Summarise the evidence
Finally, report sample counts, test periods, medians and observed ranges. Explain interruptions and limitations alongside the figures. A result from one site should not imply the same experience across Australia.
Measurements planned for publication
| Measurement | Planned method | Reporting detail |
|---|---|---|
| Download and upload | Repeat tests at different times and record the server and connection type | Median, observed range, dates and sample count |
| Latency and packet loss | Record timed measurements during idle periods and practical use | Measurement duration, latency variation, packet loss and interruptions |
| Application stability | Try calls, streaming, uploads and cloud workflows | Task duration, failures, recovery and observed usability |
| Power consumption | Measure power and energy at an identified point in the supply path | Watts, watt-hours, test duration and conversion equipment |
| Obstructions | Record app observations and installation context | Warnings, timing and observed effects, with private details removed |
| Weather and environment | Keep notes alongside each testing period | Relevant conditions without assuming they caused every performance change |
These are planned measurements, not published findings. We will update this section when verified results are ready.
Evidence needed before a scored review
Before assigning a rating or drawing a performance conclusion, we need a documented set of observations.
- Record the testing dates, duration and total sample count.
- Identify the hardware, service plan and available firmware details.
- Collect speed, latency and packet-loss records from different periods.
- Measure power at a clearly identified AC or DC point.
- Include obstruction information with private location details removed.
- Match weather and installation notes to the test timestamps.
- Explain what the evidence supports and what remains uncertain.
How we will report the results
We will distinguish measurements from interpretation. In addition, we will explain our commercial relationships so readers can assess the review in context.
- Publish only results and experiences we can substantiate.
- Show typical observations alongside the best and worst recorded samples.
- Include dates, sample counts and test conditions.
- Describe installation photographs accurately.
- Disclose relevant product sales and referral benefits.
- Discuss limitations and alternative services where relevant.
- Record material changes when updating the review.
Checking Starlink availability?
You can review the current offer directly with Starlink while our testing continues. Our referral link opens the Residential page. Confirm availability, kit compatibility and eligibility for your selected service before ordering.
Commercial and referral disclosure: DigArt sells Starlink mounting accessories and may receive a benefit from qualifying referral orders. Starlink controls referral eligibility, service-credit amounts and offer conditions. This page does not yet contain a completed performance review.
