⏱QuickTimer

Home › Guides › Why online timers slow down or stop

Why online timers slow down or stop

Background tabs, frozen pages, computer sleep and silent alarms: what the browser makers say, and how to get a reliable timer.

Open the timer

Written by the QuickTimer editorial team. Published 8 November 2026. General information only.

If a browser timer ran slow, rang late or never rang, the cause is usually not the timer itself. Browsers deliberately slow down the code in tabs you cannot see, and a few other situations can pause a page completely. This guide explains what the browser makers say about it and what you can do.

Why a timer in a background tab can run late

Web pages run timers with a function called setTimeout or setInterval. MDN, the Mozilla developer documentation, says browsers "will enforce a minimum timeout delay in inactive tabs", and that the actual delay "may be longer than set". For Firefox on desktop it gives a minimum of 1 second for inactive tabs. A timer that updates once a second is largely unaffected by that, but a timer that checks more often can be held back.

Chrome's stronger limit after five minutes

Chrome goes further. Its developer blog says that from Chrome 88 (January 2021) it heavily throttles chained JavaScript timers on hidden pages. Chrome applies the strongest limit only when all of these are true:

  • The page has been hidden for more than 5 minutes.
  • The timer chain count is 5 or greater.
  • The page has been silent for at least 30 seconds.
  • WebRTC (live video or data calls) is not in use.

When those conditions are met, Chrome says "the browser will check timers in this group once per minute". A countdown that simply counts ticks can therefore fall behind in a tab you left open in the background for a long time. A well-built timer works out the time left from a stored end time instead of counting ticks, so when it next runs it still shows the right number. That design choice is our own approach, not something the browser makers require.

Frozen and discarded tabs

Chrome's Page Lifecycle documentation describes two states that matter for long timers. In the frozen state, "JavaScript timers and fetch callbacks don't run" until the page is unfrozen. In the discarded state, "no tasks, event callbacks, or JavaScript of any kind can run", and the page must be reloaded to be used again. If your timer tab was frozen or discarded to save resources, the alarm will not sound until you return to the tab.

Does a timer keep running when the computer sleeps?

Not reliably. MDN notes that the specification says the browser's high resolution clock should keep ticking when the operating system sleeps, but that "only browsers on Windows keep ticking during sleep". For long timings MDN suggests the system clock, Date.now(), may be more useful. Neither source says exactly what your page does when your machine sleeps, so for anything important do not rely on a browser tab: if the computer sleeps, expect the alarm to be late or missing.

Can I keep the screen awake?

Browsers offer a Screen Wake Lock feature that stops a device from dimming or locking the screen while a page needs it. MDN says it is limited to secure (HTTPS) pages, that a request "may be rejected" for reasons such as power save mode or low battery, and that locks are released automatically when the page becomes inactive. In other words, it can keep the screen on while you are watching the timer, but it does not give a hidden tab special treatment.

Why does the alarm sound sometimes stay silent?

MDN's autoplay guide says audio playback that starts without a user action is generally blocked: media can autoplay only if it is muted or "the user has interacted with the site". So an alarm sound normally needs you to have clicked, tapped or pressed a key on the page first, such as pressing Start. If a sound does not play, make sure you started the timer on that page and that the tab or device volume is not muted.

How to get the most reliable result

  • Keep the timer in its own window, visible, rather than buried in a hidden tab.
  • Press Start on the page itself so the browser allows the alarm sound.
  • Stop the computer from sleeping in your power settings for long timers, and plug in a laptop.
  • For anything critical, such as medication or a cooking time, back the browser up with a phone or kitchen timer.

Sources, read 8 November 2026: Chrome for Developers: heavy throttling of chained JS timers (Chrome 88); MDN: setTimeout; Chrome for Developers: Page Lifecycle API; MDN: Performance.now(); MDN: Screen Wake Lock API; MDN: Autoplay guide. Browser behaviour changes, so check the current documentation.

Related timers

Common questions

Why does my online timer slow down when I switch tabs?

Browsers limit the code in hidden tabs. MDN says they enforce a minimum timeout delay in inactive tabs, and Chrome checks some timers only once per minute after a page has been hidden for more than 5 minutes.

Does an online timer work if my computer goes to sleep?

Not reliably. MDN says only browsers on Windows keep the high resolution clock ticking during sleep, so expect a late or missing alarm if the computer sleeps.

Why did my timer alarm not make a sound?

Browsers generally block audio that starts without a user action. MDN says media can autoplay only if it is muted or the user has interacted with the site, so press Start on the page first and check your volume.

Can I stop my screen from turning off during a timer?

Browsers offer a Screen Wake Lock feature on HTTPS pages, but it can be rejected for reasons such as low battery and is released when the page becomes inactive.