To fix a slow Largest Contentful Paint (LCP) in WordPress, find your LCP element, optimize that image or text block, speed up your server with caching and a CDN, and remove code that blocks rendering. Google considers an LCP of 2.5 seconds or less good (web.dev). Start by testing your page with our free website speed test.
Key takeaways
- LCP measures when the largest visible element, usually a hero image or heading, finishes loading.
- A good LCP is 2.5 seconds or less for most visits (Google, web.dev).
- Fix the specific LCP element first, then work on server speed and render-blocking code.
- Never lazy-load the LCP image.
What is LCP in WordPress?
Largest Contentful Paint (LCP) is a Core Web Vitals metric that measures how long it takes for the largest visible element on a page to render. In WordPress, that element is often the featured image, a hero banner, a slider image or a large heading. LCP is the main loading metric Google uses to judge how fast a page feels.
What is a good LCP score?
A good LCP is 2.5 seconds or less. Between 2.5 and 4 seconds needs improvement, and over 4 seconds is poor, according to Google’s Core Web Vitals guidance on web.dev. The result is judged at the 75th percentile of real visits, so most of your visitors need a fast experience, not just some.
How do you find your LCP element?
You find your LCP element by running a speed test and opening the LCP diagnostics. The report names the exact element, such as an image or a text block.
- Run your page through our free page speed checker or Google PageSpeed Insights.
- Open the diagnostics and look for Largest Contentful Paint element.
- Note whether it is an image, a background image or text.
- Check the mobile result first, because the LCP element can differ between mobile and desktop.
What causes a slow LCP?
A slow LCP has four possible parts: slow server response, a late start to loading the LCP resource, a long download time and a delay before the element is rendered. Knowing which part is slow tells you which fix to use.
| LCP part | Typical cause in WordPress | Main fix |
|---|---|---|
| Server response (TTFB) | No caching, slow hosting | Caching, better hosting, CDN |
| Resource load delay | Image found late, lazy-loaded | Remove lazy loading, prioritize the image |
| Resource load time | Large image file | Compress, resize, use WebP |
| Element render delay | Render-blocking CSS and JavaScript | Defer scripts, reduce CSS |
How do you fix LCP in WordPress? 9 fixes
1. Compress and resize the LCP image
Resize the image to the size it is displayed at and compress it before or after upload. An oversized hero image is the most common cause of a slow LCP.
2. Use WebP or AVIF
Modern formats deliver smaller files than JPEG and PNG at similar quality. Many WordPress image plugins can convert and serve them with a fallback.
3. Do not lazy-load the LCP image
Lazy loading delays an image until it is near the viewport. For the top image, that makes LCP worse. Exclude the first image or hero from lazy loading in your optimization plugin settings.
4. Prioritize the LCP image
Add the attribute fetchpriority=”high” to the LCP image so the browser downloads it early. You can also preload it. Do this only for the one LCP image, not for many.
5. Enable page caching
A caching plugin serves a ready-made copy of your page, which lowers server response time and gets the LCP resource moving sooner.
6. Use a CDN
A content delivery network serves your files from a location near each visitor, which cuts download time, especially for international audiences.
7. Defer render-blocking JavaScript and CSS
Scripts and styles in the head can delay the first render. Defer non-critical JavaScript and reduce unused CSS. See our guide on how to eliminate render-blocking resources in WordPress.
8. Reduce server response time
A slow Time to First Byte holds back every other step. Check hosting, plugin load and database queries. Our guide explains what a good TTFB is and how to improve it.
9. Simplify the page above the fold
Sliders, video backgrounds and heavy page-builder sections often become the LCP element and load slowly. Use a single static image or heading at the top of the page instead.
How do you fix LCP in Elementor?
To fix LCP in Elementor, replace sliders with a single image, avoid background videos above the fold, exclude the hero image from lazy loading and keep sections shallow. Elementor adds extra markup and scripts, so a simple top section loads faster. Re-test after each change.
Frequently asked questions
What is a good LCP time?
Google treats 2.5 seconds or less as good. Between 2.5 and 4 seconds needs improvement, and more than 4 seconds is poor.
Why is my LCP slow on mobile only?
Mobile tests simulate a slower network and processor, and the LCP element can be different on a small screen. Check the mobile LCP element separately and optimize that image.
Does LCP affect SEO?
Yes, as one page experience signal among many. Google includes Core Web Vitals in its ranking systems, but relevance and content quality usually matter more.
Can a plugin fix LCP automatically?
Some optimization plugins help with caching, lazy-load exclusions and script deferral, but they cannot fix an oversized image or slow hosting. Use a plugin together with manual fixes.
Is LCP the same as page load time?
No. LCP measures when the largest visible element appears, not when the whole page finishes loading. A page can have a good LCP and still load other resources afterward.
Conclusion
Fixing LCP in WordPress starts with knowing which element is slow and which part of the loading process is causing the delay. Optimize the LCP image, remove lazy loading from it, and speed up your server. For the full list of speed fixes, read our guide on how to improve website speed, then check your result with our free website speed test.
