Does the homepage respond?
A basic uptime check requests an address at intervals and records whether it receives an acceptable response. It can help identify availability problems at that address. The checking interval matters: an hourly check cannot prove that the site was continuously available between checks.
Do the other pages respond correctly?
Page monitoring examines more addresses. A homepage might return 200 while a contact page returns 404 or a service page returns 500. Checking discovered pages helps reveal these differences. A public HTML report can also flag a missing title and show redirects or other metadata worth reviewing.
Can a customer actually complete a task?
For that question, use a browser journey test or perform the task yourself. A contact form can load normally but fail when submitted. A checkout can show a healthy page while payment processing fails. Neither a successful HTTP response nor a page title proves that these flows work.
Where Website Oversight fits
We schedule hourly homepage checks and daily checks of up to 100 discovered public pages per website. Availability charts describe recorded checks, not uninterrupted uptime. Confirmed HTTP errors and missing titles can trigger alerts after retries.
We do not run browser JavaScript, submit forms, test payments or inspect private pages. If your business needs minute-by-minute outage detection or transaction testing, use a tool with those capabilities alongside or instead of this service.
A practical choice
- For a small public brochure site: scheduled page checks plus manual contact-form tests may be useful.
- For an online shop: prioritise checkout journey tests as well as page availability.
- For a JavaScript application: use tests that actually render the app and exercise important flows.
Compare our full coverage guide with your needs, or follow the maintenance checklist.