The Google internet speed test is one of the quickest ways for New Zealanders to check how their broadband is performing, without installing an app or leaving the search results page. Type "speed test" into Google, tap a button, and within about half a minute you get three numbers: download speed, upload speed and latency (ping). Because the tool is run by an independent, non-profit measurement project rather than by an internet provider, many Kiwis treat it as a neutral second opinion on the megabits they are paying for. This guide explains exactly how the test works, how to read the results against today's New Zealand fibre plans, why your figures can differ from your provider's own test, and how to troubleshoot a connection that looks slower than it should.
Quick facts
| Tool | Google internet speed test (in Google Search) |
| Powered by | Measurement Lab (M-Lab), a non-profit consortium |
| Method | NDT (Network Diagnostic Tool) |
| Measures | Download speed, upload speed, latency (ping) |
| Typical data used | About 9.4 MB (more on very fast connections) |
| Cost | Free — no app or sign-in required |
| NZ server | M-Lab hosts a test server in Auckland (via REANNZ) |
| How to open | Search "speed test" on Google, press Run Speed Test |
How to run the Google speed test
Starting the test takes just a couple of clicks. Unlike some dedicated speed-test websites that are cluttered with ads, Google shows a clean box at the very top of the search results page. When you press Run Speed Test, a small amount of data is sent to and from a nearby measurement server, and the result appears in roughly 30 seconds. It works in any modern browser, including Chrome, Safari, Edge and Firefox, on phones, tablets and computers alike. For the most reliable reading, close background apps first — a cloud backup, a game update or another person streaming video can all pull the figure down.
- Search trigger: type "speed test" or "internet speed test" into Google.
- One-click start: press the "Run Speed Test" button in the box at the top of the results.
- Cross-platform: the same test runs on mobile browsers, tablets and desktops.
- Plain-English summary: when it finishes, Google tells you whether the connection can handle activities such as HD video or multiple users at once.
| Step | Action | Why it matters |
|---|---|---|
| Search | Type "speed test" in Google | Fastest way to open the tool |
| Prepare | Close background tabs, downloads and apps | Stops other traffic skewing the result |
| Execute | Press "Run Speed Test" | Starts the download, upload and ping check |
| Analyse | Read the Mbps and latency figures | Shows the real quality of the connection |
What powers the test: M-Lab and NDT
The Google speed test is powered by Measurement Lab (M-Lab), an open, non-profit consortium of research, industry and academic partners that publishes one of the largest public collections of internet-performance data in the world. The underlying method is called NDT (Network Diagnostic Tool), and it measures the connection between your device and an M-Lab server. Because M-Lab is independent of any single provider, the results are often seen as more even-handed than a test that runs only inside an internet company's own network. All of the measurements are anonymised and released publicly for researchers to use. Helpfully for New Zealanders, M-Lab hosts test servers inside the country (in Auckland, supported by the research network REANNZ), so for many people the test runs against a local server rather than one across the Tasman or in the United States. If you want a fuller picture, it is worth also running a separate internet speed test and comparing the numbers.
How to read your results in New Zealand
A finished test shows three main figures. Download speed is how quickly you can pull data from the internet — loading a page, or streaming a film. Upload speed is how quickly you can send data out, such as your video feed on a Microsoft Teams call or a file syncing to the cloud; on most New Zealand plans it is lower than the download figure. Latency (ping), measured in milliseconds, is the delay before data starts moving; against a local server it is usually well under 20 ms. If your latency comes back over 100 ms, the test may have connected to an overseas server, which is a common reason results look worse than expected.
- Mbps (megabits per second): the standard unit for broadband speed in New Zealand.
- Download: around 25 Mbps is enough for smooth 4K streaming on a single device.
- Upload: important for remote workers who send large files to Google Drive, iCloud or OneDrive.
- Latency: the number gamers and video-callers care about most; lower is better.
New Zealand's fibre plans changed in 2025. Under Chorus's "Big Fibre Boost", the entry Fibre 50 tier doubled to about 100/20 Mbps, and the popular Fibre 300 plan — still the most common household choice — was lifted to about 500/100 Mbps at no extra wholesale cost. The table below shows realistic figures to expect on today's tiers. If you want the detail behind these numbers, see our guide to what Fibre 300, 500 and Max really deliver.
| Plan | Typical download (Mbps) | Typical upload (Mbps) | Local latency (ms) |
|---|---|---|---|
| Home Fibre Starter | ~100 | ~20 | < 15 |
| Fibre (was Fibre 300) | ~500 | ~100 | < 15 |
| Fibre Max (gigabit) | 900+ | 400–500 | < 10 |
| Hyperfibre | 2000–8000 | 2000–8000 | < 5 |
Why your numbers may differ from an ISP test
It is common for the Google test to return a slightly lower figure than a test run inside a Chorus or Spark app. The Google/M-Lab test measures performance across the wider internet to a neutral server, whereas a provider's own test often measures only within its local network, where there are fewer bottlenecks. Neither is "wrong" — they answer slightly different questions. If your Google result is much lower, it can point to congestion further out toward the international gateways where New Zealand's undersea cables connect to the rest of the world, rather than a fault on your own fibre line. Running the free Ookla Speedtest.net as well lets you pick a specific local server and cross-check.
What affects the accuracy of the test
The biggest variable for most households is the difference between Wi-Fi and a wired connection. Even on a gigabit plan, a laptop on an older 2.4 GHz Wi-Fi band, or one several rooms away from the router, may report only a fraction of the line's real speed. To see your true line speed, plug the computer directly into the router with a Cat5e or Cat6 cable. Thick walls in an older villa, distance from the router, and how many devices are active all change the wireless figure — which is why a "slow" Wi-Fi result is often a Wi-Fi problem, not a broadband one. A dedicated Wi-Fi speed test helps you tell the two apart.
- Wired vs wireless: Ethernet is faster and steadier than Wi-Fi for testing.
- Device age: older phones and laptops have Wi-Fi chips that cannot keep up with modern fibre.
- Congestion at home: other people streaming 4K while you test will lower your figure.
- Browser add-ons: some ad-blockers or VPN extensions can interfere with the test.
| Factor | Impact on result | What to do |
|---|---|---|
| Wi-Fi interference | High | Use the 5 GHz band or plug in via Ethernet |
| Distance from router | Moderate | Test in the same room as the router |
| VPN switched on | High | Turn the VPN off before testing |
| Outdated browser | Low | Keep Chrome, Edge or Safari up to date |
The Google speed test is not Google Fiber
A common point of confusion: the Google speed test has nothing to do with Google Fiber (Wikipedia), Google's fibre-broadband service in parts of the United States. Google Fiber is not available in New Zealand and never has been. The speed test is simply a diagnostic feature inside Google Search that works no matter which local provider — Spark, One NZ, 2degrees, Contact or another retailer — you are connected through.
Troubleshooting a slow Google speed test result
If the test shows far less than you pay for, a few checks usually help before you call your provider. The classic reset is to unplug the router and the ONT (the fibre box on the wall) for about 60 seconds, which clears many software hangs. Next, check where the router sits: it should be central and out in the open, not inside a cabinet or behind a television. Finally, run the test on a second device — if only one device is slow, the problem is that hardware, not your broadband.
- Reboot the ONT: the small white fibre box occasionally needs a restart to refresh the link.
- Find bandwidth hogs: use Task Manager (Windows) or Activity Monitor (Mac) to spot an app quietly using the connection.
- Update firmware: newer router firmware can noticeably improve Wi-Fi performance.
- Retest at different times: a slow evening but fast morning points to congestion, not a line fault.
| Symptom | Likely cause | Fix |
|---|---|---|
| High latency | Test connected to an overseas server | Retest, or cross-check with a tool that lets you pick a local server |
| Low download | Background downloads running | Pause Steam, Windows or app updates |
| Inconsistent figures | Faulty or old Ethernet cable | Swap to a newer Cat5e/Cat6 cable |
| Page won't load fully | DNS issues | Try a public DNS such as 8.8.8.8 |
When to contact your provider
If a wired test consistently comes back well below your plan's advertised speed, it is worth logging a fault. New Zealand's Commerce Commission runs the independent Measuring Broadband New Zealand programme (delivered by SamKnows), which publishes regular reports on the speeds providers actually deliver — a useful reference point when you raise a complaint. Keep a record of several results taken at different times of day; a clear pattern is far more persuasive to technical support than a single slow reading.
Google speed test vs Ookla vs Fast.com
The Google test is convenient, but it is not the only option. Ookla's Speedtest.net is the long-standing industry standard and lets you choose which New Zealand city server to test against. Fast.com, run by Netflix, measures the speed specifically from Netflix's servers — so if Google looks fast but Fast.com is slow, it can hint that streaming traffic is being throttled or is congested. For a straightforward everyday check the Google tool is an excellent all-rounder; for deeper troubleshooting, a tool that lets you pick the server is handy. It is also worth checking your ping test separately if lag rather than raw speed is the issue.
| Tool | Best for | Key advantage |
|---|---|---|
| Google (M-Lab) | A quick, neutral check | No ads, built into search, local server |
| Ookla Speedtest.net | Detailed troubleshooting | Choose a specific NZ city server |
| Fast.com | Streaming readiness | Measures from Netflix's servers |
| Provider app | In-network check | Tests within your ISP's own network |
Why server location is the biggest variable
Every speed test measures the path between you and one specific server. If a test connects to Sydney instead of Auckland, your latency roughly doubles and your download figure can fall. When you compare tools, always check the reported server location so you are comparing like with like — a "slow" result is sometimes just a distant server.
Gigabit and Hyperfibre: why browser tests can under-report
On very fast plans — gigabit Fibre Max or Hyperfibre — a browser-based test can show less than the line is capable of. This is not usually a fault in your fibre. Saturating a multi-gigabit link depends on your device's processor, network card and Wi-Fi standard, and a single browser test on ordinary consumer hardware can struggle to push that much data at once. To confirm a true gigabit-plus figure, use a wired connection and a dedicated desktop speed-test app rather than a browser, and make sure the computer has a gigabit-capable network card and a Cat5e or Cat6 cable (older Cat5 cabling is only rated for 100 Mbps).
- Wi-Fi standard: Wi-Fi 5 typically tops out a few hundred Mbps; Wi-Fi 6 gets much closer to fibre speeds.
- Network card: some older PCs are limited to 100 Mbps and can never show gigabit.
- Cabling: use Cat5e or Cat6 for gigabit; Cat5 is a hard 100 Mbps bottleneck.
- Device load: a very fast test can briefly max out an older processor and dampen the figure.
Mobile data vs Wi-Fi tests, and using a VPN
With 5G now widespread in New Zealand's main centres, a Google speed test on mobile data can sometimes beat home Wi-Fi. Two cautions apply. First, a single high-speed test can burn through a lot of mobile data in seconds, so watch your cap. Second, if you are trying to test your home broadband, turn mobile data off first so the phone is definitely using your Wi-Fi and not the cellular network. And if you run a VPN for privacy, remember it will always lower the result: the VPN adds an extra hop and encrypts your traffic, which raises latency and reduces raw speed. Disconnect the VPN before testing to see your connection's true capability.
Key points
- The Google speed test is run by the independent non-profit M-Lab, not by any internet provider.
- It measures download, upload and latency in about 30 seconds, free and with no app.
- For a true line speed, test over a wired Ethernet connection with the VPN switched off.
- Results can read lower than a provider's own test because they measure across the wider internet.
- On gigabit and Hyperfibre plans, a browser test may under-report — use a dedicated app to confirm.
- Keep a short log across the day; an evening drop usually means area congestion, not a home fault.
Building a simple speed test log
A single test at 10 pm on a Friday does not tell the whole story. To understand your connection's real health, run the test a few times a day — morning, afternoon and during the evening peak (roughly 7 pm to 11 pm, when most households are streaming) — and note the figures. If mornings sit near your plan speed but evenings collapse, that is a classic sign of network congestion in your area rather than a problem with your own gear. A short log like the example below is exactly the kind of evidence your provider will take seriously.
| Time | Download (Mbps) | Upload (Mbps) | Ping (ms) |
|---|---|---|---|
| 10:00 am | 505 | 102 | 8 |
| 3:00 pm | 498 | 99 | 10 |
| 8:30 pm | 60 | 92 | 22 |
| Reading | Large evening drop — a sign of peak-time congestion | ||
Reference sources
Frequently asked questions
How do I run the Google speed test in New Zealand?
Open any browser, search for "speed test" on Google, and press "Run Speed Test" in the box at the top of the results. The check finishes in about 30 seconds and shows your download, upload and ping figures.
How much data does the Google speed test use?
Google says a typical test uses around 9.4 MB, but the amount rises with your connection speed — a very fast fibre or 5G link can consume considerably more in a single run, so be careful on a capped mobile plan.
Why is the Google test slower than my provider's test?
Your provider's test often measures only within its own network, while the Google/M-Lab test measures across the wider internet to a neutral server. That path has more potential choke points, so it can read a little lower — and it is a more realistic view of everyday browsing.
Is the Google speed test accurate?
Yes, for everyday browsing and streaming it is reliable, and M-Lab hosts a server in Auckland so latency stays low for many Kiwis. On gigabit or Hyperfibre plans, though, a browser test may under-report — use a wired connection and a dedicated app to confirm the full speed.
What is a good ping for New Zealanders?
Under 20 ms to a local server is excellent. Expect roughly 30–50 ms to Australia and about 130–160 ms to the United States — higher figures simply reflect the distance the signal travels.
