Problem with my website: loads slow

[ymk101]

Hi all

I have a problem with my site (bayrings.co.uk) it takes ages to load. the developer of my site and he also hosting it said this is the best it can be for this site. what your take on this?

Thank you

 

The speed seems fine for me at the moment, as you use ASP.net the first time the site is called the .aspx page needs to be compiled and cached on the server. It may be worth asking your developer if he can pre-compile the .aspx pages if they are not already.

 

[adamscomputers07]

Loaded in less than 5 secs here!

 

[Optegris]

It's reasonably quick but your pings are quite high:

Pinging bayrings.co.uk [65.99.201.96] with 32 bytes of data:
Reply from 65.99.201.96: bytes=32 time=171ms TTL=107
Reply from 65.99.201.96: bytes=32 time=179ms TTL=107
Reply from 65.99.201.96: bytes=32 time=313ms TTL=107
Reply from 65.99.201.96: bytes=32 time=179ms TTL=107

And from one of my servers:

Reply from 65.99.201.96: bytes=32 time=140ms TTL=112
Reply from 65.99.201.96: bytes=32 time=137ms TTL=112
Reply from 65.99.201.96: bytes=32 time=147ms TTL=112
Reply from 65.99.201.96: bytes=32 time=143ms TTL=112

and a tracert indicates quite a few hops to your US server by the looks of things:

1 <1 ms <1 ms <1 ms alice-rose.ukcore.as33970.net [195.242.213.254]
2 <1 ms <1 ms <1 ms vl380.ccr01.lon08.atlas.cogentco.com [149.6.80.2
21]
3 173 ms 8 ms 218 ms vl3496.mpd01.lon01.atlas.cogentco.com [130.117.1
.145]
4 <1 ms <1 ms <1 ms vl3490.mpd01.lon02.atlas.cogentco.com [130.117.2
.218]
5 <1 ms <1 ms <1 ms verio.lon02.atlas.cogentco.com [130.117.14.102]
6 80 ms 79 ms 79 ms p64-2-1-0.r21.nycmny01.us.bb.gin.ntt.net [129.25
0.2.38]
7 86 ms 86 ms 85 ms as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.9
]
8 120 ms 121 ms 121 ms p64-3-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.25
0.5.24]
9 131 ms 121 ms 120 ms po-1.r02.dllstx09.us.bb.gin.ntt.net [129.250.2.1
54]
10 133 ms 132 ms 132 ms xe-8-4.r03.dllstx09.us.ce.gin.ntt.net [157.238.2
24.34]
11 128 ms 128 ms 128 ms border4.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
191.94]
12 133 ms 132 ms 133 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.
189.10]
13 133 ms 133 ms 132 ms 206.123.64.34
14 132 ms 132 ms 132 ms 206.123.64.122
15 144 ms 148 ms 136 ms 65.99.244.246
16 144 ms 147 ms 137 ms cp.d3hosting.com [65.99.201.96]
Trace complete.

As a comparison, this is one of my clients servers:

Pinging intotheblue.co.uk [89.238.133.121] with 32 bytes of data:
Reply from 89.238.133.121: bytes=32 time=91ms TTL=115
Reply from 89.238.133.121: bytes=32 time=68ms TTL=115
Reply from 89.238.133.121: bytes=32 time=48ms TTL=115
Reply from 89.238.133.121: bytes=32 time=47ms TTL=115
Ping statistics for 89.238.133.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 91ms, Average = 63ms

Note the difference in time for each ping?

 

[ymk101]

Thanks for your help. I have the Alexa toolbar installed and its says 63% of sites are faster than my site. when you select a ring from the site and then you make you selection from the drop downs after every selection the page reloads, is that normal in my opinion the all proses is to slow, but my developer/ host cant help me on that one.

Openmind can you tell me more about pings and what can i do about this? 1st time I heard of this.


Thanks

 

[Spire]

Hi

With it being an Asp.Net site you could keep it warm by pinging it evey 10mins, that will help with the first time load.

I run a little prog on my own server that keeps all my sites warm.

 

Do you really expect anyone to read all that Phil ?

Loads OK for me.

Earl

 

[Dwebs-Ltd]

Home page is 305kb quite a large page especially when loading from a USA based server. A good website home page is around 100kb if not less. You don't want to leave clients waiting for the page to load. .NET Sites are usually large so there might be nothing you can do about the page size.

You would be better off using a UK host, you will get a quicker response.
e.g. getting from a UK ISP to your site would take around 120-140ms from a UK based host it will be between 18-35ms.

That would boost the response time connecting to the site especially if your customer base is UK based.

I have also sent you a PM with something for you to try out!

 

[DotNetWebs]

.NET Sites are usually large so there might be nothing you can do about the page size.

ymk101 does have a HUGE ViewState. The chances are that this could be reduced significantly by disabling the ViewState where not required.

[ymk101] I would suggest you ask you developer to consider this.

Regards

Dotty

ps if anybody does not know what I mean, view the source of ymk101's site, the problem will be immediately obvious. Then view the source and compare my Visit Horsham site which has the ViewState disabled for the home page.

 

