If you use Microsoft Edge or Mozilla Firefox to access YouTube to stream videos, read comments, or interact with the site in other ways, you may have noticed that the site is slow as molasses. If you perform the same operations in Chrome or other Chromium-based browsers, performance is blazing fast instead.
A Twitter message by Mozilla's Technical Program Manager Chris Peterson has created heated discussions on Twitter, Reddit, and elsewhere about YouTube's use of a deprecated API that favors Chrome and other Chromium-based browsers over competing browsers such as Microsoft Edge and Firefox.
Peterson stated the following on Twitter:
YouTube page load is 5x slower in Firefox and Edge than in Chrome because YouTube's Polymer redesign relies on the deprecated Shadow DOM v0 API only implemented in Chrome.
YouTube serves a Shadow DOM polyfill to Firefox and Edge that is, unsurprisingly, slower than Chrome's native implementation. On my laptop, initial page load takes 5 seconds with the polyfill vs 1 without. Subsequent page navigation perf is comparable.
YouTube launched a design refresh last year, and one of the changes that Google implemented on the video streaming site was to make use of a deprecated API that only Chrome supported. Use of the API improved YouTube on browsers that support it and made the performance of browsers not supporting the API noticeably worse.
Peterson went on to state that YouTube serves Internet Explorer 11 users with the classic site which does not impact performance, and that Google should have done the same for Firefox, Edge and other affected browsers.
He mentioned a userscript and Firefox add-on that Edge and Firefox users could install to restore access to the classic version of YouTube. Doing so restores the old site and improves performance significantly when these browsers are used to access YouTube.
A thread on Reddit suggests another option that involves using the Developer Tools and modifying a cookie that YouTube set.
Note that since the method is cookie based, it needs to be done again whenever the cookie is deleted. You may also watch YouTube on the desktop to avoid all these issues.
It is pretty clear that YouTube's engineers knew what they were doing when they implemented support for the API. Research of compatibility issues would have pointed them to issues with the implementation in Edge or Firefox. The engineers could have decided to serve the old site to users of Firefox or Edge similar to serving the classic site to Internet Explorer 11 users but they decided against it.
Now You: What is your experience on YouTube?Advertisement
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.