so this was not the case prior for me but systemd boot has become noticeably slower for me at start up. i noticed that the loader time is exceptionally long all of a sudden
systemd-analyze
Startup finished in 16.356s (firmware) + 16.799s (loader) + 1.411s (kernel) + 1.347s (userspace) = 35.915s
graphical.target reached after 1.327s in userspace.
systemd-analyze blame
82ms mnt-never4get.mount
79ms user@1000.service
78ms dev-nvme0n1p2.device
58ms systemd-journal-flush.service
46ms mnt-69hell.mount
44ms systemd-udev-trigger.service
27ms systemd-journald.service
25ms systemd-udevd.service
20ms power-profiles-daemon.service
20ms systemd-random-seed.service
19ms accounts-daemon.service
18ms systemd-hostnamed.service
18ms systemd-timesyncd.service
17ms systemd-fsck@dev-disk-by\x2duuid-041B\x2d4CA1.service
17ms systemd-tmpfiles-setup.service
15ms efi.mount
15ms systemd-logind.service
12ms avahi-daemon.service
11ms NetworkManager.service
11ms systemd-tmpfiles-setup-dev.service
10ms dbus.service
7ms polkit.service
6ms mnt-dumbshit13.mount
5ms modprobe@fuse.service
5ms lightdm.service
5ms wpa_supplicant.service
5ms dev-hugepages.mount
5ms alsa-restore.service
5ms systemd-modules-load.service
5ms dev-mqueue.mount
4ms sys-kernel-debug.mount
4ms user-runtime-dir@1000.service
4ms sys-kernel-tracing.mount
4ms tmp.mount
3ms kmod-static-nodes.service
3ms systemd-sysctl.service
3ms modprobe@configfs.service
3ms systemd-update-utmp.service
3ms modprobe@drm.service
2ms systemd-remount-fs.service
1ms systemd-user-sessions.service
1ms rtkit-daemon.service
1ms sys-fs-fuse-connections.mount
916us sys-kernel-config.mount
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 @1.327s
└─lightdm.service @1.320s +5ms
└─systemd-user-sessions.service @1.318s +1ms
└─nss-user-lookup.target @1.327s