[Optegris]

Openmind can you tell me more about pings and what can i do about this? 1st time I heard of this.


Thanks

A ping is simply a small packet of data that can be sent to a server. The server then responds and send back the same packet to the sender with the time taken for the round trip.

This time is very useful for not just making sure a server is alive and well but also for measuring how long the data takes to travel back and forth. It does give a reasonable indication of speed. The longer the time, the longer a site will take to load.

There are a lot of other factors in play but this is a non-techy explanation

Do you really expect anyone to read all that Phil ?

Loads OK for me.

Earl

Not really but I was feeling geeky

 

[tommy]

Your developer seems to be using a lot of the RadAjax calls which are near over 50k each (you have 3 on the homepage).

you have 5 images over 15k and 2 over 25k

You have the viewstate showing, he can change it so it doesnt display

how many nested tables?

Also check the SQL and make sure he isnt doing Select * from tablename

 

[Spire]

When I hosted in the USA on a cheap as chips pile em high sell em cheap host, I suffered with a slow Asp.net site, so I set about it and cached everything I possibly could, eliminated Viewstate by storing it in session on the server, examined all my Stored procedures to ensure that only the data I required was selected, and constantly pinged the site every 2 mins to ensure the site was warm.

Doing the above made quite a difference, but even so I eventually moved to UK host which charges quite a bit more than the US but then the performance is substantially better.

 

[RayB]

I often wondered about this stuff - and I still am

It's reasonably quick but your pings are quite high:

Pinging bayrings.co.uk [65.99.201.96] with 32 bytes of data:
Reply from 65.99.201.96: bytes=32 time=171ms TTL=107
Reply from 65.99.201.96: bytes=32 time=179ms TTL=107
Reply from 65.99.201.96: bytes=32 time=313ms TTL=107
Reply from 65.99.201.96: bytes=32 time=179ms TTL=107

And from one of my servers:

Reply from 65.99.201.96: bytes=32 time=140ms TTL=112
Reply from 65.99.201.96: bytes=32 time=137ms TTL=112
Reply from 65.99.201.96: bytes=32 time=147ms TTL=112
Reply from 65.99.201.96: bytes=32 time=143ms TTL=112

and a tracert indicates quite a few hops to your US server by the looks of things:

1 <1 ms <1 ms <1 ms alice-rose.ukcore.as33970.net [195.242.213.254]
2 <1 ms <1 ms <1 ms vl380.ccr01.lon08.atlas.cogentco.com [149.6.80.2
21]
3 173 ms 8 ms 218 ms vl3496.mpd01.lon01.atlas.cogentco.com [130.117.1
.145]
4 <1 ms <1 ms <1 ms vl3490.mpd01.lon02.atlas.cogentco.com [130.117.2
.218]
5 <1 ms <1 ms <1 ms verio.lon02.atlas.cogentco.com [130.117.14.102]
6 80 ms 79 ms 79 ms p64-2-1-0.r21.nycmny01.us.bb.gin.ntt.net [129.25
0.2.38]
7 86 ms 86 ms 85 ms as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.9
]
8 120 ms 121 ms 121 ms p64-3-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.25
0.5.24]
9 131 ms 121 ms 120 ms po-1.r02.dllstx09.us.bb.gin.ntt.net [129.250.2.1
54]
10 133 ms 132 ms 132 ms xe-8-4.r03.dllstx09.us.ce.gin.ntt.net [157.238.2
24.34]
11 128 ms 128 ms 128 ms border4.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.
191.94]
12 133 ms 132 ms 133 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.
189.10]
13 133 ms 133 ms 132 ms 206.123.64.34
14 132 ms 132 ms 132 ms 206.123.64.122
15 144 ms 148 ms 136 ms 65.99.244.246
16 144 ms 147 ms 137 ms cp.d3hosting.com [65.99.201.96]
Trace complete.

As a comparison, this is one of my clients servers:

Pinging intotheblue.co.uk [89.238.133.121] with 32 bytes of data:
Reply from 89.238.133.121: bytes=32 time=91ms TTL=115
Reply from 89.238.133.121: bytes=32 time=68ms TTL=115
Reply from 89.238.133.121: bytes=32 time=48ms TTL=115
Reply from 89.238.133.121: bytes=32 time=47ms TTL=115
Ping statistics for 89.238.133.121:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 91ms, Average = 63ms

Note the difference in time for each ping?

 

Not really but I was feeling geeky

Whats a Geek urn ?

 

[Dwebs-Ltd]

When I hosted in the USA on a cheap as chips pile em high sell em cheap host, I suffered with a slow Asp.net site, so I set about it and cached everything I possibly could, eliminated Viewstate by storing it in session on the server, examined all my Stored procedures to ensure that only the data I required was selected, and constantly pinged the site every 2 mins to ensure the site was warm.

Doing the above made quite a difference, but even so I eventually moved to UK host which charges quite a bit more than the US but then the performance is substantially better.

Exactly UK hosts don't tend to be to cheap or oversell and performance is usually far higher!