Most of the time the site here is snappy and smooth. There are times when it takes up to 1 minute to respond to even a page refresh.
Having my own co-located hosted webservers I recognize the difference between network latency, packetloss and application latency as well as being able to tell if the sluggishness is local or remote.
From what I've experienced, the issue here isn't the webserver but a router/gateway getting bogged down. When I was having long response times with this site I ran a few network diagnostics from this end and a few using remote hosts and even a proxy server.
I located a border router within the level 3 Inc. Colorado network that was causing the problem. It would be slow to respond but then timeout altogether. We must keep in mind that our data travels different routes to and from the server at random times.
From out west often our network traffic will be routed along the high line or through San Jose, CA, across NV-UT-CO then sent south to Phoenix where the FSJN web server is hosted. From the midwest and east, the traffic goes to CO as well then south to Phoenix.
What does all the gibberish mean in English?
From what I've seen the problem is the internet backbone traffic and
NOT the FSJN network or server.
Internet/Network issues are every bit as numerous as Jeep issues
Jim