Stopwatch
Counts up in hundredths, records laps, and stays accurate whatever else your browser is doing.
Reading the clock, not counting frames
A stopwatch has the same failure mode as a countdown and it is even easier to trip over: if elapsed time is accumulated by adding up intervals, every dropped frame is time that quietly disappears. Under load, or in a background tab, a frame-counting stopwatch can lose whole seconds.
This one stores the moment you pressed start and subtracts it from the current time. Laps are recorded the same way. The consequence is that the number is right even if the display stutters, which is the correct trade — a stopwatch that renders smoothly but reports the wrong elapsed time is useless.
Hundredths, and why not thousandths
The display stops at hundredths of a second deliberately. Browsers deliberately coarsen high-resolution timers to make fingerprinting and timing attacks harder, and human reaction time on a button press is around 200 milliseconds regardless. A stopwatch showing thousandths would be displaying three digits of noise to look precise.