High reported result time

Numerlor

When I do a search, then refresh w/o cache with ctrl shift r, on the next refresh the time to get results seems to be counted from previous forced refresh instead of the last refresh.

I can't completely reliably reproduce it but it happens most of the time, sometimes a new window is needed so I'd assume it's related to result caching on the backend

RoxyRoxyRoxy

Yes we do backend caching, I'm almost certain this is related to that (something like the elapsed time getting cleared during the hard reload). Will fwd to the team for review.