Basically you can use our services to monitor websites. It is key for website owners and administrators that their websites are available continuously and function properly, regardless of what the websites are for. Company sites, product sites, blogs, forums, online shops, news portals, online applications, extranets - in all these cases users expect to have permanent access to data and functionalities.
Any disruption which is not immediately found and eliminated causes or increases users’ annoyance. This can have various consequences, be it a greater load on customer service or complaints and desertion.
We monitor websites regardless of the technology they were made in and there is no need for website owners or administrators to do anything so that the service can be started. That is because while establishing connection our system acts like an ordinary internet browser.
We say that a website is available if within a given time period there is a positive response from the server to the website’s URL address ("HTTP 200 OK"). Any other response or its lack (timeout) is considered a failure (of course after it is confirmed by additional monitoring stations).
Server response time is a sum of a few very short values (DNS name lookup time, connect time, pretransfer time, starttransfer time and redirect time) - and it's measured in milliseconds. These values are usually not noticeable, but they provide valuable insight into web server status and performance.
We measure these values with every availability test (i.e. up to 1440 times per day) and then we calculate hourly and daily averages. This data is visible in the user panel in the form of stacked bar charts.
For the last 24 hours you can check the hourly average values. Further into the past you can see daily averages. If the total response time is longer than the defined limit (10 seconds by default), a CONNECTION TIMEOUT failure is reported.
The availability of a website is not the only thing the monitoring mechanism can check. When the content monitoring feature is used, the monitored website is also checked against a defined phrase.
An example of such a phrase could be a HTML closing tag ("</html>"). If it is there, it means the website has loaded fully. That can also be a simple part of the websites’ dynamic content which confirms that the content is correctly downloaded from the base and displayed.
This functionality lets you test the functioning of simple forms, such as contact forms or login forms. A form (found at a defined URL address) is automatically completed with preconfigured data. Then the monitoring system ‘clicks’ the button to send the form and subsequently loads the result page and checks whether there is a predefined phrase on it. Only if this is the case, the proper functioning of the form is confirmed.
Speed of a website is an important value not only for increasingly impatient visitors, but also for Google, which promotes fast loading websites. Our system is capable of measuring the loading time of your entire page – along with all embedded styles, scripts and image files. Define an acceptable limit for your website loading time and we will let you know as soon as your website slows down and will load longer than it should.
In that case, among detailed information about the event you will also find a waterfall chart showing the loading times of all the elements of your website and a HAR file for optional further analysis using external tools.
Are you running an online store or provide services via a web app (SaaS)? If so, then you might want to monitor entire processes, say, in ecommerce, and spot problems at any stage they may appear at.
Define a multi-step testing scenario that our system will use to verify the proper working of your process. If something will stop working, you’ll learn immediately at which stage the problem occurs.
If your website contains files of special importance – such as critical legal documents or forms, we can monitor them for unauthorized changes. You will only need to generate a checksum of a valid file and our system will regularly compare the current checksum of the file on the website with the checksum of the original. Checksum inconsistency will mean that the file has changed – in that case, you will receive a notification immediately.
Less typical and more advanced functionalities can also be monitored. That, however, requires a dedicated solution.