Skip to Content
Platform.Ontology

Paint timing (FCP, LCP) and Core Web Vitals

Reports when content first appeared and the largest element rendered.

Gets silentlySpeed and timingPerformance APIWeb browsersWhile you use it

In one line

Can check when content first showed and how long the biggest item took

Reports when content first appeared and the largest element rendered.

PerformancePaintTiming and LargestContentfulPaint give render timings that reflect network, CPU and GPU. Cross-origin images need Timing-Allow-Origin for full detail.

What it can and can't do

What the user does: Nothing. It happens as the page loads

It can

  • Get time to first content and time to the largest picture or block
  • Learn how fast your network, processor and graphics are
  • Get fuller detail for outside images only if their site allows it

It cannot

  • See your files
  • Ask permission first
  • Know who you are by itself
  • See full detail for other sites' images without their approval

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported772019-09-10None
EdgeSupported792020-01-15None
FirefoxSupported1222024-01-23None
SafariSupported26.22025-12-12None
Safari on iPhoneSupported26.22025-12-12None
Chrome on AndroidSupported772019-09-10None
Samsung InternetSupported12.02020-06-19None

How a site asks for it

APIPerformanceObserver type 'paint', 'largest-contentful-paint', 'layout-shift'
Browser compat keysapi.LargestContentfulPaint
How access is grantednone
What the user seesNot listed
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Observe paint entries
  2. Collect LCP candidate
  3. Report on pagehide

Data you get

What comes back: startTime in ms, 1 ms resolution
Shape: event

FieldTypeUnitRangePrecision
LCPfloatms200 to 200001 ms

Technical limits

  • Rounded to timer resolution
  • Cross-origin elements without TAO are exposed only with limited info

The story

What it is

Browsers report when the first content appeared and when the biggest item finished drawing.

For you

You never see the measure, but you feel it as how fast a page seems to load. Pages that show their main content quickly feel better and tend to rank higher in Google.

For makers

These numbers feed Google's Core Web Vitals, so they affect search ranking, ad revenue and sales. Teams track them from real visitors and fix slow images and scripts.

Where you see it

TypeExampleApps
shoppingA retailer tracks how fast the main product photo appears and sees that faster pages sell more.Shopify stores, Etsy
newsA news site fixes a slow hero image because search and ads depend on a fast first view.None named
adsAn ad network watches that its ad slot does not push the main content later, since publishers get graded on it.None named
gamesA game portal checks how fast the game page and play button show up, to stop people leaving.Poki, CrazyGames
analyticsReal user monitoring tools show LCP by country, device and network.Chrome UX Report, SpeedCurve, Datadog RUM
videoA video site makes sure the poster image and play button appear first, before heavy scripts.YouTube
travelA booking site compares paint times on slow phones to decide what to trim.Booking.com

Risks

  • Slow scores hurt ranking
  • Sent to analytics vendors

What the platform says

Good uses and abuse

Legitimate uses

  • Core Web Vitals

Known abuse

  • Device and network speed class

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility5 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits1Rough identifying entropy, when known

History

  • 2025-09, Firefox 122: LCP support
  • 2025-09, Safari 26.2: LCP and paint timing in Safari 26.2

Sources

How well checked: Based on official documentation.

On this page