Paint timing (FCP, LCP) and Core Web Vitals
Reports when content first appeared and the largest element rendered.
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
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 77 | 2019-09-10 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Supported | 122 | 2024-01-23 | None |
| Safari | Supported | 26.2 | 2025-12-12 | None |
| Safari on iPhone | Supported | 26.2 | 2025-12-12 | None |
| Chrome on Android | Supported | 77 | 2019-09-10 | None |
| Samsung Internet | Supported | 12.0 | 2020-06-19 | None |
How a site asks for it
| API | PerformanceObserver type 'paint', 'largest-contentful-paint', 'layout-shift' |
| Browser compat keys | api.LargestContentfulPaint |
| How access is granted | none |
| What the user sees | Not listed |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Not listed |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- Observe paint entries
- Collect LCP candidate
- Report on pagehide
Data you get
What comes back: startTime in ms, 1 ms resolution
Shape: event
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
LCP | float | ms | 200 to 20000 | 1 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
| Type | Example | Apps |
|---|---|---|
| shopping | A retailer tracks how fast the main product photo appears and sees that faster pages sell more. | Shopify stores, Etsy |
| news | A news site fixes a slow hero image because search and ads depend on a fast first view. | None named |
| ads | An ad network watches that its ad slot does not push the main content later, since publishers get graded on it. | None named |
| games | A game portal checks how fast the game page and play button show up, to stop people leaving. | Poki, CrazyGames |
| analytics | Real user monitoring tools show LCP by country, device and network. | Chrome UX Report, SpeedCurve, Datadog RUM |
| video | A video site makes sure the poster image and play button appear first, before heavy scripts. | YouTube |
| travel | A 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
- web.dev: Largest Contentful Paint (LCP). Google says LCP measures how soon the main content of a page appears, as one of its Core Web Vitals.
- web.dev: Web Vitals. Google describes a set of simple measures of real user experience, to help sites improve speed.
Good uses and abuse
Legitimate uses
- Core Web Vitals
Known abuse
- Device and network speed class
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 5 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
History
- 2025-09, Firefox 122: LCP support
- 2025-09, Safari 26.2: LCP and paint timing in Safari 26.2
Related capabilities
Related
- Navigation and Resource Timing. Can see how fast the page and each file loaded for you
Sources
How well checked: Based on official documentation.