Seravo Plugin – Site Status
The site status page is an excellent way to get a quick overview of your site and its status. You can easily view the basic site information and statistics such as HTTP requests and the site's disk usage, as well as more detailed reports with the Go Access report that is available for each month. Additionally, you can see and test the status of caching for your site, manage the shadows linked to the site, and manage the built-in image optimizer's settings.
All of the postboxes on these pages are freely movable and can be organized in the way that best suits your individual workflows. They cannot be hidden, but closing a postbox will keep it minimized until it's manually opened again, which makes it handy if you rarely need certain information, but want to keep it at hand just in case.
Site information lists the basic details related to the site. Here you can see the site name, creation date, the plan the site is currently on, the contact details of your account manager if your site has an enterprise plan, and the technical contacts for the site. These contacts are especially important, as we use the email addresses added here as the point of contact in case your site experiences issues. We also use these to validate whether or not a specific person has the right to send us customer support requests related to the site. More information about the technical contacts can be found in the Seravo Plugin – Upkeep article, where you can also modify the contacts associated with your site.
HTTP Request Statistics
We don't sell server resources to our customers, but instead we measure the number of HTTP requests that are made each month. These HTTP request numbers are used to determine the suitable service plan for the site, so keeping an eye on these is useful for site owners as well.
An easy way to understand what HTTP requests are and why they matter, is to look at them as individual items being requested from our servers, and our servers providing the requested resource to the user's browser, that made the request when visiting your website. If, for example, your front page has 40 different items, elements, scripts and other components that together make the actual page itself, then each user who visits the front page will make 40 HTTP requests. That number usually goes down if caching is enabled, thus a repeat visit or another page might only create about four to five new HTTP requests. We highly recommend making sure your site is caching correctly to ensure the best performance without unnecessary costs!
Clicking the View report button allows you to see the more detailed report for each individual month.
Each plan has a set amount of disk space included, and in this postbox you can see a detailed report of how much disk space you're currently using and what it is being used for.
Do note, even though we shot the amount of data we've backed up, this does not count against your quota. We just want you to be able to see that there are backups being made and how much data we've backed up. We use incremental backups that are compressed after a more recent one is made, so the actual size of the backups varies highly.
If you see that your site has more than ten times the size of the /data/wordpress worth of backups, it's most likely that you are using a backup plugin. This causes multiple copies of the site being backed up to our system, which might cause trouble, especially if a backup needs to be restored. We recommend you read more about our recommended plugins and the plugins we consider unnecessary, banned and malicious in our documentation.
Caching is often one of the hardest things to get right on a website, which is why we've built a handy tool right into WordPress that allows you to quickly see the hit rate of your Redis memory cache and the Long-term HTTP cache. It also allows you to test your cache, so you can quickly see if something is wrong and the site is not caching correctly.
After pressing the Run Tests button, you can click the Toggle Details arrow to see the full details of our cache testing.
Staging environments, or shadows as we affectionately call them, are a convenient way to test modifications, updates and changes on sites, without actually having to test them on the live version of the site. Shadows are exact copies of the production site, but hidden from the public eye with the help of cookies. You can read more about shadows and how to use them in our developer documentation.
If you have shadows available for the site, they will be shown in the dropdown here, along with the SSH port, identifier and creation date. From here you can also reset the shadow by clicking the Move Data link. This means that the contents of the shadow will be overwritten by the current state of the production instance. Very useful for bringing new content from production to the shadow if you wish to see how it behaves with potential modifications.
There is also an option to have the shadow use a specific URL, such as a subdomain like staging.example.com. This can be requested from our customer service, but do note, that the shadow reset will overwrite the siteurl setting in the shadow, meaning that this should only be requested if you are comfortable with search-replace and know how WordPress handled siteurl in its options and the database in general.
This is where you can control the built-in image optimization tool that is available for all of our clients. More information about how you can use it to optimize the images on your site can be found in our Optimizing Images article. The simplest way? Just tick the Optimize Images box and click Save, we'll handle the rest.