Why does Big O Notation come up so often in Front End interviews?

Ok so I've been a front end developer for over 3 years now, and recently I've started interviewing for front end roles abroad because I want to have the experience of living in a different country.

In the past 4 interviews I've attended, there were at least 20 to 30 minutes of complex algorithm discussions involving Big O Notation and the likes. I cannot comprehend how this is at all that relevant to a front end position! I have never met a single web developer who was able to solve a performance issue with an algorithmic approach.

In my mind, if you're having to iterate through millions and millions of entries (where big O really becomes an issue), there is something SERIOUSLY wrong with your API design, and there are a number of -better- ways to solve these issues rather than making that algorithm O(logn) instead of O(n).

I really do understand the importance of Big O Notation in CS fields in general, and for some specific software engineering roles (mainly backend roles), it is vital for the application to function properly. But I have yet to see a real-case scenario where big O Notation came to save the day in the front end part of an application. How can a front end developer remember something organically in an interview if we are not using those concepts in our day-to-day work?

I feel like the interview process for all software engineering roles has become so standard that people just ask these 2nd-year CS questions out of pure laziness.

Am I crazy about this?