Well that happens to be a phone I have too, although the battery is pretty dead so it's hard to use. It's still a pretty powerful phone though, weird that it would have issue rendering the page.
I was able to reproducing freezing and hanging even on my Pixel 3, so I can probably look into it myself. Again, I have to guess the large SVGs are to blame.
As a former owner of that model of device, whose phone bricked itself irreparably after updating to Oreo, I'm surprised it hasn't been destroyed by the bootloop of death. I'll never buy a Google hardware product again after the runaround they gave me.
I managed to avoid that problem although I read about it plenty. It was my first Android phone, but I liked it except for the battery life issues, which were, frankly, brutal. Regularly shuts down at 50% battery. To replace the battery you are pretty much guaranteed to break parts of the camera assembly (the cover).
I'm not sure how blame should be apportioned between Google and the manufacturer though.
I bought the device from the Google store, had it replaced once (under warranty due to a different failure) by Google, and the box and device say "Google Nexus 6p." The update that bricked the phone (literally on the first startup after installing the update) came to me from Google.
So, I blame Google entirely. If they chose to contract out their hardware work to a poor manufacturer, that's their problem. My business is with Google, not that manufacturer.
Google didn't see it that way. They told me to contact the nearest Huawei service center.
That service center was across the Pacific Ocean, in China.
If my Macbook Pro fails to start up immediately after an Apple software update, I don't expect Apple to tell me "It's a problem with Samsung's memory, so we can't help you. Call Samsung in Korea." I expect them to take responsibility for their software update having rendered my device useless.
