Faster boot times without wifi?

I tried disabling wait for wifi on boot. But when checking

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 7.995s
└─multi-user.target 7.994s
└─getty.target 7.994s
└─serial-getty@ttyS2.service 7.992s
└─systemd-user-sessions.service 7.953s +26ms
└─network.target 7.872s
└─ifup@wlan0.service 3.474s +4.396s
└─network-pre.target 3.435s
└─dietpi-preboot.service 3.145s +288ms
└─dietpi-ramlog.service 3.041s +73ms
└─basic.target 2.999s
└─sockets.target 2.999s
└─dbus.socket 2.998s
└─sysinit.target 2.995s
└─systemd-timesyncd.service 2.866s +128ms
└─systemd-tmpfiles-setup.service 2.720s +99ms
└─local-fs.target 2.679s
└─run-credentials-systemd\\x2dtmpfiles\\x2dsetup.service.mount 2.731s
└─local-fs-pre.target 1.360s
└─systemd-tmpfiles-setup-dev.service 1.269s +89ms
└─systemd-sysusers.service 1.149s +83ms
└─systemd-remount-fs.service 977ms +144ms
└─systemd-journald.socket 803ms
└─system.slice 720ms
└─-.slice 720ms

I can still see that it slows down the boot:

ifup@wlan0.service  +4.396s

Can I do anything else to skip wifi on boot to save boot time, and connect when the system is up and running?

did you tried using STATIC IP? This might speed up network park

I’ve set a static IP on my router yes.

But this device will not be used with wifi at all times, so I rather have it connect to wifi after boot.

why not disabling WiFi completely if not used?

STATIC IP on the device itself to bypass DHCP

It is used, but not all the time. And doesn’t need to be prioritized on boot.

I’ll try that!