MPD & HTTP servers take some time to start. Is that normal?

It takes the MPD server and the HTTP server almost 2 minutes to start, if I read these status logs correctly. Is that normal behaviour? Are there ways to speed this up?

pi@jimmys:~ $ sudo systemctl status mopidy
● mopidy.service - Mopidy music server
   Loaded: loaded (/lib/systemd/system/mopidy.service; enabled)
   Active: active (running) since Sun 2016-07-31 23:01:33 CEST; 2min 10s ago
 Main PID: 2095 (mopidy)
   CGroup: /system.slice/mopidy.service
           └─2095 /usr/bin/python /usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf

Jul 31 23:01:35 jimmys mopidy[2095]: INFO     Starting Mopidy backends: SoundCloudBackend, StreamBackend, M3UBackend, FileBackend, LocalBackend, SpotifyBackend
Jul 31 23:01:35 jimmys mopidy[2095]: INFO     Audio output set to "autoaudiosink"
Jul 31 23:01:36 jimmys mopidy[2095]: INFO     Loaded 0 local tracks using sqlite
Jul 31 23:01:37 jimmys mopidy[2095]: INFO     Starting Mopidy core
Jul 31 23:01:39 jimmys mopidy[2095]: INFO     Logged in to Spotify in offline mode
Jul 31 23:01:40 jimmys mopidy[2095]: INFO     Logged in to Spotify in online mode
Jul 31 23:03:39 jimmys mopidy[2095]: INFO     Starting Mopidy frontends: MpdFrontend, HttpFrontend
Jul 31 23:03:39 jimmys mopidy[2095]: INFO     MPD server running at [::]:6600
Jul 31 23:03:39 jimmys mopidy[2095]: INFO     HTTP server running at [::]:6680
Jul 31 23:03:39 jimmys mopidy[2095]: INFO     Starting GLib mainloop

Using Raspberry Pi? You could be bumping into the same problem as me:

The thing is that each playlist takes 1-5 seconds to load on my raspberry (can be seen in debug output). I don’t know what this means (is it loading the full playlists?) or if pyspotify/libpotify has to do this, but this has made mopidy kind of unusable to me the last months. I don’t have a solution unfortunately.