Quattr leads AEO, SEO, and content rankings on G2 Spring 2026. View our G2 badges →
Request demo
Request demo

score seconds · lower is better

Largest Contentful Paint

also called LCP

Definition

How long it takes for the largest visible element on a page to render.

How it's calculated

Read from the product's weighted summary measure, which is already expressed in SECONDS, the semantic layer divides the underlying millisecond measurement by a thousand before exposing it, and the product renders that value unchanged with a seconds suffix. The display projection only rounds to two decimal places; grading is applied to the same seconds value, bucketing at 2.5 and 4 seconds.

Scope, grain and dimensions

Grain
One number per date range, optionally split by device, or one row per page.
Dimensions
page · device
Required filters
date_range
Aggregation
The headline number is read from the product's own weighted summary measure with no page dimension. Averaging page-level values a second time would give every page equal weight and is the documented cause of a past mismatch against the product UI.
Metric type
score · seconds

Data sources

Where you'll see this

Named reports that normally include this metric.

Core Web Vitals report

Skills and analyses that use it

Skills carry the judgment; the analysis verbs do the reading.

Analysis verbs

site_health_cwv_checkcorrelate_domainssignificance_check

Method rungs and levers

R1 Reachable

This sits on the bottom rung: if it reads badly, every measurement above it is unreliable.

levers L1 Technical & crawl health

Ask Quattr

How to read it

Rendering speed, in the same seconds the thresholds are written in, read it against 2.5 and 4 seconds and quote the grade beside it. It is also the field the page evidence is ranked by: the worst-pages list is the slowest-rendering pages, so this vital, not the performance score, decides which pages get looked at.

Caveats, freshness and failure modes

Seconds, end to end. It is not a Lighthouse sub-score and not milliseconds: a reading of 5.72 is 5.72 seconds. An earlier version of this product treated the same value as an internal hundredths-of-a-second score, multiplied it by a hundred and labelled the result milliseconds, turning 5.72 seconds into 572 milliseconds, that is the bug the current scale replaces, and it is why any figure here quoted in milliseconds should be distrusted.

The grading thresholds are the standard Core Web Vitals bands, and the threshold VALUES are recorded in code as pending product-specific confirmation.

These are lab measurements, not field data from real visitors.

Collection cadence varies by site and by page, so a vital measured three weeks ago is reported as three weeks old rather than as current.

When results are split by device the page rows become page-by-device observations, so a worst-page figure is a single device's measurement and can sit well above the device-blended value the product UI shows for the same page and window.

Freshness
varies by site, priority URLs can run nightly; most pages far less often. The collection date rides on the card rather than being assumed.

Common failure modes

  • Treating the value as a zero-to-one Lighthouse sub-score, or rescaling it by a hundred in either direction.
  • Quoting a device-split worst-page figure as that page's blended value.
  • Averaging page-level values to produce a site headline.

Not the same as

The confusions that cause the most wrong decisions.

Largest Contentful Paint Vital grade Compare definitions →

One is a numeric average, the other is the graded bucket that average falls into. Score and verdict are kept separate on every vital.

Largest Contentful Paint Crawler response time Compare definitions →

Server response latency to a crawler is not page-render speed for a visitor. Different measurements from different sources, and neither predicts its counterpart.

Verification

Last verified 2026-08-04 · reference version 1.1 { } This metric as JSON ↗