Browser Timeline: Five Years of Speed Gains, Memory Bloat, and Default HTTPS
Archi4 min read
Contents
- 2021: The Year Defaults Moved
- Memory: The Quiet Regression
- 2022: Extensions Get a New Engine
- The Performance Race Slows
- 2023: Passwordless and Passkeys
- Tab Management Becomes a Feature
- 2024: The Cookie Deadline Slips
- AI Enters the Address Bar
- 2025: Default HTTPS and Encrypted DNS Everywhere
- What Changed Since 2020
- What to Watch Next
2021: The Year Defaults Moved#
In early 2021, the biggest browser story was not a new feature. It was a setting change. Chrome 90 made HTTPS the default for typed addresses. Firefox and Safari had already leaned this way, but the scale of Chrome moved the baseline. Within months, plain HTTP sites became the exception on the open web. The change felt invisible to most users. For site owners, it forced a choice: buy a certificate or watch the padlock warning appear.
That same year, cookie policies started to tighten. Safari and Firefox blocked third-party cookies by default. Chrome announced a longer path. The result was a split web: one experience for users on Safari, another for those on Chrome. Ad tech firms spent the year rewriting scripts.
Five years ago, browser competition was mostly about speed scores. By the end of 2021, it was about privacy defaults. That shift set the tone for everything that followed.
Memory: The Quiet Regression#
Chromium-based browsers kept adding processes. Each tab, each extension, each site isolation boundary took memory. It made the browser more secure. It also made 8GB laptops feel old. By late 2021, users on forums were posting screenshots of browsers using 3GB of RAM with a dozen tabs open. The tradeoff was real, and it has not gone away.
2022: Extensions Get a New Engine#
Manifest V3 arrived in Chrome in 2022. The change replaced background pages with service workers. Extension developers had to rewrite code. Ad blockers and privacy tools were hit hardest. Some shipped lite versions. Others told users to switch browsers.
Firefox and Safari declined to adopt the same model. That divergence mattered. For the first time in years, extension compatibility became a reason to pick a browser. Users who relied on content blockers had a concrete reason to leave Chrome.
The Performance Race Slows#
The annual JavaScript benchmark gains that defined 2015 to 2020 got smaller. Chrome, Firefox, and Safari all landed within a few percent of each other on common tests. Speed stopped being the main selling point. Stability, battery use, and memory took its place.
2023: Passwordless and Passkeys#
Passkeys moved from demo to default. Google, Apple, and Microsoft shipped support across their browsers and operating systems. By mid-2023, signing in with a fingerprint or face scan worked on major sites. The old password manager model started to look dated.
Adoption was uneven. Enterprise identity providers moved slowly. Consumers who used passkeys found them faster. Those who did not kept typing passwords. Five years earlier, two-factor authentication was the big security push. Passkeys changed the shape of that conversation.
Tab Management Becomes a Feature#
Browsers shipped vertical tabs, tab groups, and sleeping tabs. Memory-saving features became standard. Edge and Chrome added tab suspension. Safari pushed profiles. The browser started to look more like an operating system shell.
2024: The Cookie Deadline Slips#
Chrome's plan to remove third-party cookies slipped again. The company delayed, then announced a choice-based model. Regulators in the UK scrutinized the plan. Advertisers and publishers argued over what counted as consent. The deadline moved to 2025, then changed shape again.
This was the clearest break from five years earlier. In 2019, the industry expected a clean removal. By 2024, the reality was a patchwork of regional rules and browser defaults. Developers who built for one model had to support three.
AI Enters the Address Bar#
Sidebar assistants and page summarizers arrived in Edge, Chrome, and Arc. Most ran on cloud models. Privacy advocates raised questions about what got sent and when. The features were useful for some tasks and noisy for others. None of them changed browsing for people who ignored them.
2025: Default HTTPS and Encrypted DNS Everywhere#
Encrypted DNS became common by default. Chrome, Firefox, and Edge all enabled DNS over HTTPS for most users. Internet providers lost visibility into domain lookups. Network administrators pushed back, and some enterprises turned it off. For home users, the change was silent.
Default HTTPS reached near-total coverage. Browsers now warn loudly on plain HTTP forms. The progress since 2021 is easy to measure: certificate issuance is cheaper, and the padlock is standard. The cost is that small sites on shared hosting sometimes break.
What Changed Since 2020#
Five years ago, the browser was a window to the web. Today it is a gatekeeper. It decides which cookies work, which extensions run, which DNS resolver answers, and whether a site loads over a secure connection. That concentration of decisions is the biggest shift of the period.
Speed gains since 2020 are modest. Memory use is worse. Privacy defaults are stronger. Extension power is weaker in Chromium browsers. The web is more secure and less open at the same time.
What to Watch Next#
The next fights are already visible. Browser makers are testing local AI models that run on the device. Regulators are asking whether a browser can favor its own services. And the cookie question remains unresolved in several markets. The timeline from 2021 to 2026 shows a pattern: defaults change slowly, then all at once, and the people who notice last are usually the ones running the sites.
More articles