Code review is a spectrum and its significance varies by company
In a past organization, I was tasked with code reviewing things that I barely understood. We were also under pressure to deliver features and the way to get praise was to have a higher velocity. So I just sat on the review requests for an hour, did other work, ran the tests, and approved them. I can't remember requesting any changes beyond removing
console.logs that got stuck. We also had no real standards for it, so it was often chaotic and different reviewers would have very contradictory feedback. There was one library one dev loved and another dev thought was an anti-pattern, so they battled about whether that should be there.
One of the challenges with code review is that in many organizations, it has been a good way to burn a lot of time and not get credit for that time. Here, I was the new guy who was seemingly churning through work very quickly as a junior. That should have raised red flags that corners were being cut. It didn't, because I suspect it was not considered important. It just made the senior who did give more detailed code reviews seem slow (one of many reasons related to code quality).
In my current organization we are a bit more serious about it, but as soon as there are deadlines, it quickly becomes about giving it a cursory check for errors and sending it through, especially given the relative juniority of the team here now. Even if feedback is given, the PR is usually approved with just a note about possible changes. Urgency is usually conveyed in the request, so whether the person asking says "review this please" or "approve this please."
At a company a friend works with, code review is a contractual requirement, but no PR has ever been rejected or had changes requested as they bill by the feature. Code review is a mere matter of box ticking there. It has no organizational purpose other than meeting a requirement. Approval comes 2-3 minutes after the PR is submitted.
Another friend is at a company where code review can take weeks as it requires so many people to view it, including people not from the team to ensure it is still usable to people who don't know the codebase. There, it is taken extremely seriously and it is expected for developers to spend hours on it if required.
So basically figure out what code review is supposed to mean at your company. In your company it seems like something one developer champions and everyone agreed should be done and could easily be done but really isn't considered important or incentivized. What you want to do in that case is up to you and what your manager wants.