[BUG] Profiles are not screenshotable

[prastut]

Describe the bug
I was trying to shill YieldScan on this tweet: https://twitter.com/balajis/status/1309033381615874048?s=20
Given Balaji is an OG in the crypto space, a tweet showing a validator profile with cool visualization would have garnered some organic traction.

Now the idea in my mind was to find the validator that has the most nominations in count.

Here is the bugs I found in my journey:

1. I wasn't able to find the most nominated validator from validator tab. I then had to resort to https://kusama.polkastats.io/validators and sort by nominators.

2. I landed https://kusama.polkastats.io/validator/EUwcW86EFGDoDfUP2UJYuBwhCWC7cW9SdFH9cPh6UPBvBHj as the most staked given it's being staked by 55 stakers as of writing. I used this address and opened up YieldScan, this is what I see:

Source: https://yieldscan.onrender.com/validator-profile/EUwcW86EFGDoDfUP2UJYuBwhCWC7cW9SdFH9cPh6UPBvBHj

This entire screen is riddled with bugs.

Expected behavior
I should be able to do the above journey without requiring polkastats + take a beautiful screenshot

Screenshots

Desktop (please complete the following information):

• OS - MacOS
• Browser - Brave

[saumyakaran]

@prastut Regarding 1., could you explain what problem you faced while trying to sort by nominators?

[prastut]

I couldn't figure how how to sort.

[saumyakaran]

I couldn't figure how how to sort.

This video should help, however I can feel that this might be a UX issue

[saumyakaran]

This entire screen is riddled with bugs.

@prastut Also, I just noticed that you mentioned "riddled with bugs".

I could only see the UI bug where the viz is taking up more space that it should for this specific viewport width.

Is there any other bug here that I'm missing? If yes, then would it be possible to list them here?

2. I landed https://kusama.polkastats.io/validator/EUwcW86EFGDoDfUP2UJYuBwhCWC7cW9SdFH9cPh6UPBvBHj as the most staked given it's being staked by 55 stakers as of writing. I used this address and opened up YieldScan, this is what I see:

Regarding this, would it be possible to state the screenwidth that you were using when this happened?

Also, did this happen by default or did you try resizing the screen? Why I ask this is because I've only been able to recreate this by first rendering the page (where it renders fine) and then resizing it, where the viz doesn't change size responsively