Edit: A better comparison is https://c.tenor.com/3eIvVsG3yPYAAAPo/the-universe-tim-and-er... vs https://c.tenor.com/3eIvVsG3yPYAAAAd/the-universe-tim-and-er...
$ wget "https://c.tenor.com/bD9vHNiR1rQAAAAd/boom-mind-blown.webm"
--2022-08-12 09:39:06-- https://c.tenor.com/bD9vHNiR1rQAAAAd/boom-mind-blown.webm
Resolving c.tenor.com (c.tenor.com)... 142.251.46.225
Connecting to c.tenor.com (c.tenor.com)|142.251.46.225|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6381102 (6.1M) [image/gif]The mp4 of it is at https://c.tenor.com/Oc4nf8N08jIAAAPo/mind-blow-galaxy.mp4, and is 12.1 MiB to the HD gif's 17 MiB (https://c.tenor.com/Oc4nf8N08jIAAAAC/mind-blow-galaxy.gif). As you noted, the SD gif is only 6.1 MiB.
I know Webm and other formats might be heavily recommended, but there are a ton of issues currently in the browser ecosystem with videos and autoplay rules (looking at iOS specifically as a major problem causer here...). Those issues can make webm/etc more trouble than they are worth unless you're operating at a really large scale, or you're willing to lose your animations for a decent percentage of users.
Ideally all browsers should have uniform means to control animated graphics (allow or not autoplay, stop all or stop a particular one, etc), and a uniform way to show the intent (autoplay or not, play on hover, etc).
Tell that to all the kids that 22 years later after this article, still use GIFs several times a day in their ubiquitous chatting apps. :)
https://c.tenor.com/bD9vHNiR1rQAAAAd/boom-mind-blown.gif