YouTube slows down video load times when using Firefox

Original Article ↗ Hacker News Discussion ↗

Reports that YouTube pages load several seconds slower in Firefox have prompted claims that Google is degrading the experience for non‑Chrome users, potentially to punish ad blockers or push people toward its own browser. Code snippets circulating online show a hard‑coded 5‑second timeout in YouTube’s JavaScript, though some argue it’s part of an ad‑block detection experiment that can also affect Chrome and may not be explicitly anti‑Firefox. The episode feeds into wider concerns about Google’s dominance over browsers, web standards, and online video, with many calling for antitrust action and advocating alternative frontends or tools to access YouTube content.

Reported behavior & evidence

  • Multiple users report a new ~5s delay before YouTube videos start, originally noticed in Firefox but also in Chrome, Brave, Vivaldi, and others; some can’t reproduce it at all.
  • A minified snippet was highlighted: setTimeout(function(){ c(); a.resolve(1) }, 5E3).
  • A fuller code context shows:
    • A small WebM video is injected as an “ad” element.
    • If its ontimeupdate fires within ~3s, one code path runs.
    • If not, after 5s the timeout fires and resolves with a different value, effectively detecting adblocker / failure.

Is it Firefox-targeting, adblock-targeting, or a bug?

  • Some report the delay disappearing when spoofing a Chrome user agent, suggesting UA-based behavior.
  • Others see the same code and no delay in both Firefox and Chrome, or only on specific profiles, making rollout and targeting unclear.
  • A later “debunk” in the thread frames it as part of anti-adblock experiments that can trigger on Chrome too, not specifically Firefox.
  • Several participants stress that Google runs many A/B tests, so behavior may differ by user, region, login state, or adblock status.

Technical interpretations

  • Some initially interpret the 5s timer as a crude, intentional slowdown; others argue it’s a detection timeout / fallback for ad-loading, not the primary blocker.
  • There’s debate over whether such an obvious client-side delay would ever pass YouTube’s code review unless its impact was known and intended.
  • A minority suggest it could be a leftover debug/workaround, but others call that implausible at YouTube scale.

User experience & workarounds

  • Many attribute recent weirdness (delays, playback glitches, auto-pauses) to the YouTube–adblock “arms race”; uBlock Origin filter updates often restore normal behavior.
  • Common workarounds: spoofing Chrome UA, alternative frontends (Invidious, Piped, NewPipe, SmartTube), yt-dlp + mpv/VLC, or paying for Premium.
  • Some use the delay as friction to curb mindless watching and view it as an accidental “feature.”

Competition, antitrust, and browser ecosystem

  • Strong concern that this fits a pattern of Google under-testing or degrading non-Chromium browsers, especially Firefox, and steering users to Chrome.
  • Comparisons are made to IE6-era behavior; Chrome/Chromium dominance plus Google’s role in ads, web standards, Android, and major sites is seen as dangerous concentration of power.
  • Several call for EU/UK or US antitrust action and even structural separation of YouTube, Chrome, and Search; others worry YouTube might not be viable without Google cross-subsidies.