YouTube has been cracking down on ad-blockers in recent months, pushing users to either deactivate their ad-blocker on its platform or subscribe to YouTube Premium. Now, the Google-owned platform may have taken things one step further: Firefox users are reporting a noticeable increase in load times on YouTube's desktop website, and it looks like that’s an intentional choice on Google’s part.
Redditor u/vk6_ recently shared a video showing a five-second delay when loading up YouTube on Mozilla's Firefox web browser. For a few seconds, the page remains mostly blank with background elements populating but no videos to be seen. After the brief delay, the page loads up as usual. Other Redditors also ran into the same problem, claiming that YouTube is taking noticeably longer to load on Firefox and Edge, whereas on Chrome, there's no wait time. Annoyingly, the delay doesn't just trigger once, but rather every time a YouTube link is opened, users said.
Upon analyzing the JavaScript files that the YouTube client uses on desktop, one user uncovered code that shows a "timeout" function in the script that forces users to wait five seconds for the page to fully load after checking for the user’s browser of choice. Nothing in the code itself singles out Firefox or Edge in particular, but some users have found that using a filter for this code seems to solve the issue. Others reported that when spoofing the user agent of Firefox to make it appear to be Chrome, YouTube loads up as fast as usual with no five-second delay. Even more curious still, 9to5 Google experimented with the reverse, and found that spoofing Chrome to act as Firefox didn't push this delay into effect.
While the reasoning for the delay remains unclear, some users suggested it may be related to the ad-blocker crackdown. Some posited the code could be a clumsily implemented ad fallback if a user uses an ad blocker, with the relevant code possibly ensuring that an ad is displayed for at least five seconds before the video begins.
So far, Google has not acknowledged the issue. We’ve reached out for comment and will update this article once we hear back.
