A stopwatch with laps is only useful if the numbers change what you do next. Each of the three summary figures answers a different question.
This stopwatch shows one list, where each row is the time for that segment rather than the total elapsed time at that moment. Pressing Lap seals the segment that just finished and starts counting the next one, so row three is the third segment on its own.
Once you have recorded at least two laps, the list highlights the quickest segment as fastest and the longest as slowest, and the footer shows the average across all of them. They are marked per segment, not per total, so you can see which part of a run or a task actually varied.
Readings run to a hundredth of a second. Note that browser timing is not a laboratory instrument: very heavy pages, a sleeping machine or an overloaded CPU can all add drift, so treat it as accurate to roughly a frame, not to a millisecond.
Yes. Elapsed time is computed from the wall clock rather than from animation frames, so switching tabs or app windows does not slow the countdown. It does, however, use the digits' rendering to tick, so a throttled background tab may update less often while still being correct.