Results of testing prototype Blink vs WebKit on an iPhone 17 Pro Max – Image Credit: Kyle Pflug/Microsoft Edge
WebKit has met its match, as the prototype Blink schools Apple’s well-worn browser engine and hints at the future of web browsing on iOS.
WebKit, Apple’s well-used browser rendering engine, has not had to deal with alternatives for quite some time. Even after the EU’s Digital Markets Act changed the game and forced Apple to allow others to be used on iOS, via BrowserEngineKit.
However, a LinkedIn post from Microsoft Edge Web Platform Group Product Manager Kyle Pflug on June 15 indicates that a change is in progress. All based on a Chromium project using the Blink browser engine that dates back to February 2023.
In the post, Pflug explains that the Edge web platform team has helped contribute to Chromium to create the Blink-based prototype. It’s the same rendering engine that the Edge browser uses on other platforms.
A development build of the prototype browser was tried out against a number of browser benchmarks, and put against Safari. All were based on an average of three runs, all on an iPhone 17 Pro Max running iOS 26.5.1.
In Speedometer 3.1’s Web Responsiveness test, Blink managed a score of 49.27 versus 38.3 for WebKit, a 28.6% difference. For Jetstream 3’s JavaScript and Wasm throughput testing, the gap was narrower at 306.35 for Blink and 270.9 for WebKit.
Lastly, Motionmark 1.3.1’s graphics rendering test of canvas graphics saw a score of 4,773.52 for Blink, 4,673.68 for WebKit. This, too, was a very narrow victory for the Chromium project.
Curious to see how fast it was, Pflug went to an Apple Store to try Speedometer on an M5 iPad Pro running Safari. On that hardware, he still saw a slower score of 45.7.
Each time you open a webpage or click a link, a rendering engine operates quietly behind the scenes, translating code and displaying the webpage within milliseconds. Understanding how these engines work can shed light on why Blink, currently, holds an edge over WebKit.
At the core of Blink is its ability to handle advances in web standards and deliver performance improvements with agility and precision. It’s a fork of the WebCore component of WebKit, re-engineered to embrace rapid advancements in web technology. The decision to create Blink arose because Google aimed to push more aggressive architectural improvements, focusing on speed, security, and ongoing innovation.
Blink’s architecture separates its rendering responsibilities into smaller, more manageable units through a process called “Out-of-Process iframes”. This unique handling contributes significantly to the engine’s efficiency. By isolating each frame or part of a webpage, Blink minimizes the risk of one slow element dragging down the performance of the entire page.
In contrast, WebKit maintains a more integrated approach. Born as a collaborative project between Apple, KDE, and a few other contributors, WebKit has a history of prioritizing stability and broad compatibility. Although it’s the elder statesman in this tale, its development pace must often consider users and use cases that prioritize reliability. Together with Safari’s market presence, WebKit’s adherence to stable evolution sometimes comes at the cost of speed when compared to Blink’s approach.
The choice behind each engine’s developmental focus underscores the philosophy of its steward. Google, with Blink, aims to distill every microsecond of performance into creating the snappiest user experience. Apple’s WebKit, however, aims to blend smooth performance with robustness, ensuring that every user—be it on a new device or an older model—receives a dependable experience.
As an ecosystem, Blink also benefits from its symbiotic relationship with the larger Chromium project. This giant collaborative arena enables developers across various companies and interests to refine and optimize this engine. Whether enhancing JavaScript execution, fine-tuning rendering logic, or innovating around new web technologies, the constant input from a diverse range of experts elevates Blink’s capabilities.
Ultimately, the technological base of both Blink and WebKit isn’t just about today but about architecting tomorrow’s internet. As developers and companies continue to push the limits of digital, how these engines evolve will define the pace and power of future web experiences.
The recent advances in rendering engine technology aren’t just causing ripples for developers and browsers, they’re making waves for end users too. For the everyday user, this means faster, smoother, and more efficient browsing experiences, especially if you’re someone who frequently multitasks between tabs, loves to dive into media-rich websites, or relies on web applications for work and leisure. Nobody likes a slow-loading page or an app that lags just when you need it most. Blink’s superior speed performance can transform these tiny frustrations into seamless, barely noticeable events. It’s as if your browser understands the race against time, eager to keep up with your pace, allowing you to consume content and execute tasks with minimal delay.
For web developers, the performance gap between Blink and WebKit could heavily influence future projects. Developers are often the unsung heroes in this tale, working tirelessly under the hood to create content that is both engaging and efficient. A faster engine opens the door to more dynamic content, complex animations, and interactive experiences without the fear of bogging down users’ machines. It gives developers more room to innovate and push creative boundaries, knowing that Blink can handle the load with elegance and precision.
At the same time, this technological leap prompts a strategic consideration for developers on where to prioritize their efforts. With Blink powering some of the most popular browsers today, optimizing websites and applications for this engine becomes not just beneficial but necessary to reach the widest and most engaged audience. Yet, it’s important not to leave WebKit in the dust; despite the speed differences, Safari remains a staple on iOS devices. Building web experiences that are performant across both engines ensures accessibility and user satisfaction across the board.
Beyond pure performance advantages, the rise of Blink also signals a broader cultural shift towards open collaboration and rapid innovation—principles that align closely with the ethos of many in the tech community. By choosing to invest time and resources into projects compatible with engines like Blink, developers not only stay at the forefront of technology but also contribute to a larger movement towards a more integrated and efficient web ecosystem.
With such powerful tools at their disposal, developers can embrace the challenge of crafting faster, more interactive web experiences. Blink’s capabilities nicely dovetail with community-driven development, encouraging a cycle of improvement and breakthrough. So, while Blink’s current speed superiority is indeed a tool for today, it’s also a promise for the future—a promise that browsing the web can be an intuitive, almost invisible aspect of digital life rather than a bottleneck or hurdle.
As we move forward, the trajectory of browser engines like Blink and WebKit promises an exciting future where innovation is the norm rather than the exception. The competition between these engines is not just about rendering speed; it encapsulates a larger narrative of digital progress and the relentless pursuit of excellence in user experience.
The future of browser engines will continue to be shaped by the demands of a rapidly changing digital landscape. As websites and web applications grow increasingly complex, there is a constant need for engines that can deliver content swiftly without compromising on feature richness or security. Users expect more from their browsing experiences, from flawless video streaming to seamless, interactive applications. Therefore, the evolution of engines like Blink and WebKit will be pivotal in meeting such expectations.
With Blink’s demonstrated prowess in speed and performance, we can anticipate further optimizations that push boundaries even more. The engine may explore innovations such as enhanced support for emerging technologies like Progressive Web Apps (PWAs) and Extended Reality (XR) experiences, revolutionizing how we interact with the web. Moreover, with Google’s resources and commitment behind Blink, we may see progressive enhancements in memory management and energy efficiency, further elevating the web browsing experience on all devices.
On the other side, WebKit is unlikely to rest on its laurels. Apple engineers have consistently shown a commitment to innovation balanced with stability. As Safari remains a central part of the Apple ecosystem, WebKit is poised to integrate deeply into Apple’s broader emphasis on privacy and security. Expect WebKit’s future to be characterized by cutting-edge security features, and possibly, breakthrough technologies that take advantage of Apple’s hardware, such as native support functionalities and improved synergy between iOS applications and browser windows.
Further, we are likely to witness expanded opportunities for collaboration between companies that seek to merge the strengths of Blink and WebKit. This could form a broader trend of hybridizing technology to take advantage of the best aspects from each engine. It’s a thrilling prospect for developers eager to leverage robust tools to craft superior web experiences. By pooling resources and ideas, tech companies might very well unlock new heights of browser capability, propelling the internet into an era defined by unprecedented access and performance.
The horizon for browser engines, therefore, is bright and full of promise. As users, we can look forward to a period of incredible innovation that will make our digital journeys faster, safer, and more enjoyable. For developers, there is a unique opportunity to be part of this evolution, to harness the cutting-edge tools at their disposal, and to push the boundaries of what’s possible on the web. As technology continues to advance, both in terms of capabilities and accessibility, the future of web browsing becomes a canvas upon which limitless potential can be painted, one keystroke at a time. For related coverage, see our SecureROM vulnerability in Apple devices.
