Hi Oren,
First before trying to work around an issue like this, I would would argue that is an application defect that your development team should be “fixing” by removing those 3rd party components if they are not absolutely necessary.
Of course that was a very pious answer from my high horse and reality doesn’t always meet with our ideals 
The builtin library has options like Run Keyword And Expect Error and Run Keyword And Ignore Error for dealing with things like this, you may even want to temporarily shorten the timeout for that (those?) page load(s) so the time out error is predictable.
Another option might be a simple “infrastructure” fix of using a proxy server that caches these elements.
But I would really want to report upstream that the end user will experience these timeouts, not having those 3rd party elements loaded may lead to unpredictable user experience if your devs are relying on them for UI theming etc, as for google analytics if that’s timing out then the analytics results are not going to be reliable, and so therefore not really providing any value, since you’ve proven that to be the case it can be removed too.
Hope this helps,
Dave.