Tech Bleg
Site speed is way, way down. I thought it might be the various scripts I have on the site so, one by one, I took each off to see if that would speed it up. No dice. Anyone have an idea why this site is so damn slow to load?
Site speed is way, way down. I thought it might be the various scripts I have on the site so, one by one, I took each off to see if that would speed it up. No dice. Anyone have an idea why this site is so damn slow to load?
Remember, I do this to entertain me, not you.
Uncle Pays the Bills
Find Local
|
June 27th, 2005 at 9:45 am
There is still a delay.
For me, from Detroit (in an auto company with *huge* ‘net connections), it takes 5-8 seconds to change from “Waiting for saysuncle.com” to “Transferring data from saysuncle.com”.
The transferring data takes between 1 and 2 seconds.
June 27th, 2005 at 10:39 am
It’s probably your hosting provider.
June 27th, 2005 at 10:42 am
It’s like your server.
It takes over 3 seconds for your server to return a response after the initial request:
$ time HEAD https://www.saysuncle.com/archives/2005/06/27/tech_bleg/
200 OK
Cache-Control: no-store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Connection: close
Date: Mon, 27 Jun 2005 14:41:44 GMT
Pragma: no-cache
Server:
Content-Type: text/html
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Last-Modified: Mon, 27 Jun 2005 14:41:44 GMT
Client-Date: Mon, 27 Jun 2005 14:41:48 GMT
Client-Peer: 63.247.133.128:80
Client-Response-Num: 1
X-Pingback: https://www.saysuncle.com/xmlrpc.php
X-Powered-By: PHP/4.3.10
real 0m3.114s
user 0m0.180s
sys 0m0.013s
June 27th, 2005 at 10:42 am
Er, that is, “It looks like”
June 27th, 2005 at 10:44 am
Check out http://www.websiteoptimization.com/services/analyze/
It’s a free page I use to check website performance. It can give some hints about ways to increase speed. It’ll give a list of recommendations at the bottom of the results page.
The only really odd thing I saw in your code was the following line:
I’m not sure what that is intended to do but that file returns a 404 not found error so it might be good to cut that from the template.
I also saw that you have two stylesheets being loaded. You’re pulling in both print.css and styles-site.css. Unless there’s a reason for having two you might gain a little bit of speed by consolidating them into css file. The reason I say that is because things loaded in the head of the document usually must be completely loaded before the browser will begin displaying the page.
Also, I agree with the previous commenter. I just ran a get on your home page (using wget) and saw it waiting at “HTTP request sent, awaiting response…” for 4-5 seconds. Once it got a response the speed was fine. I think either it’s a slow server problem, or for some reason the php code is running slowly. I don’t have any experience with wordpress so I don’t know what would be causing that. My assumption is that some script running server side is running slowly.
June 27th, 2005 at 10:45 am
I just thought it was you.
June 27th, 2005 at 10:45 am
It looks like my code snippet was cut out of my comment for some reason. My second paragraph was about the script tag that referenced src=”sayuncle_archive.html”.
June 27th, 2005 at 11:01 am
Thanks for the advice. Dunno how to make it stop pulling from one or the other sheet but i did lose the archives script. Also, sent a message to my host regarding response time.
June 27th, 2005 at 2:06 pm
Unless the Web browser is pretty braindead, it should only load the print stylesheet when actually printing. And you don’t want to combine the two – one is for output to screen and one is for output to printers.
Anyhoo, I think your speed problems are probably caused by your Web hosting provider or a link on the Internet that’s down. Your Web page didn’t suddenly become slower overnight.
June 27th, 2005 at 3:29 pm
Yeah, the link has been slow for a while.
June 27th, 2005 at 6:50 pm
I have had a 4-5 second delay to fully load image for a bit also. Nothing that really bothered me so did not mention it.
June 28th, 2005 at 1:44 pm
Les Jones,
You’re right about print.css. I somehow missed the media=”print” when I first looked at it.