
The short answer
A homepage video is worth it when motion shows something a photo can't and the page still loads fast. Use a short, muted background loop with a light poster image, a visible pause button and a reduced-motion fallback, or put the full brand film behind a play button. Never autoplay sound or a heavy file.
Your homepage should have a video if it shows something a still photo can't, and if it is built so the page still loads fast on a phone. That usually means one of two things: a short, silent background loop that sets the mood, or a full brand film that plays only when a visitor clicks. Big Wave Productions, a national photo and video production company headquartered in Orlando, plans both before the shoot, and the web build matters as much as the footage.
Background loop or play-on-click film
| Background loop | Play-on-click film | |
|---|---|---|
| Job | Sets the mood behind the headline | Tells the story to someone who chose to watch |
| Sound | None, with the audio track removed | Yes, with captions |
| Length | Roughly 10 to 30 seconds, looping | Usually one to three minutes |
| Starts | Automatically, muted | When the visitor presses play |
| Loads | With the page, so it must be light | After the click, so it can be full quality |
| Must have | Poster image, pause button, reduced-motion fallback | Captions, a clear thumbnail, a play button people notice |
Many strong homepages use both: a loop in the hero and a "Watch the film" button that opens the full version. Our post on how long a brand video should be covers running times for each.
When a homepage video earns its place
Video is worth its weight when movement is the point. A marina at sunrise, a resort pool, a production line, a packed conference hall or a busy branch lobby all read better moving than frozen. When the offer is mostly words, such as a law firm or software with nothing visual to show, a strong photograph and a sharp headline often do more.
Signs the video is doing its job:
- It shows your real people, places or product, not stock footage any competitor could buy.
- The headline and the main button still make sense with the video paused.
- Nothing important exists only inside the footage. Search engines and screen readers read your text, not your video.
- It looks intentional on a phone, not like a wide shot squeezed into a tall frame.
How a homepage video affects Core Web Vitals
Core Web Vitals are Google's three page experience metrics: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness, and Cumulative Layout Shift (CLS) for visual stability. According to web.dev, a good LCP is 2.5 seconds or less, a good INP is 200 milliseconds or less and a good CLS is 0.1 or less, measured at the 75th percentile of page loads. Google Search Central recommends that site owners achieve good Core Web Vitals for success in Search.
A hero video is often the largest thing on screen, which makes it the likely LCP element. web.dev's LCP guide confirms that video elements count, and that LCP uses whichever comes first: the poster image loading or the first video frame appearing. An LCP above 4 seconds is rated poor.
That gives you three rules for the hero:
- Always set a poster image. Use a compressed still of the first frame, so the hero renders quickly while the video loads behind it. web.dev's guide to lazy loading video also suggests preloading that poster with
fetchpriority="high"when the video is an LCP candidate. - Don't lazy-load it. The same guide says videos that are LCP elements shouldn't use
loading="lazy", just as LCP images shouldn't. - Reserve the space. web.dev's CLS guide says to include width and height attributes on images and video elements, or to reserve the space with CSS
aspect-ratio. Otherwise the layout jumps when the video arrives.
Videos lower on the page are the opposite case. web.dev recommends preload="none" with a poster for videos that don't autoplay, and loading="lazy" where browsers support it, so nothing downloads until a visitor scrolls near it.
File size, format and encoding
File size is bitrate multiplied by duration. A 15-second loop encoded at 2 megabits per second is 30 megabits, about 3.75 megabytes, before a single image or font has loaded. Halve the length or the bitrate and you halve the file. That arithmetic is why a background loop should be short and calm.
A sensible starting spec for a background loop:
- Container and codec. MP4 with H.264 (AVC) is the most compatible choice. MDN's web video codec guide describes MP4 with AVC and AAC as supported by every major browser. You can list a WebM file encoded with AV1 first and fall back to the MP4.
- No audio track. A muted loop doesn't need one, and removing it saves bytes.
- Resolution. 1080p is usually plenty for footage that sits under an overlay and a headline. Serve a lighter file, or just the poster, to small screens.
- Attributes.
autoplay muted loop playsinline. web.dev notes thatplaysinlineis necessary for autoplay on iOS. - Calm footage. Slow camera moves and steady scenes compress far better than fast cuts, handheld shake or busy crowds.
Chrome's autoplay policy always allows muted autoplay but holds back autoplay with sound until the visitor has interacted with the site or met other conditions. Plan for the loop to be muted every time.
Designing the loop itself
A good loop is shot on purpose, not trimmed from leftovers. We shoot with the final edit in mind, so when a homepage is on the deliverables list, the loop gets its own shots:
- Hold the frame. Locked-off or slow-moving shots. The loop runs behind text, so the movement should be felt, not watched.
- Leave room for the headline. Plan open space where the text will sit, usually the left side or the center.
- Protect the center for phones. A wide frame cropped to fill a tall phone screen loses its edges, so keep the subject near the middle. Our guide to vertical, horizontal and square video explains framing for several shapes at once.
- Hide the loop point. End on a frame that matches the first one, or use a slow dissolve, so the jump back isn't noticeable.
- Keep text out of the video. Put the headline in live HTML. It stays sharp, search engines and screen readers can read it, and you can edit it without exporting a new file.
- Watch the contrast. Text over moving footage changes contrast frame by frame. WCAG's contrast minimum, a Level AA criterion, asks for at least 4.5:1 for normal text and 3:1 for large text, so most loops need a dark overlay behind the words.
Accessibility: pause, sound and motion
Moving content needs a way to stop. WCAG success criterion 2.2.2 Pause, Stop, Hide, a Level A requirement, says that moving content which starts automatically, lasts more than five seconds and appears alongside other content needs a mechanism to pause, stop or hide it. A looping hero video fits that description, so give it a visible pause button that keyboard users can reach.
If you embed through Vimeo, its background mode turns off all player controls, including play and pause. Your developer will need to add a pause control of their own.
Sound should never start on its own. WCAG 1.4.2 Audio Control requires a way to pause or stop audio that plays automatically for more than three seconds, or to set its volume separately from the system volume. The simplest answer is a loop with no audio at all.
Respect reduced motion. Some visitors set their operating system to minimize animation, and web.dev's guide to prefers-reduced-motion lists holding back autoplaying videos as one use of that setting. When it is on, show the poster image instead of the loop.
Caption the full film. WCAG 1.2.2 Captions (Prerecorded) is also Level A. Our guide to captions and accessibility for bank video covers caption files and burned-in captions.
Where to host a homepage video
| Option | Good for | Watch out for |
|---|---|---|
| Self-hosted file on your site or CDN | Background loops, with full control of the file and the markup | You handle compression, phone versions and the pause button |
| Vimeo embed | Play-on-click films in a clean player, and loops through background mode | Background mode hides every control |
| YouTube embed | Films you also want people to find on YouTube | A heavy player for a homepage, and built for watching rather than backgrounds |
| Streaming video platform | Long films, large libraries, adaptive quality on slow connections | One more account and one more script on your page |
For any third-party player, consider a facade: a lightweight image that looks like the player and loads the real one only when someone clicks. Chrome's Lighthouse documentation on facades gives a YouTube example in which a facade of about 3 KB stands in for a player of about 540 KB until the visitor interacts.
A note for banks and financial institutions
Bank homepages carry one more constraint. Under the FDIC's digital sign rule, 12 CFR 328.5, an insured bank's homepage has to display the FDIC official digital sign clearly, continuously and conspicuously. Design the hero so the video and its overlay never cover or crowd it. Our bank video compliance checklist covers it, including the FDIC's compliance dates, and your compliance team has the final word.
A pre-launch checklist
- Poster image set, compressed and shown first
- Loop around 30 seconds or shorter, with no audio track,
mutedandplaysinlineset - Width and height (or
aspect-ratio) set, so nothing shifts - Visible pause button that works with a keyboard
- Poster shown instead of the loop when reduced motion is on
- Headline in live text, readable over every frame
- Lighter file or poster for phones
- LCP checked in PageSpeed Insights on mobile, before and after the video goes in
Plan the loop on the same shoot as the film
The cheapest time to get a homepage video right is before the cameras roll. Tell us where the video will live and we will build the hero loop, the full film and the social cuts into one production plan. See our brand films page, then book a free discovery call or call or text the office at 407.498.5980.
Sources
- web.dev, Web Vitals.
- web.dev, Largest Contentful Paint (LCP).
- web.dev, Optimize Cumulative Layout Shift.
- web.dev, Lazy loading video.
- web.dev, prefers-reduced-motion: Sometimes less movement is more.
- Google Search Central, Understanding Core Web Vitals and Google search results.
- W3C, Understanding WCAG 2.2: Success Criterion 2.2.2 Pause, Stop, Hide, 1.4.2 Audio Control, 1.4.3 Contrast (Minimum) and 1.2.2 Captions (Prerecorded).
- Chrome for Developers, Autoplay policy in Chrome.
- Chrome for Developers, Lazy load third-party resources with facades.
- MDN Web Docs, Web video codec guide.
- Vimeo Help Center, About embedding background and Chromeless videos.
- Electronic Code of Federal Regulations, 12 CFR 328.5, Signs for digital deposit-taking channels.




