ThisCalculator

Everyday

Monitor WordPress Server Uptime & Load

Updated · Standard formula, shown below

This guide shows you how to keep an eye on your WordPress server’s uptime and load, so you can catch problems before visitors do. You’ll learn to set up free or low-cost monitoring tools, interpret the key metrics, and know what to do when something looks wrong. No advanced sysadmin skills are needed, but you should have basic access to your hosting control panel or command line.

What You’ll Need

  • Access to your WordPress hosting control panel (cPanel, Plesk, or custom) or SSH access to the server.
  • A free account with an uptime monitoring service (like UptimeRobot, HetrixTools, or Better Uptime).
  • Optional: A free account with a server monitoring service (like Netdata Cloud, Grafana Cloud, or a simple cron-based script).
  • Basic familiarity with reading graphs and logs.

Step-by-Step

  1. Set up an external uptime monitor. Go to your chosen uptime service and create a new monitor. Enter your WordPress site’s URL (e.g., https://example.com) and choose a check interval (1 minute for free plans is common). The service will ping your site from outside and alert you if it can’t reach it.
  2. Add a second monitor for a critical page. Create another monitor for a page that exercises the database, like your homepage or a WooCommerce shop page. This catches cases where the server is up but WordPress is erroring out.
  3. Configure alert channels. In the uptime service, set up email, SMS, or push notifications (e.g., via mobile app) so you get alerted when a monitor goes down. Test an alert by pausing the monitor or using the service’s test feature.
  4. Install a server load monitor. If you have SSH access, install a lightweight agent like Netdata (one-line script) or use a service like Grafana Cloud with the Prometheus node exporter. If you don’t have SSH, check if your hosting control panel has a “Server Health” or “Resource Usage” section.
  5. Check load average and CPU usage. In your monitoring dashboard, look for the load average (1, 5, 15 minutes) and CPU usage percentage. For a single-core server, load average above 1.0 means the CPU is saturated. For multi-core, divide by the number of cores.
  6. Watch memory and swap usage. Keep an eye on RAM usage and swap (virtual memory). If swap is being used heavily, your server is running low on memory, which can cause slow responses.
  7. Monitor disk I/O and inodes. High disk I/O (reads/writes per second) can indicate database issues. Also check disk space and inode usage—a full disk or exhausted inodes will cause WordPress to throw errors.
  8. Set up alerts for load thresholds. In your server monitoring tool, create an alert that triggers when load average exceeds a reasonable threshold (e.g., 80% of cores) for more than 5 minutes. This gives you time to act before the site becomes unresponsive.
  9. Review logs regularly. Check your WordPress debug log and server error logs (e.g., /var/log/nginx/error.log or /var/log/apache2/error.log) at least weekly. Look for repeated errors, slow queries, or signs of an attack.
  10. Document a response plan. Write down what you’ll do if an alert goes off: restart the web server, check for a plugin conflict, scale resources, etc. Keep this handy so you don’t panic during an outage.

Common Mistakes

  • Monitoring only the server IP, not the website. The server can be up while WordPress is down (e.g., database connection failure). Always monitor a URL that loads WordPress.
  • Ignoring load average trends. A single spike may be harmless, but a consistent upward trend means you need to optimize or upgrade.
  • Not setting up alerts. Monitoring without alerts is like having a smoke detector with no battery—you won’t know there’s a problem until it’s too late.
  • Using too-short check intervals on free plans. Free uptime services often have minimum intervals of 1 minute; setting it to 5 minutes is fine and avoids false alarms.
  • Forgetting to monitor disk space. A full disk can crash your site silently. Include disk usage in your checks.

Tips

  • Use a monitoring service that offers a public status page. It keeps your users informed during outages and reduces support tickets.
  • Set up a “maintenance mode” page that you can quickly enable if you need to take the site down for work—this prevents false alarms from your uptime monitor.
  • For WordPress-specific issues, install a plugin like Query Monitor to see slow database queries, but don’t leave it active on a production site—use it only when troubleshooting.
  • If you’re on a shared host, you can’t install server agents, but you can still use WordPress plugins that report site health and uptime (e.g., Jetpack).
  • Keep a log of all alerts and what you did to resolve them. This helps you spot patterns.

Troubleshooting

You get an alert but the site loads fine for you. This often happens because the monitor is located in a different region and your server is blocking its IP. Whitelist the monitoring service’s IP ranges or ask your host to do so.

Load average is high but CPU is low. This could indicate heavy I/O wait (disk bottleneck) or too many processes waiting for locks. Check disk I/O and database slow queries.

Uptime monitor says “down” but the site is up. The monitor might be checking a URL that returns a 404 or a redirect. Make sure the monitor follows redirects and expects a 200 status code.

Server monitor shows memory usage near 100% but the site is fast. Linux uses free RAM for caching, so high memory usage isn’t always bad. Look at the “available” memory, not just “used”.

No alerts are coming through. Check your email spam folder, or test the notification channel. Some free services have a delay on email alerts; use a mobile app for instant notifications.

You can’t install a server agent. If you’re on managed WordPress hosting, they often provide built-in monitoring in their dashboard. Contact support for a link to it.

Frequently Asked Questions

Q: How often should I check my server load?
A: For a small site, a daily glance is enough. For a busy site, set up real-time alerts and review trends weekly.

Q: What is a good load average for my WordPress server?
A: For a single-core server, keep load below 1.0. For a quad-core, below 4.0. Sustained loads above that mean you’re over capacity.

Q: Can I monitor uptime for free?
A: Yes, services like UptimeRobot offer free plans with 50 monitors and 5-minute intervals. That’s plenty for a small site.

Q: What’s the difference between uptime and load monitoring?
A: Uptime monitoring checks if your site is reachable from the internet. Load monitoring tracks server resources (CPU, memory, disk) to predict and diagnose performance issues.

Q: Do I need to monitor both the server and the website?
A: Yes, because they can fail independently. A server can be up but the website down due to a plugin error, or the server can be overloaded while the website still loads slowly.

Q: How do I know if my monitoring is working?
A: Most services send a test alert when you set up. You can also temporarily pause your web server for a minute and see if the alert fires.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.