Free LCP Tester & Analyzer

Largest Contentful Paint measures how long it takes for the largest visible element (usually a hero image or heading) to load.

Under 2.5 seconds is Good. 2.5–4.0s needs improvement. Over 4.0s is Poor.

Yes, completely free.

Absolutely. The LCP Tester & Analyzer processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the LCP Tester & Analyzer is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the LCP Tester & Analyzer in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Yes, the LCP Tester & Analyzer is built following current Google Search guidelines and best practices. We regularly update the tool to reflect changes in search engine requirements.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The LCP Tester & Analyzer works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

The two numbers measure different things. This tester reads the live largest-contentful-paint timing from your own browser using the PerformanceObserver API, so the result reflects your exact device, network speed, and cache state at that moment. PageSpeed Insights reports two figures instead: a lab score from a simulated mid-tier device, and field data (CrUX) showing the 75th-percentile LCP of real Chrome users over the trailing 28 days. Your fast laptop on fibre will almost always post a lower LCP than the throttled lab test or the real-world field average. That is expected, not a bug. Use the in-browser reading for a quick sanity check, but treat the PageSpeed field number as the score Google acts on. Paste that field value into the analyzer here to get an instant Good, Needs Improvement, or Poor rating.

LCP records the render time of the single largest content element visible in the viewport when the page first loads. In practice that is most often a hero image, a background image set in CSS, a video poster frame, or a large block of heading or paragraph text. The browser tracks candidates as the page paints and reports the biggest one, which can change as resources arrive. Elements scrolled below the fold do not count, and neither do the dimensions of an element that has not yet loaded its image. Knowing which element is your LCP tells you exactly what to optimize first, since shaving time off that one resource moves the score directly. Run this page through the tester to see a real measured LCP, then identify the matching hero element on the page you want to improve.

First Contentful Paint (FCP) marks the moment the browser renders the very first piece of content, such as text, an icon, or background colour. Largest Contentful Paint marks when the largest visible element finishes rendering, which almost always happens later. FCP tells you the page has started to appear; LCP tells you the main content the user came for is actually on screen. That is why LCP, not FCP, is one of the three Core Web Vitals Google uses in its page experience signals. A site can show a fast FCP but still feel slow if a heavy hero image pushes LCP past 2.5 seconds. Focus your tuning on the LCP element for ranking impact. Enter your LCP value from PageSpeed Insights or DevTools into this analyzer to check it against Google's official 2.5-second threshold.

Hero images are the most common reason LCP creeps over 2.5 seconds, and a few changes usually fix it. Compress the image and serve a modern format like WebP or AVIF to cut its file size, and set explicit width and height attributes so the browser can paint it without waiting. Never apply loading="lazy" to the above-the-fold hero, since that intentionally delays the very element LCP measures. Add a <link rel="preload"> for the image so the download starts earlier in the page lifecycle, and serve it from a CDN to shorten the trip to the user. Finally, keep your server's TTFB under 600ms with caching, because a slow first byte delays every resource. The tester surfaces these exact fixes as built-in tips. Test the page first, apply the changes, then re-measure to confirm the number dropped.

It is accurate for what it measures: the real largest-contentful-paint timing of the page you are currently viewing, captured directly from your browser's performance entries rather than estimated. The catch is that it reflects only your conditions, the device you are on, your connection, and whether the page was already cached, so it is a single sample, not a representative score. Google ranks on the 75th-percentile LCP across many real visitors, which can differ substantially from your one reading. So trust the number as a true measurement of your own session, but do not assume it equals what most users experience. For the figure Google actually uses, pull field data from PageSpeed Insights and paste it into the analyzer here. That gives you both a live local read and a ratable real-world score side by side.