LinkedIn Consumes 2.4 GB RAM With Just Two Tabs Open: Web Bloat Continues

The Report

A Hacker News post has highlighted that LinkedIn uses 2.4 GB of RAM with just two tabs open, sparking discussion about web application bloat and the ever-increasing resource demands of modern web apps.

The Evidence

Screenshots shared on HN show:

• Two LinkedIn tabs consuming ~2.4 GB total
• This exceeds the RAM requirements of many full operating systems
• Other heavy web apps like Slack, Teams, and Notion similarly consume hundreds of MB per tab

Why This Matters

Performance Impact

• Battery drain: Heavy JavaScript execution drains laptop batteries faster
• System slowdown: Users with 8 GB RAM machines feel the impact immediately
• Fan noise: Constant CPU/GPU usage from background JavaScript

The Root Cause

Several factors contribute to web bloat:

1. JavaScript frameworks: React, Angular, and Vue applications ship large bundles
2. Real-time features: WebSockets, polling, and live updates require persistent connections
3. Analytics and tracking: Third-party scripts for advertising, analytics, and A/B testing
4. Rich media: Auto-playing videos, infinite scroll with image preloading
5. Feature accumulation: Products add features without removing old ones

The Business Incentive Problem

Companies have little incentive to optimize:

• Faster hardware makes bloat less noticeable for wealthy users
• Developer time is expensive, optimization time is seen as low-priority
• Ship dates matter more than performance budgets
• "Works on my machine" with 32 GB RAM is the new norm

Comparison

For context, here's what 2.4 GB of RAM could run:

• Linux desktop with a full GUI: ~500 MB
• VS Code with extensions: ~300-500 MB
• A video game from 2015: ~2-4 GB
• An entire Android phone: runs on 2-4 GB total

The Broader Trend

Web browsers have become the most resource-hungry applications on modern computers:

• Chrome tabs routinely exceed 500 MB each
• Electron-based apps (Slack, Discord, Teams) are essentially Chrome windows
• The web has replaced native apps but brought worse performance

Possible Solutions

• Aggressive tab management: Close unused tabs, use tab suspenders
• Alternative frontends: Lightweight LinkedIn/web alternatives where available
• Site-specific browsers: Isolate heavy apps in separate browser profiles
• Hardware upgrades: Unfortunately, the most common "solution"

At 17 points on HN, this strikes a nerve with developers tired of the web's resource appetite.