DOM ready · Page ready
DOM ready: from the HTML arriving until the page finished parsing and running scripts.
DOM ready verdict
v1.2.8 vs v1.2.7 · / · mobileNowv1.2.7
Unchanged
Page ready got 63ms slower (+11.8%). 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.8
594ms
v1.2.7532msChange+63ms
Visits measured
142
on mobile, enough for a verdict
v1.2.7 · mobile237 / 30
v1.2.8 · mobile142 / 30
v1.2.8 · desktop9 / 30
Moved in the same release
The rest of load breakdown. A place to look, not a cause.
Load steps
/ · mobileThis release
v1.2.7
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.8 vs v1.2.7 · mobile · pages need 30 visits on both sidesPageVisitsv1.2.7v1.2.8ChangeVerdict
142532ms594ms+11.8%Unchanged
101578ms646ms+11.8%Unchanged
122607ms828ms+36.4%Regressed
41520ms581ms+11.8%Unchanged