DOM ready · Page ready
DOM ready: from the HTML arriving until the page finished parsing and running scripts.
DOM ready verdict
v1.2.2 vs v1.2.1 · / · mobileNowv1.2.1
Unchanged
Page ready didn’t change. A change only counts when it is at least 5% and at least 100ms. Here that means 100ms, so this one doesn’t.
faster−100ms · too small to count · +100msslower
Now · v1.2.2
536ms
v1.2.1536msChange0ms
Visits measured
241
on mobile, enough for a verdict
v1.2.1 · mobile168 / 30
v1.2.2 · mobile241 / 30
v1.2.2 · desktop87 / 30
Moved in the same release
The rest of load breakdown. A place to look, not a cause.
Load steps
/ · mobileThis release
v1.2.1
DNSConnectServerDownloadDOM readyp75 of each step, so they don’t add up exactly to TTFB.
DOM ready across releases
Typical visit · each point is a deploy, ringed by its DOM ready verdictImprovedRegressedUnchanged
DOM ready by page
v1.2.2 vs v1.2.1 · mobile · pages need 30 visits on both sidesPageVisitsv1.2.1v1.2.2ChangeVerdict
241536ms536ms+0.0%Unchanged
173583ms583ms+0.0%Unchanged
207612ms612ms+0.0%Unchanged
69524ms524ms+0.0%Unchanged