Web Design
How to Optimize Video-Heavy Websites for Performance
A practical checklist for fast video-heavy websites: poster-first loading, reserved space, proper compression, on-screen playback, embed facades, streaming for long films, and measuring on real phones.

For film studios, production houses and agencies, video is the work, so it can’t be cut. It is also, by a long way, the heaviest thing on the page. The goal isn’t less video. It is video that loads in the right order, in the right size, at the right moment. Here is the checklist I use, with examples from production company sites I have built.
1. Decide what each video is for
A short silent loop that sets a mood and a three-minute campaign film are different things and need different handling. Loops can be small, muted MP4s that play inline. Full films belong on a streaming service and should load only when someone asks for them. Write down every video on the site and put it in one of the two groups before optimising anything.
2. Make a poster the first paint
The largest thing visible when the page opens is usually what Google measures as Largest Contentful Paint. If that is a video, the page feels slow. If it is a well-compressed poster image, it feels instant. Give every video a poster, load the hero poster with high priority, and let the video replace it once it is ready.
Be careful with the preload attribute. Use preload="none" or preload="metadata" for anything below the fold, and reserve auto for the one video that must start immediately.
3. Reserve the space before the video loads
If a video container has no height until the file loads, everything below it jumps, which hurts Cumulative Layout Shift and annoys readers. Know each video’s dimensions in advance. On Social Whistles Studio, a build-time script reads every file with ffprobe, records its width, height, aspect ratio and duration, and extracts a poster frame, so each container is sized correctly before a single byte of video arrives.
4. Compress properly
Most video on agency sites is exported straight from the edit at far too high a bitrate for the web. For background loops, a single pass through ffmpeg makes a dramatic difference:
ffmpeg -i input.mov -vf "scale=-2:1080" -c:v libx264 -crf 24 -preset slow -an -movflags +faststart loop-1080.mp4
scale=-2:1080caps the height at 1080 pixels; export a smaller version for phones too.-crf 24balances quality and size; raise it for smaller files.-anstrips the audio track from silent loops.+faststartmoves metadata to the front so playback can begin before the download finishes.
5. Play only what is on screen
Ten autoplaying videos on one page decode at once and drain phone batteries. Use an IntersectionObserver to play each video only while it is visible and pause it when it leaves. On The Third Take, playback is driven by how much of each frame is on screen, so films play when a visitor is actually looking at them.
6. Put embeds behind a facade
A single Vimeo or YouTube embed loads its own player, scripts and fonts before anyone presses play. A facade shows a local poster image with a play button and loads the real player only on click. The Third Take goes a step further: its Vimeo posters are downloaded at build time, trimmed of the black letterbox bars baked into them, resized and served from the site itself, so not even the thumbnails depend on Vimeo’s servers.
7. Stream long films
For anything longer than a loop, use a service that streams adaptively (HLS), such as Vimeo, Mux or Cloudflare Stream. Adaptive streaming sends a smaller version on a slow connection instead of stalling. If you self-host files, keep them on object storage with a CDN rather than on the web server; Social Whistles Studio and Social Spark both serve their video from Cloudflare R2.
8. Respect data and motion preferences
Some visitors ask their device for less: reduced motion, or reduced data usage. Honour both. With prefers-reduced-motion set, show posters instead of autoplaying loops. When the browser signals a data-saver mode, skip background video entirely.
9. Don’t over-compress the stills
Optimisation has a limit for image-makers. The Kaushal Shah portfolio encodes its stills once at visually lossless quality and serves them without recompression, because grain and gradients are what a cinematographer is judged on. Spend the performance budget elsewhere: lazy-load everything below the fold and keep the stills sharp.
10. Measure on real phones
Lighthouse and PageSpeed Insights are useful, but field data matters more. Check Core Web Vitals in Search Console, and test the site yourself on a mid-range phone over mobile data. Watch three numbers: LCP (how fast the main content appears), CLS (how much the layout jumps) and INP (how quickly the page responds to a tap).
The checklist
- Every video is classed as a loop or a film.
- Every video has a poster; the hero poster loads with priority.
- Video dimensions are known and space is reserved.
- Loops are compressed, silent and sized for each screen.
- Videos play only while visible.
- Embeds load behind a facade.
- Long films stream adaptively.
- Reduced motion and data-saver settings are respected.
- Core Web Vitals are checked with field data.
Frequently asked questions
Is it better to self-host video or use Vimeo?
Self-host short loops as compressed MP4s on object storage with a CDN. Use Vimeo or a streaming service for long films, so viewers get adaptive quality.
Does background video hurt SEO?
Not directly, but it can slow the page and hurt Core Web Vitals, which affect user experience. With a poster-first approach, a background loop costs very little.
