The reasoning behind including self.browser.implicitly_wait() is that Selenium can otherwise look for the next element (in this case, the error window) before it's actually finished loading, throwing false errors as a result. I'd suggest reducing to self.browser.implicitly_wait(1), but if you'd rather strike it entirely and only add it back in if we start running into those false errors, I'm fine with that too.