MTR Report Analysis

20 seconds latency on any network would be a performance disaster for any kind of interactive work, if you had it. But you don't.

You experience high latency (and packet losses) in getting traceroute responses from one hop on your journey to a remote host. This is not uncommon, especially if you're using ICMP-based traceroute, because most network devices prioritise actually routing traffic over sending ICMP ttl-exceededs about random PINGs which have died of old age. As you can see from the hops on the far side of that host (13-17), there are no such delays in your traffic passing through the host. Your biggest single hop-to-hop delay is between hops 6 and 7, which seems to be a point-to-point link inside your ISP, one that's probably saturated. You might consider monitoring that and complaining to your ISP if it remains so for some time (no ISP is going to respond to the complaint that you ran one traceroute and saw link problems, and rightly not).

As for what's causing problems with "internet performance", that is such an unquantified issue that it is impossible to speculate. If you can get a clearer problem statement from the user it may be possible to design experiments to shed light on it.

As an aside, please don't post images of text output; the links rot and the evidence is lost to your question, and they are unsearchable as text would not be. I've put the image into your question (something you lack the rep to do, I suspect, which isn't your fault) - but best practice is to cut-and-paste text into your question instead.