Connecting to Internet takes too long

Question

Whereas all other Mac OS and iOS devices behave normally in the same LAN, my MBP takes a minute after waking up from sleep to connect to the Internet*.
Thanks a lot for a good idea!
Peter
*) Here are some logs:
10.02.14 16:13:16,336 UserEventAgent[13]: Captive: CNPluginHandler en1: Authenticated
10.02.14 16:13:16,341 Little Snitch Daemon[72]: FIXME: IOUnserialize has detected a string that is not valid UTF-8, "1A�?".
10.02.14 16:13:17,859 configd[59]: setting hostname to "macbookpro.home"
10.02.14 16:13:20,014 apsd[65]: Unrecognized leaf certificate
10.02.14 16:13:21,073 CalendarAgent[278]: [com.apple.calendar.store.log.subscription] [Failed to refresh <CalManagedSubscriptionInfo: 0x7f9c5da0b4d0> (entity: SubscriptionInfo; id: 0x4001ab <x-coredata://F821E31D-CB62-44F8-A1C3-6D996813A38F/SubscriptionInfo/p1> ; data: {
    calendar = "0x40018b <x-coredata://F821E31D-CB62-44F8-A1C3-6D996813A38F/SubscriptionCalendar/p1>";
    hasAlarmFilter = 1;
    hasAttachmentFilter = 1;
    hasTaskFilter = 1;
    isAutoProvisioned = 0;
    isAutoRefreshed = 1;
    languageCode = nil;
    lastError = "0x5fa0001cb <x-coredata://F821E31D-CB62-44F8-A1C3-6D996813A38F/SubscriptionError/p6120>";
    locationCode = nil;
    needsRefresh = 0;
    refreshDate = "2013-07-21 14:28:53 +0000";
    refreshInterval = 300;
    subscriptionID = nil;
    subscriptionNotes = "Schedules from Pagico";
    subscriptionTitle = Pagico;
    subscriptionURL = "(...not nil..)";
    subscriptionURLString = "webcal://127.0.0.1:1200/extras/ical-feed/";
}) with error Error Domain=NSURLErrorDomain Code=-1004 "Verbindung zum Server konnte nicht hergestellt werden." UserInfo=0x7f9c5be30310 {NSUnderlyingError=0x7f9c5da436f0 "Verbindung zum Server konnte nicht hergestellt werden.", NSErrorFailingURLStringKey=http://127.0.0.1:1200/extras/ical-feed/, NSErrorFailingURLKey=http://127.0.0.1:1200/extras/ical-feed/, NSLocalizedDescription=Verbindung zum Server konnte nicht hergestellt werden.}]
10.02.14 16:13:21,465 digest-service[29340]: digest-request: uid=0
10.02.14 16:13:21,465 digest-service[29340]: digest-request: init request
10.02.14 16:13:21,469 digest-service[29340]: digest-request: init return domain: MACBOOKPRO server: MACBOOKPRO indomain was: <NULL>
10.02.14 16:13:21,506 digest-service[29340]: digest-request: uid=0
10.02.14 16:13:21,506 digest-service[29340]: digest-request: init request
10.02.14 16:13:21,510 digest-service[29340]: digest-request: init return domain: MACBOOKPRO server: MACBOOKPRO indomain was: <NULL>
10.02.14 16:13:58,000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0x2800 ****
10.02.14 16:14:04,392 syncdefaultsd[31053]: Initial test for reachability failed. Let's mark service as unreachable for now
10.02.14 16:14:04,421 syncdefaultsd[31053]: Initial test for reachability failed. Let's mark service as unreachable for now
10.02.14 16:14:04,422 syncdefaultsd[31053]: Initial test for reachability failed. Let's mark service as unreachable for now
10.02.14 16:14:04,422 syncdefaultsd[31053]: Initial test for reachability failed. Let's mark service as unreachable for now
10.02.14 16:14:04,423 syncdefaultsd[31053]: Initial test for reachability failed. Let's mark service as unreachable for now
10.02.14 16:15:07,224 PluginProcess[35831]: CoreText performance note: Client called CTFontCreateWithName() using name "Times Roman" and got font with PostScript name "Times-Roman". For best performance, only use PostScript names when calling this API.
10.02.14 16:15:07,224 PluginProcess[35831]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.

Answer 1

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you boot, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, reboot as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.