Ian Clelland | 6688e62 | 2023-09-04 20:57:15 | [diff] [blame] | 1 | # Largest Contentful Paint change in Chrome 116 to better handle animated content. |
| 2 | |
| 3 | Starting around Chrome 116, we're making two changes to the way that LCP handles |
| 4 | animated images and videos. In both cases, Chrome will count the time that the |
| 5 | first full frame is presented as the timestamp for the candidate. |
| 6 | |
| 7 | # Videos |
| 8 | |
| 9 | Videos have previously been ignored for LCP, unless they have a poster image. |
| 10 | With this change, a video element can become an LCP candidate, exactly like an |
| 11 | image. If it is used as a candidate, then the associated timestamp will be the |
| 12 | time that the first video frame is presented on screen. |
| 13 | |
| 14 | # Animated images |
| 15 | |
| 16 | Animated images (animated GIFs and PNGs) were previously not considered as LCP |
| 17 | candidates until they were fully loaded. For large files, this could be long |
| 18 | after the video has been playing on screen. This change counts the time that the |
| 19 | first frame of the animation is displayed, if the image becomes an LCP |
| 20 | candidate. |
| 21 | |
| 22 | ## How does this affect a site's metrics? |
Barry Pollard | 27c7fe1 | 2025-03-20 17:41:25 | [diff] [blame^] | 23 | |
Ian Clelland | 6688e62 | 2023-09-04 20:57:15 | [diff] [blame] | 24 | Pages with large auto-playing videos should start seeing that video used as the |
| 25 | LCP element. LCP scores may improve or regress on those pages, depending on what |
| 26 | element is currently being chosen as LCP. |
| 27 | |
| 28 | Pages with large animated images will likely see LCP scores improve, as the |
| 29 | image will be reported with an earlier timestamp than before. |
| 30 | |
Barry Pollard | 27c7fe1 | 2025-03-20 17:41:25 | [diff] [blame^] | 31 | Note for now, this only affects UKM (and so CrUX) reporting of LCP and does not |
| 32 | affect PerformanceObserver observations as measured in JavaScript. |
| 33 | |
Ian Clelland | 6688e62 | 2023-09-04 20:57:15 | [diff] [blame] | 34 | ## When were users affected? |
Barry Pollard | 27c7fe1 | 2025-03-20 17:41:25 | [diff] [blame^] | 35 | |
Ian Clelland | 6688e62 | 2023-09-04 20:57:15 | [diff] [blame] | 36 | This change was launched to Chrome users starting on roughly 2023-08-22, to be |
| 37 | rolled out to existing Chrome 116+ installs over a 14 day period. |