[Eru]

I was thinking of switching over to CloudFlare to see about improving the website's speed, but I don't want to do it unless it's loading slowly for some people.

This is my ping and page loads are super fast for me, but a Content Delivery Network might make it a bit faster for people who are further away from the server.

Pinging in-uo.net [50.22.104.139] with 32 bytes of data:
Reply from 50.22.104.139: bytes=32 time=17ms TTL=53
Reply from 50.22.104.139: bytes=32 time=18ms TTL=53
Reply from 50.22.104.139: bytes=32 time=17ms TTL=53
Reply from 50.22.104.139: bytes=32 time=18ms TTL=53

Ping statistics for 50.22.104.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms

Any thoughts? Complaints of slow speed? Etc.

[Elcid]

Mine in Australia and it responds fast enough....

Pinging in-uo.net [50.22.104.139] with 32 bytes of data:
Reply from 50.22.104.139: bytes=32 time=240ms TTL=46
Reply from 50.22.104.139: bytes=32 time=239ms TTL=46
Reply from 50.22.104.139: bytes=32 time=284ms TTL=46
Reply from 50.22.104.139: bytes=32 time=239ms TTL=46

Ping statistics for 50.22.104.139:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 239ms, Maximum = 284ms, Average = 250ms

[Boomrak Brewforge]

yeah Ive found website speed fast enough

[Taran]

It's fast enough for me

[Brandon]

Code:

Pinging in-uo.net [50.22.104.139] with 32 bytes of data:

Reply from 50.22.104.139: bytes=32 time=57ms TTL=54
Reply from 50.22.104.139: bytes=32 time=49ms TTL=54
Reply from 50.22.104.139: bytes=32 time=54ms TTL=54
Reply from 50.22.104.139: bytes=32 time=51ms TTL=54

Ping statistics for 50.22.104.139:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 57ms, Average = 52ms

No complaints here.

[Azzo]

Yeah the site is fine for me, Sydney Australia.

[hilbertsawhat]

Fast enough. Is YSlow complaing on CDNs?

[Atlas]

It's fast enough for me

lOl

I get 52ms avg

[Carding]

Fine for me.

[Taran]

Hehe Atlas, the website is hosted in the US so I actually ping around 190 to it.

[Raziel_]

Disparando in-uo.net [50.22.104.139] com 32 bytes de dados:
Resposta de 50.22.104.139: bytes=32 tempo=110ms TTL=49
Resposta de 50.22.104.139: bytes=32 tempo=110ms TTL=49
Resposta de 50.22.104.139: bytes=32 tempo=110ms TTL=49
Resposta de 50.22.104.139: bytes=32 tempo=110ms TTL=49

Estatísticas do Ping para 50.22.104.139:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 110ms, Máximo = 110ms, Média = 110ms

Works fine for me! The pages load really fast, no complaining.. from Brazil!

[Rob]

No issues here. One thing I did notice though is that you are only gzipping the php files. You should gzip all text (php,html,js,css).

Also, not a major thing, but you are only using ETags vs also using a Cache-Control/Expires header for static files. You should typically use both. When just using an ETag the browser still sends a request to the server for every static file, the server just sends back a 304 Not Modified if the ETags match, then the browser uses the file from cache. If you set a future Cache-Control/Expires header the browser will use the cache until expiration. Then the server can still send a 304 and set a new Expires header, and the browser will use the cache again.

Just by doing that you could eliminate 29 requests from the http://in-uo.net/forums page.