Given the website is fast and responsive: do we still need an active/pressed state for a button? Can we afford to have the pressed state similar to the hover state, because a website is so fast you hardly get to see the pressed state anyway?
So far Google only came up with how to design a good active/pressed state, but I don't read why we need it. I saw a question similar to mine asked 11 years ago, but it lacks arguments. Hopefully we can ask it again and gain some shared insight.
I can imagine that if a website is slow, it's a good user experience to inform the user the action is registered. But typically, the website I work at is blazing fast. Even when I throttle my internet connection, it still remains fast. So besides speed, why would we need a pressed state? Improved accessibility? Required for screen readers?