the site can recognize an android webview (you might want to try changing the user-agent). when this occurs, it redirects the user to a url whose scheme is "intent://". this is meant to launch the appropriate app on the user's device. you can possibly work around this by intercepting webview client's shouldOverrideUrlLoading method.
obviously you could change the scheme to https://, but that doesn't necessarily mean you're going to get a webpage as a result. by using "intent" deep-linking, the site wants to launch an app, not serve a webpage. by changing the user agent, you might get a few steps further, but the site is expecting you to have that app. if you use shouldOverrideUrlLoading, you would return true (to abort the loading) and then launch the app. when the site detects a desktop browser, it just does a normal redirect.