Kyle Pflug ran the numbers himself. On an iPhone 17 Pro Max running iOS 26.5.1, a research prototype of Microsoft Edge built on the Blink engine scored 49.27 in Speedometer 3.1. Safari, powered by WebKit, managed 38.3. The gap stands at 28.6 percent.
That single figure, shared in a LinkedIn post on June 15, has stirred fresh debate over browser performance on Apple’s mobile platform. Pflug, group product manager for the Microsoft Edge Web Platform team, stressed the work remains preliminary. Tests came from his personal device. No controlled lab environment. No finished product.
Yet the results extend beyond one benchmark. The same Blink prototype recorded 306.35 on JetStream 3, measuring JavaScript and WebAssembly throughput. WebKit scored 270.9, a 13.1 percent difference according to reporting by MacRumors. In MotionMark 1.3.1, which evaluates canvas graphics rendering, Blink reached 4,773.52 against WebKit’s 4,673.68. A narrower 2.1 percent edge, but consistent.
Pflug took the prototype to an Apple Store. There, Safari on an M5 iPad Pro scored 45.7 in Speedometer 3.1. Still behind the phone-based Blink build. The demonstration carries symbolic weight. Even on premium Apple silicon, WebKit trailed.
These outcomes arrive more than two years after the European Union’s Digital Markets Act pushed Apple to open iOS to alternative browser engines. Apple responded with BrowserEngineKit. The framework lets developers integrate non-WebKit engines. So far, no major browser has shipped one. Technical hurdles, separate app distribution requirements, and user migration challenges have slowed adoption. As noted in coverage from AppleInsider, the prototype builds on Chromium contributions dating to early 2023.
Apple has long required iOS browsers to use WebKit. Third-party apps essentially repackaged Safari with different interfaces. The policy preserved tight integration and security consistency. Critics argue it also capped competition and slowed innovation. Open Web Advocacy, cited by MacRumors, called the restriction a 17-year cost to consumers. The group urged European regulators to press Apple on removing remaining barriers.
Blink’s history adds context. Google forked it from WebKit in 2013 to move faster. The split allowed independent evolution of rendering, JavaScript execution, and multi-process architecture. Alex Russell, then on the Chrome team, argued at the time that iteration speed mattered above all. WebKit’s shared codebase had begun to constrain Chromium’s direction. Over a decade later, Blink powers the vast majority of mobile and desktop browsers worldwide.
WebKit, meanwhile, delivers strong battery life and memory efficiency on Apple hardware. Earlier 2026 tests on M3 and M4 Macs often showed Safari ahead in Speedometer, sometimes by 17 percent or more, per analysis from Tech Insider. Those advantages reflect years of optimization for Apple’s unified memory and custom silicon instructions. The iOS prototype flips the script. It suggests Blink can extract more from the same hardware when freed from WebKit constraints.
Real-world impact remains harder to quantify. Benchmarks like Speedometer simulate web app responsiveness. JetStream stresses computation. MotionMark focuses on graphics. Users rarely notice small percentage gains during casual scrolling or video playback. Network conditions, caching, and site optimization usually dominate perceived speed. Still, developers building complex web experiences care about these margins. So do companies investing in progressive web apps.
The prototype tested additional developer pain points. Items on a “Top Developer Needs” list included improved CSS handling for device notches, automatic height animations via interpolate-size and calc-size, and better JavaScript date-time APIs through Temporal. These features matter for consistent cross-platform development. Pflug presented the benchmark wins as evidence that the prototype offers genuine competition.
But caveats abound. This is research code. Performance could shift under production loads or with full integration. Battery consumption and memory use were not detailed in the initial results. Security and privacy models also differ between engines. Safari’s Intelligent Tracking Prevention and site isolation choices have drawn praise from privacy advocates. Chrome-based browsers face ongoing scrutiny over data collection defaults.
Market realities add another layer. Safari holds dominant share on iOS. Users value system integration, iCloud syncing, and continuity features. Switching browsers requires habit change. Even if a Blink-powered Edge or Chrome launches with superior benchmark scores, adoption may prove slow. Comments on technology forums reflect this split. Some prioritize raw speed and engine diversity. Others favor ecosystem lock-in and perceived efficiency.
WebKit has responded to past competition with steady gains. The collaborative development of Speedometer 3.0 and 3.1, involving engineers from Blink, Gecko, and WebKit teams, aimed to create fairer measurements that reflect modern web workloads. As explained in a 2024 post on the WebKit blog, the benchmark evolved through open governance to reduce bias and improve accuracy. That collaboration continues. Yet the latest iOS numbers suggest WebKit faces pressure to accelerate optimizations for the workloads now measured.
Browser engine diversity has long concerned standards bodies and developers. A web dominated by one engine risks reduced incentive for improvement and potential compatibility regressions. Blink’s market share already exceeds 75 percent globally when counting all Chromium derivatives. WebKit retains significance through iOS. The prototype hints at what full competition might deliver.
Microsoft has not announced plans to release a Blink-based browser on iOS. The work serves as both technical exploration and policy statement. It demonstrates what becomes possible once BrowserEngineKit matures and distribution barriers ease. Regulators in Europe continue to monitor compliance. Further specification proceedings could clarify Apple’s obligations.
For now, the numbers stand. Blink pulled ahead on Apple’s own turf, on Apple’s hardware, using Apple’s framework. The 28.6 percent Speedometer advantage will fuel arguments on both sides of the browser policy debate. Engineers will study the gaps. Teams at Apple, Google, and Microsoft will iterate. And users may eventually gain more choice in how they experience the web on their phones.
WebProNews is an iEntry Publication