What is a good LCP score?

Good: under 2.5 seconds. Needs Improvement: 2.5–4 seconds. Poor: over 4 seconds. Aim for under 2.5 seconds on mobile for a Good score in Google's Core Web Vitals assessment.

What are the most common causes of poor LCP?

The most common causes are: large unoptimised hero images, slow server response time (high TTFB), render-blocking CSS or JavaScript that delays the LCP element from being visible, and lazy-loading applied to above-the-fold images.

How do I improve LCP on a WordPress site?

The most effective WordPress LCP improvements are: install a caching plugin, use a CDN, implement image compression (e.g., ShortPixel, Imagify), disable lazy-loading on the hero image, and switch to a lightweight theme.

Browse tools

Free · Fast · Privacy-first

Check Your LCP Score (Largest Contentful Paint)

Largest Contentful Paint (LCP) is the Core Web Vital that measures how quickly the main content of your page loads. A poor LCP score (over 2.5 seconds) hurts both user experience and Google rankings. FixTools checks your LCP score instantly.

⚡ Use Tool Now How it works

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

⚡

LCP timing measurement

🔒

LCP element identification

✨

Mobile and desktop LCP

Web Tool

Website Speed Test

All processing happens in your browser — your files are never uploaded to any server.

🚀Open Website Speed Test

100% Free · No account · Works on any device

How to use this tool

💡

Enter your URL to measure LCP and identify the specific element causing your Largest Contentful Paint.

How It Works

Step-by-step guide to check your lcp score (largest contentful paint):

1
Enter your page URL
Paste the URL of the page you want to check LCP for.
2
Review the LCP score
Check the LCP time. Good: under 2.5s. Needs Improvement: 2.5–4s. Poor: over 4s.
3
Identify the LCP element
The tool identifies which specific element on your page is triggering the LCP measurement — usually an image, background image, or text block.
4
Optimise the LCP element
Apply the specific fix for that element type: compress/convert images, preload the resource, or remove any JavaScript that delays its rendering.

Real-world examples

Common situations where this approach makes a real difference:

Hero image optimisation

A photographer's portfolio site has an LCP of 7.2 seconds caused by a 4.8MB hero image. Converting to WebP and resizing to 1200px wide reduces LCP to 1.8 seconds and moves the score from Poor to Good.

E-commerce product image

An online shop discovers the LCP element on product pages is the main product image, loading at 3.8 seconds. Adding priority loading, serving WebP, and sizing correctly to the viewport drops LCP to 1.9 seconds.

News article headline

A news site's LCP element is a large text headline loading slowly due to a custom font. Adding font-display: swap and preloading the font file reduces the LCP text render from 3.1 seconds to 0.8 seconds.

When to use this guide

Use this when you need to specifically diagnose and improve your LCP score — especially if your overall performance score is poor and you want to understand the leading cause.

Pro tips

Get better results with these expert suggestions:

Identify the LCP element first

LCP is caused by a specific element on the page — usually a hero image, a large text block, or a background image. The checker identifies which element is the LCP element so you can focus optimisation efforts on exactly that resource.

Preload your LCP image

Add <link rel="preload" as="image" href="your-hero-image.jpg"> in your HTML head to tell the browser to start loading your LCP image as early as possible, before it has parsed the CSS or JS that would normally trigger the load.

Ensure the LCP resource is not blocked by JavaScript

If your LCP element is rendered by JavaScript (e.g., a carousel or lazy-loaded image), the browser cannot paint it until the JS executes. Server-side rendering or eager loading of the LCP element can dramatically reduce LCP time.