Quote:
|
I'm not sure if google is the best page to gauge results from, since the page is so "light".
|
Yes, you're right - it is short on bytes. It's really there to check that my monitor machine isn't suffering from some sort of interface problem when each test is done. The test URLs are read every hour. If it took, say, 30 seconds to read each test page then I would be suspicious that there was a problem with the monitoring machine or its connection to the net. (This hasn't happened yet).
Quote:
|
You say you use 2 different hosting co's for each domain. Are the 2 domains the same site? Did you do testing for both?
|
I have been monitoring my own website's host and also the (different) host of another website (as well as Google for reference). The monitor reads a static page and a dynamic page from each host - to indicate both web server and database server performance.
The aim is to see just how often my shared host takes an excessive time to serve a page. By excessive I mean long enough that a typical visitor will give up and go somewhere else.
Sadly, this has been happening 7% of the time recently - so I expect I'm losing that kind of percentage of visitors.
The thing is, the uptime of my host has been 100% in the same period - so uptime doesn't tell you what you want to know about hosting performance.
I guess this is a loading issue - too many websites sharing the same hardware. The other host is doing a lot better - wish I'd chosen that one!