DOM ready · Page ready
DOM ready: from the HTML arriving until the page finished parsing and running scripts.
DOM ready verdict
v1.2.0 vs v1.1.9 · / · mobileNowv1.1.9
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.0
536ms
v1.1.9536msChange0ms
Visits measured
220
on mobile, enough for a verdict
v1.1.9 · mobile176 / 30
v1.2.0 · mobile220 / 30
v1.2.0 · desktop79 / 30
Moved in the same release
The rest of load breakdown. A place to look, not a cause.
Load steps
/ · mobileThis release
v1.1.9
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.0 vs v1.1.9 · mobile · pages need 30 visits on both sidesPageVisitsv1.1.9v1.2.0ChangeVerdict
220536ms536ms+0.0%Unchanged
157583ms583ms+0.0%Unchanged
189612ms612ms+0.0%Unchanged
63524ms524ms+0.0%Unchanged