<html><head><style> body {height: 100%; color:#000000; font-size:12pt; font-family:Times New Roman;}</style></head><body>If you're using firefox you might try getting the <a href="https://addons.mozilla.org/en-US/firefox/addon/966/">TamperData </a>plugin...it lets you see everything that is sent from your browser to the server, and from the server back to your browser. You might see some traffic that you weren't aware of that could account for the extra time.<br><br>----- Original Message -----<br>From: Matthew Nuzum <newz@bearfruit.org><br>To: Central Iowa Linux Users Group <cialug@cialug.org><br>Sent: Thu, 4 Nov 2010 08:15:27 -0500 (CDT)<br>Subject: [Cialug] decreasing website latency<br><br>I have a simple "hello world" php web page. When I do a wget https://.../index.php (it is an ssl website) it takes .477 seconds. Ping time is .060 seconds.<br><div>Any suggestions on what I can do to decrease latency? The apache server has (and needs) PHP. The phpinfo() page shows a lot of modules I don't need but I don't see them listed in php.ini. Currently using xcache, mod_php and mod_rewrite. Also, the SSL certificate is chained, does that affect performance? I'm very motivated to cut that latency in half or better. The site will be hosting dynamic content but I'm targeting an app that really needs to feel snappy and I think that will be challenging with half a second of latency.</div><br><div>/me does a quick test on a non-ssl website...</div><br><div>Ah, latency is down to .147 seconds on the http version of the site on the same server. So I guess my focus need to be on optimizing ssl. That also makes me wonder if wget is a good tool for testing ssl website latency.</div><br><div>I appreciate your suggestions, thanks.<br><br>-- <br>Matthew Nuzum<br>newz2000 on freenode, skype, linkedin, <a href="http://identi.ca" target="_blank">identi.ca</a> and twitter<br><br>"An investment in knowledge pays the best interest." -Benjamin Franklin <br><br></div><br><br></cialug@cialug.org></newz@bearfruit.org></body></html>