How web bloat impacts users with slow devices

Original Article ↗ Hacker News Discussion ↗

Perceived causes of web bloat

  • Heavy client-side frameworks, SPA patterns, large JS bundles, and infinite-scroll UIs are blamed for slow, janky sites even on modern hardware.
  • Marketing-driven additions (tag managers, analytics, AB testing, trackers, ads, cookie banners) are cited as major, often unaccounted-for sources of payload and CPU use.
  • “Premature optimization is the root of all evil” is seen as widely misused to justify never optimizing.
  • Some argue hardware improvements and auto-updating browsers made devs complacent about performance and backward compatibility.

Impact on slow devices and bad networks

  • Many report mainstream sites (social media, Substack, Reddit new UI, YouTube, Amazon, airline booking, banking, government) becoming borderline unusable on low-end Androids, older iPads, cheap laptops, and even mid‑2010s Macs.
  • Problems show up not just on weak CPUs but also on constrained data plans and high-latency/low-bandwidth links (rural DSL, train/airline Wi‑Fi, roaming).
  • Infinite scroll, heavy DOMs, and ad scripts cause crashes, stalls, and huge data usage; some users resort to text-mode tools or alt frontends.

Business incentives and “who matters”

  • One view: companies optimize for users with new iPhones and fast connections; poor users on $50 phones “don’t make money,” so supporting them isn’t prioritized.
  • Others counter that this ignores real paying users on older or midrange hardware, in both rich and poor countries, and underestimates global inequality.
  • Some say bloat is rational from a revenue perspective (faster feature shipping, more analytics, “checkbox” features) even if user experience suffers.

Developer culture, tools, and responsibility

  • Debate over whether bloat is mainly due to management/marketing pressure or to developers who don’t understand or value efficiency.
  • Framework ecosystems and DX-first culture make it easy to ship heavy code; cleaning it up later is hard and rarely scheduled.
  • Tracking scripts can be added outside dev control via tag managers, but devs are still seen as having agency to push back or design leaner architectures.

Examples and counterexamples

  • Lightweight sites (HN, simple forums, static blogs, certain email services, some ecommerce like McMaster) are praised as proof that fast, full-featured sites are possible.
  • WordPress with simple themes often outperforms trendy platforms like Medium/Substack.
  • Old-school forums and brutalist/minimal HTML are frequently cited as positive models.

Proposed mitigations and alternatives

  • Recommendations include: semantic HTML + progressive enhancement, server-side rendering, static sites, smaller JS and CSS, pagination instead of naive infinite scroll, and adblocking or DNS blocking.
  • Some suggest systematic “ecological development”: always testing on low-end devices and slow networks, treating regressions as bugs.
  • Others mention remote browsers, Opera‑Mini–style proxies, WASM, and native “recycler” widgets as potential technical directions, though practicality is debated.

Broader concerns

  • Several connect bloat to e‑waste and CO₂ via forced hardware upgrades, though the exact climate impact is contested.
  • There is concern that critical services (government, medical, welfare, education) becoming bloated effectively exclude poorer and less technical users.