$ systemd-analyze time
Startup finished in 1.484s (kernel) + 3.424s (initrd) + 1min 2.416s (userspace) = 1min 7.325s
graphical.target reached after 1min 2.394s in userspace
$ systemd-analyze blame
35.705s udisks2.service
20.054s power-profiles-daemon.service
19.851s plymouth-quit-wait.service
19.741s accounts-daemon.service
19.740s polkit.service
15.509s unbound-anchor.service
11.367s logrotate.service
6.797s NetworkManager-wait-online.service
5.471s lvm2-monitor.service
5.150s systemd-journal-flush.service
4.934s chronyd.service
4.715s initrd-switch-root.service
4.082s fwupd.service
3.398s firewalld.service
2.305s packagekit.service
2.047s systemd-zram-setup@zram0.service
1.632s virtqemud.service
1.213s abrtd.service
1.193s thermald.service
1.124s systemd-fsck@dev-disk-by\x2duuid-5a1091e8\x2d8621\x2d49d5\x2db051\x2d7c>
979ms rpc-statd-notify.service
$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 2.394s
└─multi-user.target @1min 2.394s
└─plymouth-quit-wait.service @42.535s +19.851s
└─systemd-user-sessions.service @42.338s +187ms
└─remote-fs.target @42.329s
└─remote-fs-pre.target @42.328s
└─nfs-client.target @36.325s
└─gssproxy.service @35.537s +787ms
└─network.target @35.523s
└─wpa_supplicant.service @58.688s +284ms
└─basic.target @11.865s
└─dbus-broker.service @11.651s +207ms
└─dbus.socket @11.628s
└─sysinit.target @11.607s
└─systemd-update-utmp.service @11.565s +41ms
└─auditd.service @11.152s +410ms
└─systemd-tmpfiles-setup.service @10.806s +332ms
└─local-fs.target @10.780s
└─boot.mount @10.740s +39ms
└─systemd-fsck@dev-disk-by\x2duuid-5a1091e8>
└─local-fs-pre.target @9.051s
└─lvm2-monitor.service @3.579s +5.471s