bash-4.3$ systemd-analyze Startup finished in 10.238s (firmware) + 5.712s (loader) + 896ms (kernel) + 2.923s (initrd) + 22.227s (userspace) = 41.998s

and

>bash-4.3$ systemd-analyze blame
          3.297s systemd-udev-settle.service
          2.611s lvm2-monitor.service
          2.442s dmraid-activation.service
          1.751s systemd-journal-flush.service
          1.528s firewalld.service
          1.403s accounts-daemon.service
          1.399s plymouth-quit-wait.service
          1.324s systemd-backlight@backlight:intel_backlight.service
          1.267s systemd-fsck-root.service
          1.257s systemd-fsck@dev-disk-by\xxxxxxxxxxxx
          1.105s plymouth-start.service
           948ms packagekit.service
           944ms colord.service
           873ms boot.mount
           788ms udisks2.service
           764ms home.mount
           753ms systemd-journald.service
           741ms NetworkManager.service
           689ms polkit.service
           675ms systemd-udev-trigger.service
           669ms systemd-fsck@dev-disk-by\xxxxxxxxxx
           618ms fedora-import-state.service
           513ms chronyd.service
           463ms dev-sda9.swap
           364ms rtkit-daemon.service

and

bash-4.3$ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character.

graphical.target @22.217s └─multi-user.target @22.217s └─libvirtd.service @20.784s +269ms └─network.target @20.377s └─wpa_supplicant.service @21.362s +8ms └─basic.target @17.829s └─dnf-makecache.timer @17.827s └─sysinit.target @17.779s └─systemd-update-utmp.service @17.768s +9ms └─auditd.service @17.567s +196ms └─systemd-tmpfiles-setup.service @17.299s +263ms └─local-fs.target @17.298s └─home.mount @16.532s +764ms └─systemd-fsck@dev-disk-by\XXXXXXXXXXXXX └─dev-disk-by\x2duuid-XXXXXXXXXXXXXXX