Long Animation Frames (LoAF)
Reports frames that took over 50 ms and which scripts caused them.
In one line
Can see slow page frames and which scripts caused them
Reports frames that took over 50 ms and which scripts caused them.
Shows slow frames with script URLs, durations, forced layout and blocking time. Gives site owners (and third party scripts) a view of device speed and which embedded scripts exist on the page.
What it can and can't do
What the user does: Nothing. It happens as the page runs
It can
- List frames that took over 50 ms
- Name which script or link made them slow
- Learn your device speed
- See how embedded or outside scripts affect the page
It cannot
- Work in Firefox or Safari
- Ask permission first
- See your files
- Know who you are by itself
How it differs between platforms: Chrome and Edge support it. Firefox and Safari do not.
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 123 | 2024-03-19 | None |
| Edge | Supported | 123 | 2024-03-22 | None |
| Firefox | Not supported | Not available | Not listed | None |
| Safari | Not supported | Not available | Not listed | None |
| Safari on iPhone | Not supported | Not available | Not listed | None |
| Chrome on Android | Supported | 123 | 2024-03-19 | None |
| Samsung Internet | Supported | 27.0 | 2024-11-06 | None |
How a site asks for it
| API | new PerformanceObserver(...).observe({type:'long-animation-frame'}) |
| Browser compat keys | api.PerformanceLongAnimationFrameTiming |
| 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
- Register observer
- Receive entries >50 ms with scripts[] attribution
- Report sourceURL and invoker
Data you get
What comes back: One entry per slow frame
Shape: event
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
duration | float | ms | 50 to 10000 | 1 ms (rounded) |
blockingDuration | float | ms | 0 to 10000 | 1 ms |
scripts | list | None | 0 to 30 | sourceURL, invoker, duration |
Technical limits
- Cross-origin script attribution limited to URL for opaque scripts only if CORS allowed
- Chromium only
The story
What it is
Browsers report screen updates that took over 50 milliseconds and which scripts caused them.
For you
You never see it. It is a tool that points to the exact script that made a page stutter. When teams fix those scripts, your scrolling and taps feel smoother.
For makers
Developers use it to find slow third party scripts, such as ads and chat widgets, and push vendors to fix or remove them. It helps meet Core Web Vitals targets and keeps real time apps smooth.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser game studio finds that one script froze the frame for 120 ms during a fight, and fixes it. | None named |
| ads | A publisher sees a slow ad script in its reports and drops that ad partner. | None named |
| shopping | A retailer finds that a chat widget makes the checkout button feel stuck and defers it. | None named |
| creative | A design tool traces a stutter while zooming to one heavy script and rewrites it. | Figma |
| video | A streaming site finds a script that makes the player controls lag, and splits it up. | None named |
| analytics | A monitoring service groups slow frames by script owner so teams can see which vendor is to blame. | Sentry, Datadog RUM |
| news | A news site traces scroll jank on phones to a heavy ad and sets a stricter ad rule. | None named |
Risks
- Exposes third party scripts
- Chromium only so far
What the platform says
- Google Chrome: Long Animation Frames API. Chrome says it helps developers find which scripts make pages feel janky or slow to respond.
Good uses and abuse
Legitimate uses
- INP debugging, third-party script audits
Known abuse
- Device performance class inference, script inventory
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 4 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2024-03, Chrome 123: LoAF ships
- 2025-01, Chrome: Adds renderStart, styleAndLayoutStart and script attribution fields
Related capabilities
Related
- Event Timing and INP. Can time how fast the page responds to your taps, clicks and key presses
Sources
How well checked: Based on official documentation.