A customer is ready to browse your CBD catalog, check dispensary hours, or place an order for cannabis seeds. Instead of your website, they see an error page. They may not try again. Knowing how to monitor website uptime gives you an early warning system, so a small technical issue does not turn into missed sales, support requests, and damage to your reputation.
For cannabis-related businesses, a website is often more than a marketing tool. It may be where customers read product information, verify store details, submit wholesale inquiries, or purchase legal hemp-derived products. Your site needs to be available when people need it, including evenings, weekends, and during a promotion.
What Website Uptime Actually Measures
Website uptime is the percentage of time your website is reachable and working as expected. A 99.9% uptime level sounds nearly perfect, but it still allows roughly 43 minutes of downtime in a 30-day month. Whether that is acceptable depends on what your site does. A simple informational site can tolerate more interruption than a WooCommerce store processing orders around the clock.
An uptime monitor checks your site from outside your hosting account. At a scheduled interval, it requests a page or service and records whether it receives a successful response. If the monitor cannot connect, gets an error, or receives an unexpected page, it sends an alert.
This distinction matters because a site can appear fine from your office while being unavailable elsewhere. Your browser may show a cached page, your local network may take a different route, or the issue may affect only a specific location. External monitoring gives you a customer-level view.
How to Monitor Website Uptime the Right Way
Start with an independent uptime monitoring service. Your host may track server health internally, and that is useful, but an outside monitor confirms whether visitors can actually reach your site. Choose a service that can check from multiple US locations and notify you by email, text message, mobile push alert, or a team communication channel.
For most small businesses, checking every five minutes is a practical starting point. It catches meaningful outages without creating excessive alerts. If your website produces frequent orders or leads, use one-minute checks. Faster intervals identify problems sooner, but they can also increase monitoring costs and create more alerts from short-lived network interruptions.
Do not monitor only your home page. The home page may load while the contact form, store, customer login, or checkout is broken. Set up separate checks for the pages that support revenue and customer service. For an ecommerce site, that usually means the home page, a product page, the cart, checkout, and a transaction test where appropriate.
A basic HTTP check confirms that a URL responds. A keyword check goes further by confirming that a specific phrase appears on the page, such as your business name or a heading unique to your site. This helps catch cases where the server returns a generic error page with a technically successful status code.
Monitor More Than a Green or Red Status
A site is not fully healthy simply because it responds. Your monitoring plan should cover the services that make the website usable.
Check HTTPS and SSL Certificate Status
An expired SSL certificate can cause browsers to display a frightening security warning. Visitors may leave immediately, especially when they are considering a purchase or entering contact information. Configure alerts well before certificate expiration, ideally 30 days ahead, and confirm that HTTPS redirects work correctly.
Watch DNS Resolution
DNS is the system that directs a domain name to the correct server. If DNS fails, your website and email can become unreachable even if the server itself is running normally. Monitor DNS resolution for your primary domain and any critical subdomains, such as shop, store, or mail.
Track Response Time
Uptime and speed are related but different. A site that takes 12 seconds to load may technically be online, yet customers will treat it as broken. Review response-time reports for sudden increases. A spike can point to a traffic surge, a poorly optimized WordPress plugin, database trouble, excessive bot traffic, or limited server resources.
Set a realistic response-time threshold. A lightweight page should respond quickly, while a large ecommerce page with many images and scripts may need a more forgiving limit. The goal is not to chase a perfect number. It is to spot a change from your normal performance before it affects customers.
Test the Customer Journey
For stores, the most valuable monitoring is often a synthetic transaction test. This simulates the path a customer takes, such as adding an item to a cart and reaching checkout. It can reveal issues that a simple page check misses, including payment gateway errors, broken shipping calculations, failed inventory updates, or a plugin conflict after an update.
Transaction monitoring takes more setup and may not be necessary for every business. If your website is primarily informational, page, form, and SSL checks may be enough. If online orders are central to your revenue, it is well worth considering.
Set Alerts That Your Team Will Actually Notice
An alert is useful only when it reaches someone who can act. Send critical downtime notifications to at least two people when possible. One person may be driving, asleep, helping a customer, or away from their phone. Use email for records, but use text or push notifications for urgent outages.
Avoid alert fatigue by requiring a second failed check before declaring a full outage. A single failed test can result from a temporary routing problem at the monitoring location. Two or three failed checks from separate locations are stronger evidence that customers have a real problem.
Your alert should include the affected URL, error type, time detected, monitoring location, and a link-free plain-language description of what failed. Keep the message short enough that someone can understand it from a phone screen. If your store checkout is down, that detail should be obvious immediately.
Build a Simple Downtime Response Plan
When an alert arrives, do not start changing settings at random. First, confirm the problem from a second device and a different network, such as a mobile connection. Check whether the issue affects the entire site or only a specific page, store function, or email service.
Next, review any recent changes. Common causes include WordPress core updates, plugin updates, theme edits, DNS changes, expired domains, firewall rules, and traffic spikes. If the issue began immediately after an update, restoring the last known good version may be faster than trying to troubleshoot a live outage under pressure.
Keep your hosting support contact details and account information available to the people who receive alerts. A useful support request states when the outage began, which URLs are affected, the error message, whether it occurs from more than one network, and what changed recently. That information shortens the back-and-forth and helps support teams investigate faster.
Automated backups are your safety net, not your monitoring system. Backups help you recover from failed updates, malware, accidental deletions, and data loss. Monitoring tells you that a problem is happening now. You need both.
Use Monitoring Reports to Improve Your Site
Do not look at your uptime dashboard only after something fails. Review reports monthly. Look for repeat incidents at the same time of day, slowdowns after particular marketing campaigns, or recurring failures tied to a plugin, payment service, or scheduled task.
A strong hosting setup should also make routine maintenance manageable. With cPanel access, current PHP versions, security controls, and dependable backups, you have more options when an issue occurs. Weed Hosts supports cannabis-focused businesses with hosting and responsive assistance designed for owners who need clear answers, not a maze of technical jargon.
Also consider the difference between a provider-side outage and a site-level issue. If the server is healthy but your WordPress site is failing because of a plugin conflict, changing hosts will not fix the immediate problem. On the other hand, recurring server instability, poor support response, or limited resources may be a sign that your current hosting plan no longer fits your business.
Your uptime target should match your business model, not a vague promise on a sales page. A local informational site may focus on avoiding long outages. A growing CBD store may need frequent checks, checkout testing, and immediate alerts. Start with the pages customers rely on most, assign someone to respond, and let your monitoring data show you where attention is needed next.