LoAF · Main-thread blocking
Long Animation Frames: time per visit the main thread was too busy to react.
LoAF verdict
v1.2.1 vs v1.2.0 · / · mobileNowv1.2.0
Unchanged
Main-thread blocking didn’t change. A change only counts when it is at least 5% and at least 50ms. Here that means 50ms, so this one doesn’t.
shorter−50ms · too small to count · +50mslonger
Now · v1.2.1
304ms
Needs improvement
v1.2.0304msChange0msGood up to200ms
Visits measured
158
on mobile, enough for a verdict
v1.2.0 · mobile207 / 30
v1.2.1 · mobile158 / 30
v1.2.1 · desktop57 / 30
Where visits landed
share of visits in each rangev1.2.043%55%
v1.2.144%54%
Good ≤ 200msNeeds improvementPoor > 600ms
Same shape as v1.2.0. One in three mobile visits block for 200ms or less.
Moved in the same release
Things that can keep the main thread busy. A place to look, not a cause.
Scripts behind long frames
The script that blocked longest on each visit with long frames · Mobile
| Script | Visits | Blocking p75 |
|---|---|---|
| www.googletagmanager.com/gtm.js | 76 · 30% | 260ms |
| Inline script | 35 · 14% | 180ms |
“New” means it never led on the previous release. Inline scripts are grouped together, and query strings are never collected.
LoAF across releases
Typical visit · each point is a deploy, ringed by its LoAF verdictGood ≤ 200ms
ImprovedRegressedUnchanged
LoAF by page
v1.2.1 vs v1.2.0 · mobile · pages need 30 visits on both sidesPageVisitsv1.2.0v1.2.1ChangeVerdict
158304ms304ms+0.0%Unchanged
113330ms330ms+0.0%Unchanged
135347ms347ms+0.0%Unchanged
45297ms297ms+0.0%Unchanged