Brendan Tully0 Comments
October 7, 2026
A standard YouTube embed is one of the heaviest things you can put on a page. Each one pulls in most of a megabyte of player files before anyone presses play, and a page with several embeds makes the browser work hard enough to spin up a laptop fan. That costs you twice: in the page experience data Google collects from real visitors, and in the visitors who give up on a clunky page before they reach your call to action.
The video compares the main ways to lazy load YouTube embeds: loading the player on scroll, showing a preview image that loads the player on click (by hand or with a plugin), and a code-only srcdoc version, along with where each one falls short.
The player only loads when the visitor scrolls near it, the same way lazy-loaded images work. On platforms without a plugin option, such as Shopify or BigCommerce, adding loading="lazy" to the iframe code does this in most browsers. It helps videos below the fold. It does nothing for a video at the top of a landing page, because that player is in view as soon as the page opens.
loading="lazy"
This is the fastest option, because the page only loads an image with a play icon over it. Most popular themes and page builders have a video widget that supports a preview image. There is a marketing upside too: you choose the image, so you can make it worth clicking. The catch is effort. On a site that already has 50 pages of videos, every widget has to be edited and every preview image found or made.
On WordPress, WP Rocket and FlyingPress can swap embeds for preview thumbnails across the whole site. This works on most sites but not every theme or builder; Divi is one that causes trouble, and Perfmatters handled it in that case. If you use WP Rocket, add its companion plugin for choosing the thumbnail resolution. Without it the previews can look grainy, which is a poor first impression on a page meant to convert.
For sites without a suitable plugin, a short block of code uses the iframe’s srcdoc attribute to show YouTube’s thumbnail and a play symbol, then loads the real player on click. Note one trade-off: most browsers now block autoplay for videos with sound, so visitors may need to click twice. The video’s view is that this is a small price for the speed gain.
Preview-image methods change what is in the HTML when Googlebot fetches the page. If your videos earn visibility in Google’s video results, check the video indexing report in Search Console before and after the change. If the number of indexed video pages drops on pages you care about, add VideoObject structured data to those pages or keep a standard embed on them.
The approach that works best in practice is a combination: use a plugin to fix every page quickly, then rebuild the most important pages with page builder preview images. The homepage comes first because it gets the most traffic. After that, use the landing page report in your analytics to find the pages with the most organic and paid entrances.
One trap: plugin optimisations only apply to pages that are being cached. If campaign landing pages are excluded from the page cache, the plugin will not touch their embeds, so check those pages by hand.
Comments are closed.