Windows 11 Adds Built-In Internet Speed Test, Drops Bing Redirect
Microsoft is testing a native internet speed test in Windows 11 that measures upload and download speeds without sending users to a Bing search.
According to ZDNET, Windows now has a built-in internet speed test tool, available first to Windows Insiders. The tool measures upload and download speeds over either an Ethernet or Wi-Fi connection, and the outlet explains how testers can try it out.
TechRadar reports that the existing speed test in Windows 11 works by redirecting users to a Bing search page to run the measurement. The outlet calls this approach clunky and describes it as a form of Bing promotion. According to TechRadar, a recent preview release, build 26340.9767, changes how the feature works and integrates the speed test fully into the operating system.
Windows Central, cited by TechRadar, is the source for the detail about the preview build. The reporting places the change within the Quick Settings area, though the outlets do not describe the new interface in depth.
Taken together, the reports point to a shift in how the feature is delivered. Rather than handing the task off to a web search, the test appears to run inside Windows itself. The outlets do not say when the change will reach general users, and they do not describe how the new test is built or which servers it uses.
Background
Windows has long included small utilities that help people diagnose their computers and networks. Some of these tools live in the Settings app, others in Quick Settings or the taskbar, and many have been expanded or replaced over several Windows releases. Checking connection speed is a common task. Most people run it when a video call stutters, a download seems slow, or a streaming service buffers, and the results are often used to decide whether to contact an internet provider or move closer to a router.
Using a search engine to run a speed test is a practical shortcut. A search page can show a test widget with minimal development work, and it keeps the feature current without a full operating system update. The tradeoff is that the user lands in a browser-based experience that may show advertising, search suggestions or unrelated results. When that search provider is also the company that makes the operating system, critics often question whether the feature serves the user or the company's own products.
Speed tests in general measure throughput between a device and a test server, and results can vary with the server chosen, the time of day, background traffic, the Wi-Fi band in use, and the condition of the hardware. A single measurement is a snapshot, not a full picture of a connection. Operating system makers that build their own tests usually aim to provide a quick, consistent way to check these numbers without leaving the system.
Windows Insiders are volunteers who receive preview builds before general release. Features tested in these channels are often changed, delayed or removed based on feedback, so a feature appearing in preview does not guarantee it will ship in its current form.
Why it matters
The story is small on its face, but it touches a broader question about how platform companies use default features. A speed test is a useful, low-stakes tool, and the way it is delivered affects how users perceive the operating system. When a built-in utility sends people into a search engine, it blurs the line between a helpful feature and a marketing channel. Users who simply wanted a number may end up seeing a page full of promotional content.
For ordinary users, a native tool offers a more direct experience. It can be quicker to open, easier to understand and more consistent with the rest of the interface. Someone troubleshooting a connection on a deadline benefits from fewer steps and fewer distractions. The change also reduces dependence on a web page that could change its layout, its test provider or its availability without notice.
The reporting also matters for how people judge Microsoft's approach to Windows 11 more generally. Several earlier design decisions have drawn criticism from users who felt the operating system pushed them toward particular services. A move away from one example of that pattern may signal responsiveness to feedback, though the outlets present it as a single change rather than a policy shift.
Finally, the story is a reminder that preview channels reveal how product teams are thinking. Insiders who test features early are, in effect, helping shape the final design, and their reactions can influence what reaches everyone else.
What to watch
The most important open question is when the native speed test will reach general Windows 11 users. Preview features can change or disappear, and the outlets do not provide a release timeline. Readers should watch for official notes from Microsoft as builds move through the preview channels.
It will also be worth seeing how the tool performs in practice. Accuracy, the choice of test servers, and whether results match those from established third-party tools will all shape how much people trust it. Independent comparisons may help answer those questions once the feature is widely available.
Observers should also check whether the change is accompanied by similar adjustments elsewhere in Windows 11. If other utilities that currently route through search are rebuilt as native features, that would suggest a wider change in approach. If not, this may remain an isolated fix.
Finally, watch for how Microsoft describes the feature. Whether it is presented as a neutral diagnostic or as part of a broader service bundle will affect how users read the change.
Viewpoints
Commentary from our columns: three angles on this story.
The Skeptic open questions and weak points
It is easy to cheer when a company stops sending users to its own search engine, but the reporting here leaves more questions open than answered. The outlets describe a preview build, and preview features are routinely altered or withdrawn before they reach anyone else. Nobody has yet said when this tool will ship, what servers it will measure against, or how its results will compare with independent tests.
There is also a question of motive. Redirecting a speed test to Bing was a choice, and reversing it is a choice too. Is this a principled correction or a response to criticism that happened to be loud enough? The answer changes how much weight we should give to the promise that Windows will stop nudging people toward its own products.
Until a stable release arrives and the measurements can be checked against other tools, the safest reading is cautious. The feature is a step in a better direction, not proof that the direction will hold.
The User what changes for people who use it
Think about what this means for someone with a slow connection on a weeknight, trying to figure out why a video call keeps freezing. Right now the path is clumsy: open the tool, get pushed into a web search, and hope the results page is not cluttered with other content. A native test that runs inside Windows removes a few steps and a bit of frustration.
That matters more than it sounds. Most people do not want to become network engineers. They want a quick answer and a sense of whether the problem is their provider, their router or their own device. A tool that gives a clear reading without sending them somewhere unexpected lowers the barrier to asking for help at all.
Of course, the benefit depends on the feature actually arriving and working well. For now it is a preview, and the people who see it first will be the Insiders who opt in. For everyone else, the practical advice is to keep using whatever speed check they trust until the built-in version is available.
The Builder the engineer's view
From an engineering standpoint, the interesting part of this story is the architecture change. Running a speed test through a web search is a convenient shortcut: it ships without an OS update and offloads the test to someone else's infrastructure. Moving the test into the operating system means Microsoft has to own the measurement logic, the server selection and the reporting, and it has to make those pieces behave consistently across Ethernet, Wi-Fi and different hardware.
Those are real engineering problems. Throughput numbers are sensitive to how many parallel streams are used, how buffers are sized and which server is chosen. A native tool that gives results people trust will need careful design and transparent defaults. If the implementation simply mirrors a third-party test, it inherits that test's limits without adding much.
The preview build is the place to watch. Insiders testing it can judge whether the numbers are stable across repeated runs and whether the interface stays out of the way. Those early signals will show whether this is a well-built utility or just a relocated one.