It opens inside Bing in your default browser:
Last year, we reported on a speed test feature coming to Windows, built right into the taskbar, where you could gauge your internet connection without venturing out to a browser. In reality, it was more like a shortcut that would still open Bing and take you to a miniaturized version of Ookla's Speedtest. Today, that feature is finally here in the Insider program, as part of Build 26100.7918 and 26200.7918.
In these updates pushed to the Release Preview channel, you'll now see an option to "Perform speed test" when you right-click on the network icon or open the Wi-Fi/cellular quick settings. Upon clicking, your default browser will open up Bing, where you'll see a simplified Ookla interface with a meter in the middle, and three stats below: Latency, Download, and Upload.
That means this is technically not a "native" feature, rather just a website link in your taskbar. Still, for the uninitiated, it can be a convenient way to check their internet speed. Let's say you're in a game and suddenly start experiencing packet loss; instead of Alt-tabbing into a browser for a speed test, you can just right-click on your Ethernet icon and go there directly.
This feature will save you a click or two; however, some users may be disappointed by yet another web wrapper implemented inside Windows. Windows has enjoyed a poor run of stability recently, with even Microsoft recognizing its slack, so a built-in taskbar speedtest is probably not high on most users' list of priorities.
(Score: 2) by ls671 on Sunday February 22, @02:32PM (4 children)
Some people like links and icons. As a matter of fact, they are just lost without icons on their desktop for everything they might use.
Everything I write is lies, including this sentence.
(Score: 3, Interesting) by JoeMerchant on Sunday February 22, @04:41PM (3 children)
Back in the day, some guy somewhere coded up a tray icon: Modem Status. It had little colored circles for Rx and Tx activity and was generally nice to have for awareness of your connection health, and potential activity you weren't expecting. I think the author asked for donations or some such as was the tradition of the day.
Then a Windows update came out with a modem status thingy looking exactly the same - I don't believe they licensed it, I think they just blatantly copied his widget and rolled it into the OS. I imagine there was some kerfuffle following because in a later revision M$ changed the icon to a harder to read, but still somewhat serviceable pair of computer monitors alternating between dark and light green.
At least with the linking scheme Ookla is still getting user data / advertising opportunities...
🌻🌻🌻🌻 [google.com]
(Score: 2) by JoeMerchant on Sunday February 22, @04:49PM (2 children)
Via Gemini:
Before Microsoft integrated the modem status icon into Windows 95, a nearly identical "single modem" graphic was popularized by Trumpet Winsock, a legendary third-party TCP/IP stack developed by Peter Tattam.
The Trumpet Winsock Era
The Original Visual: Before Windows had built-in internet support, users on Windows 3.1 relied on Trumpet Winsock to connect to the internet via dial-up. Its status icon was a small, detailed graphic of an external modem.
Dynamic Feedback: Long before the OS did it, this icon featured active "LED" lights that flickered red and green to represent Transmit (TX) and Receive (RX) data. This provided the critical visual confirmation that the handshake was successful and data was moving.
Interface Influence: When Microsoft developed the Dial-Up Networking (DUN) utility for Windows 95, they adopted a very similar single modem icon as the default status indicator in the notification area.
Transition to the Built-In Icon
Windows 95 "Gold": The initial retail release of Windows 95 featured a modem icon in the system tray that was clearly an evolution of the third-party designs used in the early 90s.
Functional Parity: Just like the independent versions, double-clicking the Microsoft icon opened a status window showing connection speed and duration—a workflow pioneered by early shareware dialers.
The Shift to "Two Computers": Microsoft eventually moved away from the single modem graphic in later updates of Windows 95 and Windows 98, replacing it with the two flashing computers icon to symbolize a networked connection rather than just a hardware device.
------
Before Microsoft’s native integration, Trumpet Winsock (developed by Peter Tattam) was the gold standard for connecting Windows 3.1 users to the internet. When Microsoft finally released its own TCP/IP stack (initially codenamed "Wolverine" for Windows for Workgroups 3.11 and then standard in Windows 95), the two coexisted for a brief, competitive era.
Performance & Technical Comparison
32-Bit Architecture: Microsoft’s native stack was built using a 32-bit VxD (Virtual Device Driver) architecture, making it fundamentally faster and more stable than the 16-bit Trumpet Winsock. This allowed the OS to handle network traffic more efficiently without the bottlenecks of the older 16-bit environment.
Operating System Integration: Unlike Trumpet Winsock, which ran as a standalone application that had to be manually launched and minimized, Microsoft's stack was fully integrated into the kernel. This reduced system overhead and prevented the "application crashes" that frequently disconnected third-party dialers.
Hardware Compatibility: Trumpet Winsock was praised for its low hardware requirements; it could run on a 286 processor, whereas Microsoft’s TCP/IP stack for Windows for Workgroups 3.11 required a 386.
Ease of Use: Trumpet Winsock was highly customizable, allowing power users to manually tune settings like MTU (Maximum Transmission Unit) and RWIN (Receive Window) to squeeze better performance out of slow 14.4k or 28.8k modems. Microsoft’s stack prioritized a "plug-and-play" experience, which was easier for average users but initially offered fewer granular optimization options.
The "Wolverine" Advantage: Microsoft's stack allowed for advanced LAN features, such as sharing files and printers over TCP/IP, which Trumpet Winsock did not support as it was primarily designed for point-to-point dial-up (SLIP/PPP).
Ultimately, while Trumpet Winsock was the "best tool" for the early internet, Microsoft’s native 32-bit implementation eventually made it obsolete by providing a more stable, integrated, and slightly faster experience for the Windows 95 era.
🌻🌻🌻🌻 [google.com]
(Score: 3, Insightful) by gawdonblue on Sunday February 22, @08:01PM (1 child)
And was any of that real?
(Score: 2) by JoeMerchant on Sunday February 22, @08:36PM
>And was any of that real?
I don't know if it's real or not, but it aligns with everything I remember from the time - filling in some of the fuzzy spots in my memory with stuff that sounds right to me once I heard it again.
At the time, I certainly didn't appreciate any of the "innovations and improvements" that they're touting for the Microsoft version (who would want to give people direct access to your file system over the wire, anyway?) And I don't remember it being any more stable, or faster either - if anything, less of both when it first got shoved down our throats. But, that's the kind of revisionist history I would expect around a story regarding a well funded surviving corporation.
Other items I remember clearly from the news 20-30 years ago also have evolved into stories more compatible with the big interests - like the time the Miami Dade police helicopter crew thought it was O.K. to stop at Dunkin Donuts on their way back to base - that story has just disappeared altogether, but I absolutely remember it being all over local and national news when it happened. Then there was the guy that Miami International airport security shot dead because he was off his meds and acting crazy. At the time that was released I researched it thoroughly and the stories published within a few months after the event were all focused on "off his meds" "acting irrationally, but harmless." These days if you dig up stories about the event they're all focused on "he repeatedly stated he had a bomb, we had no choice..."
🌻🌻🌻🌻 [google.com]
(Score: 4, Informative) by Runaway1956 on Sunday February 22, @09:50PM
You might have 10 gig fiber, and your connection still sucks. Ookla isn't going to tell you that, and certainly not explain it.
https://bufferbloat.libreqos.com/ [libreqos.com] You won't see blazing fast speeds here, but the tell you whether your connection is solid or not.
https://www.waveform.com/tools/bufferbloat [waveform.com] Much better libreqos, and if you follow their links, you can improve whatever you have.
https://bufferspeed.com/ [bufferspeed.com] This one's not as good, maybe, but it's not bad.
https://www.ipstik.com/internet-stability-test [ipstik.com] Another pretty good one, I haven't followed the links here, but it looks like they might help you improve a crap connection.
Speed isn't the end-all-be-all, you want your internet connection to be lag-free and reliable. Relying on Ookla, or many other speed test sites, you may believe that your crap connection is really great.
We're gonna be able to vacation in Gaza, Cuba, Venezuela, Iran and maybe Minnesota soon. Incredible times.
(Score: 0) by Anonymous Coward on Monday February 23, @02:38AM
It's funny they use the one that lies and overestimates your speeds vs something like fast.com.