$ systemd-analyze blame
1.959s dev-mapper-cryptroot.device
1.439s udisks2.service
528ms upower.service
376ms systemd-rfkill.service
304ms systemd-journal-flush.service
285ms systemd-udev-trigger.service
265ms systemd-udevd.service
227ms user@1000.service
194ms polkit.service
185ms NetworkManager.service
167ms systemd-tmpfiles-setup.service
160ms systemd-logind.service
154ms systemd-journald.service
109ms systemd-tmpfiles-setup-dev.service
83ms systemd-fsck@dev-disk-by\x2duuid-257cdd11\x2dc157\x2d4e8f\x2daff4\x2d3e07561de4ec.service
78ms lvm2-monitor.service
73ms modprobe@fuse.service
66ms dev-mqueue.mount
65ms modprobe@drm.service
65ms sys-kernel-debug.mount
64ms dev-hugepages.mount
63ms sys-kernel-tracing.mount
61ms tmp.mount
60ms kmod-static-nodes.service
57ms modprobe@configfs.service
49ms systemd-remount-fs.service
46ms systemd-modules-load.service
41ms wpa_supplicant.service
29ms systemd-random-seed.service
29ms sys-kernel-config.mount
28ms systemd-sysctl.service
27ms sys-fs-fuse-connections.mount
19ms systemd-backlight@backlight:intel_backlight.service
16ms systemd-update-utmp.service
16ms boot.mount
13ms user-runtime-dir@1000.service
12ms alsa-restore.service
9ms systemd-user-sessions.service