Checkout, signup, and login
Check as often as every 1 minute. These are directly tied to revenue and access, so fast detection pays for itself.
Check too rarely and you find out about problems late; check constantly and you risk noise and wasted effort. The right monitoring frequency depends on how much a minute of downtime actually costs your site — and it is not the same for every page.
Match check frequency to what a minute of downtime actually costs each page.
Monitoring frequency directly sets the ceiling on how fast you can respond. If you check every 15 minutes, then in the worst case you learn about an outage 15 minutes after it starts, plus the time to react. For a personal blog that is fine; for a checkout that processes orders every minute, it can be expensive.
The instinct is to check everything as often as possible, but that has costs too. Very frequent checks on low-stakes pages add noise, and some third-party services throttle or rate-limit aggressive checking. The goal is to match frequency to the real cost of a page being broken, not to maximize it everywhere.
It also matters what a 'check' does. A one-minute ping that only confirms a response is less valuable than a five-minute check that renders the page and verifies SSL, content, and journeys. Frequency and depth work together — a slightly less frequent but much deeper check often catches more real problems.
A simple rule: the more a minute of downtime costs, the more often you should check. Revenue-critical pages — checkout, signup, login, pricing — justify the fastest checks. Important but less time-sensitive pages can be checked less often, and purely informational pages least of all.
NorthDuty lets you check as often as every 1 minute on paid plans, with 5-minute checks on the free plan and 15-minute options where that fits. Because every check renders the page and covers SSL, DNS, blank-page detection, and errors in one pass, you get depth at every frequency rather than trading one for the other.
For the highest-stakes journeys, pair frequent health checks with scheduled user journeys that confirm the whole flow — not just the page — still works. That way your most expensive failure modes get the most attention, and your monitoring effort is spent where it protects the most revenue.
Match how often you check to how much a failure on that page actually costs.
Check as often as every 1 minute. These are directly tied to revenue and access, so fast detection pays for itself.
Every 1–5 minutes. High-visibility pages where a break is quickly noticed by visitors and search engines.
Every 5–15 minutes is usually enough for pages that matter but are less time-sensitive.
Every 15 minutes keeps an eye on them without adding unnecessary noise or load.
Spend your monitoring frequency where it protects the most value.
There is no single right monitoring frequency — there is the right frequency for each page, set by what a failure there actually costs. Revenue-critical pages deserve the fastest checks; quieter pages need less.
NorthDuty supports 1, 5, and 15-minute checks with full page-health depth at every interval, so you can tune frequency to the stakes of each page without giving up coverage.
Keep exploring the feature pages and commercial routes connected to this topic.
Feature
Monitor uptime every 5 minutes by default with HTTP, SSL, DNS, blank-page detection, broken resources, JavaScript errors, and API call tracking.
Explore Uptime MonitoringFeature
Learn how NorthDuty combines health checks, screenshot diffs, and editable user journeys in one website monitoring project.
Explore Website MonitoringFeature
Monitor website performance signals, response timing, and rendering context on the pages and journeys that affect revenue, leads, and trust.
Explore Website Performance MonitoringPricing
NorthDuty pricing for website monitoring: Free, $29 Starter, $79 Pro, $199 Business, and $499 Enterprise plans.
Compare pricing plansArticle
Learn what website downtime really costs in lost revenue, lost leads, support burden, and damaged customer trust.
Read Website Downtime CostMore NorthDuty guides on related website monitoring topics.
Article
Learn how to set up a public status page for your website — what to include, how to manage incidents, and how to schedule maintenance so customers stay informed.
Read How to Set Up a Public Status PageArticle
Learn how to monitor website uptime, choose the right checks, and catch downtime before it hurts traffic, leads, or sales.
Read How to Monitor Website UptimeArticle
Learn why websites can break without going fully offline and how website health monitoring helps detect silent failures.
Read Why Websites Break Without Going OfflineShort answers that summarize the practical takeaways from this guide.
Match frequency to the cost of downtime on each page. Revenue-critical pages like checkout and login justify checks as often as every minute, while informational pages can be checked every 5–15 minutes.
NorthDuty supports checks as often as every 1 minute on paid plans, every 5 minutes on the free plan, and 15-minute options — with full page-health depth at every interval.
Not necessarily. Very frequent checks on low-stakes pages add noise and load without much benefit. A slightly less frequent but deeper check often catches more real problems.
Yes. Increasing frequency temporarily around deploys, launches, and sales events helps you catch and respond to problems during your highest-risk windows.
Use NorthDuty to check each page as often as it deserves — up to every minute — with full page-health depth at every interval.
Free forever plan, no credit card required — add your base URL and monitoring starts in minutes.