Methodology: This check follows wSEO methodology 1.0. How the assessment works

Poster before intent, working video afterwards

How to audit deferred video loading

Record Network before scroll and click, then press Play once. A good facade makes no early provider requests, preserves layout and becomes an accessible working player.

Comparing network requests before and after pressing Play on a video facade
Evidence includes both states of the same page.

Browser check

  1. Open the page in a clean window, DevTools → Network, enable Disable cache and Preserve log.
  2. Reload without scrolling. Filter the video provider's domain, Media, JS and iframe.
  3. For click-to-load, expect zero player/video-provider requests before action. A local poster may load.
  4. Scroll to the block without clicking and record whether a near-viewport strategy loads its iframe as intended.
  5. Press Play once: requests should begin, layout should remain stable, and playback should start or show a clear ready state.
  6. Repeat with keyboard, mobile and throttled network; inspect Console, focus, captions, consent and analytics events.

Issue levels

How to rate lazy video
ObservationLevelAction
Only poster before click; first click starts stable playerNo issueSave HAR and test recording
Offscreen iframe loads near viewportAcceptableCompare with click-to-load requirement
Player and third-party JS load immediately without needHighAdd facade or preload none
First click lost, focus/controls absent or consent brokenCriticalRoll back and repair interaction

Technical inventory

[...document.querySelectorAll('video, iframe')].map(el => ({
  tag: el.tagName,
  src: el.currentSrc || el.src,
  loading: el.loading,
  preload: el.preload,
  size: [el.clientWidth, el.clientHeight],
  title: el.title
}))

This lists rendered video/iframe elements, but a pre-click facade may intentionally contain neither. Combine DOM inventory with Network evidence and button testing.

False conclusions and scope

  • loading="lazy" on an iframe means near-viewport loading, not necessarily waiting for click.
  • preload="none" is a browser hint; assess poster and support requests separately.
  • Service worker, cache and an already-open player can hide requests; use a clean profile.
  • Consent may correctly block a provider beforehand; test both states.
  • No initial requests does not prove accessibility, captions or successful playback.

Automated pricing applies to agreed templates and players on the service page. Use the step-by-step guide for repairs.