Modern browsers must handle user input, request remote files, run various callbacks, and ultimately render to the screen, all while staying fast and responsive. That requires a unified task abstraction to keep track of the browser’s pending work. Moreover, browser work must be split across multiple CPU threads, with different threads running tasks in parallel to maximize responsiveness.
Running Interactive Scripts | Web Browser Engineering
The first web applications were like the previous chapter’s guest book, with the server generating new web pages for every user action. But in the early 2000s, JavaScript-enhanced web applications, which can update pages dynamically and respond immediately to user actions, took their place. Let’s add support for this key web technology to our browser.
Now THAT’S What I Call Service Worker!
If you’re looking to achieve the single-page app level performance without the overhead (and boot time) of a huge JavaScript library or having to completely rewrite your website in a new technology…
Run Workers for up to 5 minutes of CPU-time
Workers now support up to 5 minutes of CPU time per request. Allowing more CPU-intensive workloads.
Building the DOM faster: speculative parsing, async, defer and preload – Mozilla Hacks - the Web developer blog
In 2017, the toolbox for making sure your web page loads fast includes everything from minification and asset optimization to caching, CDNs, code splitting and tree shaking. Understanding what goes ...
Multi-process Firefox brings 400-700% improvement in responsiveness | TechCrunch
Earlier this summer I wrote about Mozilla's efforts to rollout a multi-process architecture, codename Electrolysis, for Firefox. In the months since,
Reorganizing Website Architecture for HTTP/2 and Beyond
This document discusses reorganizing website architecture for HTTP/2 and beyond. It summarizes some issues with HTTP/2 including errors in prioritization where some browsers fail to specify resource priority properly. It also discusses the problem of TCP head-of-line blocking where pending data in TCP buffers can delay higher priority resources. The document proposes solutions to these issues such as prioritizing resources on the server-side and writing only what can be sent immediately to avoid buffer blocking. It also examines the mixed success of HTTP/2 push and argues the server should not push already cached resources. - Download as a PDF or view online for free
Stop Ignoring the Browser: The Biggest Frontend Shift in a Decade
Native browser APIs now provide powerful alternatives for routing, state management, and components. Never mind the frameworks, use the browser.
Sending Information to Servers | Web Browser Engineering
So far, our browser has seen the web as read-only—but when you post on Facebook, fill out a survey, or search Google, you’re sending information to servers as well as receiving information from them. In this chapter, we’ll start to transform our browser into a platform for web applications by building out support for HTML forms, the simplest way for a browser to send information to a server.
Turbocharging Web Apps: Efficient AI Model Caching in Chrome
Lightpanda | The headless browser
The AI-native web browser built from scratch for machines. Not a fork. Not a patch. Fast, scalable web automation with a minimal memory footprint. 10x faster, 10x less RAM, and 100x better than Chrome headless.
3W for In-Browser AI: WebLLM + WASM + WebWorkers
What if AI agents could run entirely in your browser? Not just the UI part—the actual model inference, agent logic, and response generation, all happening locally without a single API call.
Web Engines Hackfest 2025
A Quantum Leap for the Web
Over the past year, our top priority for Firefox was the Electrolysis project to deliver a multi-process browsing experience to users…