Google is finalizing a new technical feature for Chrome 148 promises to change how videos and audio load on the webThe browser will intelligently delay the download of these multimedia resources until they are actually needed, with the aim of improving page performance and reducing data consumption, especially on mobile connections.
The idea isn't entirely new: since 2019, Chrome and other Chromium-based browsers have been implementing lazy loading of images and iframesWhat is now being put on the table is extending that same logic to the elements y which are usually much heavier and have a greater impact on the initial loading speed.
What is deferred loading and how will it apply to video and audio?
La lazy loading It is a technique that consists of Defer the download and initialization of certain resources until the user scrolls close to themInstead of bringing everything up at once when the page opens, the browser focuses first on the visible content and leaves what is off-screen for later.
In practice, when a website includes video or audio far below the first screen, the browser, with this new feature, It will not start downloading or preparing it immediately.It will wait until the user moves a certain distance from that resource before starting the load. This avoids unnecessary downloads of media that may never be viewed or played.
Until now, many developers relied on Custom solutions in JavaScript, combining tools like Intersection Observer with dynamic attribute loading srcIt was a valid way to achieve a similar effect, but it added complexity to the code and didn't integrate as well with the browser engine's internal optimizations.
With the new implementation, Chrome will allow use the attribute directly loading=»lazy» in video and audio tagsJust like with images and some other elements. That will be the clue the browser uses to decide which multimedia resources can be deferred and when to retrieve them.
According to the information gathered in the platform's roadmap, Chromium began working on this capability at the beginning of the yearThe feature has already passed several internal implementation phases. The goal is to refine both its visual behavior and its interaction with the rest of the browser's loading system.
What changes in Chrome 148 and other Chromium-based browsers
The new feature will be activated natively in Chrome 148This applies to both computers and mobile devices, as well as to WebView, the container many apps use to display web content. According to Google's documentation, The feature is already being tested in development branches such as Chrome 147 and its stable release is planned for one of the next versions, with a gradual rollout that could be completed around mid-April, always subject to change.
By integrating directly into the Chromium code, the improvement It won't be limited to Google Chrome.Browsers that share the same base, such as Microsoft Edge, Brave, Opera or VivaldiThey will also be able to take advantage of this optimization when they upgrade to versions that include the new lazy loading behavior for media.
It should be noted that Not all multimedia content will be affected in the same way.Typical YouTube videos embedded using an iframe have long benefited from native lazy loading for iframes in Chromium-based browsers, so in those cases the change will be less noticeable. The impact will be greater on websites that directly use tags y suitable for reproducing content.
Google also points out that the Native lazy loading for video and audio will take into account other attributes such as autoplay y preloadIn other words, the browser will try to balance resource conservation with the behavior the developer expected for each player, minimizing surprises in the user experience.
Another key point is that the system will prevent blocking the event window.onload with multimedia resources that are outside the visible areaOn sites loaded with clips, embedded players, or audio tracks, this can make a difference in how fast the page feels when it loads.
Impact on loading speed, mobile data, and RAM
The practical effect of this improvement is most noticeable in pages with many multimedia elements spread throughout the contentInstead of trying to download all those files at once as soon as you enter, the browser can focus on the text, initial images, and essential resources, leaving the rest for later.
That translates into shorter initial load times, less bandwidth consumption, and less strain on RAMThis is especially relevant for mobile phones with limited resources or data plans with monthly allowances. Many users in Spain and the rest of Europe still browse the internet with tight budgets or in areas with unreliable coverage, so every unnecessary download avoided is a small relief.
In terms of experience, the user perceives that The page responds faster and you can start reading without the browser freezing while loading videos in the background.Although you may not see any visible changes in the interface or receive a notification about the new feature, you will notice that certain heavy websites feel somewhat more responsive.
Google also points out that the Native implementation allows for optimized loading based on network statusThe browser engine can decide on different thresholds depending on whether the connection is fast or slow, or if it detects many ongoing requests. This is difficult to replicate with external scripts, which do not have the same access to the internal information of the loading process.
By reducing downloads of items that the user may never see, an additional benefit is obtained. more efficient use of cache and rendering pipelineIn the long run, these are details that contribute to a smoother navigation experience, even if the improvement isn't noticeably dramatic from page to page.
What does this mean for web developers and the Chromium ecosystem?
From the perspective of those who build websites, the arrival of this new feature implies a significant simplification in the way multimedia resources are managedUntil now, those who wanted to control in detail when a video or audio was loaded had to resort almost exclusively to JavaScript, with additional logic to detect the position on the screen.
With the new API, simply adding the attribute will suffice loading=»lazy» in tags y Just as it already does with images. The browser will automatically handle the rest, applying its own heuristics to decide when to start the download without disrupting the user experience.
This has several advantages: it reduces the amount of custom code, Possible errors in the loading logic are minimized and dependencies on external libraries solely for managing player behavior are avoided. Furthermore, the browser can better coordinate this load with its system. preload and with the resource scanner that runs before rendering the page.
The proposal to incorporate native lazy loading for video and audio has been driven by active contributors to the Chromium projectwho have been working on performance optimizations of this type for some time. The specification is being refined within the usual working groups and, although it can still be polished, Google is already presenting it as a a logical extension of the lazy loading APIs that developers have known for years.
As with almost everything integrated into the Chromium engine, the change will ultimately benefit a wide range of browsersAnd not just in Chrome. In the European context, where more and more users are switching between options like Edge, Brave, Opera, or Vivaldi, these kinds of shared improvements reinforce the feeling that a large part of the web is moving at the same technical pace.
In the end, it's all about one of those silent updates that don't change the appearance of the browserBut these improvements can shave seconds (or at least reduce friction) off your daily routine, especially on sites overloaded with multimedia content. And in an environment where many pages compete for the user's attention, any advancement that makes the experience faster and less cumbersome is quite valuable.
With the arrival of native lazy loading for videos and audio in Chrome 148, the browser reinforces its role as a benchmark for performance within the web ecosystem: page opening speed is improved, data and memory usage is reduced, and the work of developers is simplified, while the rest of the Chromium-based browsers in Spain and Europe prepare to inherit an optimization that, without making headlines, can make daily browsing a little more bearable.