What is a good LCP score?
Rubric check: slow main content on phones (LCP) (check id lab_lcp)
A good Largest Contentful Paint (LCP) is 2.5 seconds or less. LCP is how long the biggest element in view, usually the hero image or headline, takes to appear. Rubric flags pages over 2.5 seconds in a lab test on a mid-range phone over slow 4G.
Why it matters for SEO
LCP is one of Google's Core Web Vitals, which its ranking systems use as part of page experience. Google is clear that relevance matters far more, so a slow page with the best answer can still rank. Google judges Core Web Vitals on real visits; a lab test is a guide to what real users see.
Does this matter for ChatGPT and AI Overviews?
There's no evidence that LCP affects whether AI search tools cite a page. They read the HTML and don't wait for images to paint. Page speed matters for the people who click through from the answer, not for the citation itself.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: Opt-in: page speed.
It is judged on every page Rubric scores. It is only judged when you ask for the page speed test.
Every Rubric score starts at 100. When this check fails, it takes up to 6 points off. Even one failing page costs at least 3 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Rubric doesn't have enough crawled sites to say how common this is yet.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 2 of 2. On clean test pages, it stayed quiet 1 of 1 times. (Engine build d17c9d9.)
Real sites: people checked 12 of its findings by hand and 0 were wrong (0%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Compress and resize the hero image, and serve WebP or AVIF (most image plugins do this).
- Don't lazy-load the hero image. Since WordPress 6.3, core skips lazy loading and adds
fetchpriority="high"to the likely main image, but some themes and plugins override it. - Use a caching plugin or your host's cache, and cut render-blocking scripts from plugins you don't need.
Shopify
- Upload hero images at the size they display. Shopify's CDN serves WebP or AVIF to browsers that support them.
- In Customize, avoid sliders as the first section; a single image loads faster.
- Remove apps you don't use. Many add scripts to every page even after you stop using them.
Webflow
- In the Assets panel, convert large images to WebP or AVIF.
- Select the hero image and in its settings set Load to Eager rather than lazy.
- Remove heavy interactions or third-party scripts that delay the first view, then publish.
Custom code
Preload the hero image and give it priority:
<link rel="preload" as="image" href="/hero.avif" fetchpriority="high">
<img src="/hero.avif" width="1200" height="600" alt="Hikers on a ridge" fetchpriority="high">Also speed up the server response and inline the CSS the first screen needs.