WordPress problem fix
A full video hero has a real LCP ceiling. We pull as close to it as physics allows, honestly, without breaking the visual.
If your WordPress page has a full screen video hero and Largest Contentful Paint will not break below 2.5 seconds no matter what you tune, you are bumping against a physical ceiling. A 2 to 4 MB video file cannot render its first frame in 1.5 seconds on a 4G mobile connection, period. The honest fix is to combine three things: serve a poster image as the actual LCP candidate, lazy load the video itself after the first paint, and compress the video to under 800KB if it stays in the fold. With those three, most video hero pages can hit 2.2 to 2.5 seconds LCP on a real mobile device.
If any of these match, you are on the right page.
PageSpeed Insights shows LCP above 2.5 seconds on mobile
Tuning images, CSS, and JS has stopped moving the LCP score
Video element is detected as the LCP element in field data
Desktop is fine, mobile is the problem
Video bytes are an order of magnitude larger than images. A 3 MB video on a 5 Mbps mobile connection takes nearly 5 seconds just to download enough to render. No amount of code tuning beats that physics.
No. Preloading a 3 MB video makes LCP worse on slow connections, not better, because it competes with other critical assets. Preload the poster image instead.
Sometimes yes. If the video is decorative and not part of the brand promise, a high quality poster image gives a 1.5 second LCP and a better user experience. We test conversion both ways.
The real method, in the order it works.
Add a poster image attribute to the video and make sure it loads before the video file.
Move the video source to load only after the first paint (lazy load with intersection observer).
Compress the video to under 800KB using AV1 or HEVC where supported, fallback to MP4.
Preload only the poster image, never the video file.
Re measure with field data over 28 days, not synthetic Lighthouse, and accept the realistic ceiling.
Real fix, from our work
A US personal brand site insisted on a full screen looping video hero for brand reasons. LCP was stuck at 3.2 seconds on mobile and refused to move. I rebuilt the hero: a high quality poster image became the LCP candidate at 1.8 seconds, the video lazy loaded after first paint, compressed from 4.1 MB to 720 KB. LCP settled at 2.3 seconds in 28 day field data, and CLS stayed under 0.05. The owner kept his video, the site passed Core Web Vitals, and we set realistic expectations on the absolute ceiling.
Written by Ali Yasin Jatoi
Founder of WebCare Studios. Ali has worked with WordPress for more than 10 years, including managing a fleet of 150+ sites with WP-CLI automation for updates, security cleanup, and malware removal. He has hands on experience across major hosts including Cloudways, A2 Hosting, Hostinger, and Bluehost.
Site down, hacked, or broken checkout gets a senior engineer within 4 hours. No ticket queues, no bots.
Flat quote up front. If we cannot get you back online, you do not pay. Risk sits with us, not you.
We work on a snapshot first and never touch your live database until the fix is verified safe.
We run a fleet of WordPress sites every day. The errors you are seeing are ones we have closed hundreds of times.
2.2 to 2.5 seconds on a real mobile device with a compressed video and a poster image. Below 2.0 seconds is rare without removing the video entirely.
No. The Core Web Vitals threshold is 2.5 seconds. Anything under is considered good. Chasing 1.5 seconds with a video hero gives diminishing returns and often forces ugly tradeoffs.
Yes where supported, often 30 to 50 percent smaller files than MP4 at the same quality. We serve AV1 with HEVC and MP4 fallbacks so every browser gets the best version it supports.
Two fields. Email and your URL. A senior WordPress engineer reads it within minutes and replies on email and WhatsApp with what is wrong and what we will do next.