Jump to content

[SOLVED] Website extremely slow


Recommended Posts

Hi ,

 

Please can someone help me with this site as it's too slow. The website url

is www.mefie.co.uk and is using prestashop 1.4.8.2. The following are the

settings in the performance tab.

 

Smarty

Force Compile: No

Cache :Yes

 

CCC (all set to use ccc)

Smart cache

Smart cache and Javascript

Minify HTML

Compress inline javascript in html

 

Ciphering

Use Rijndael with mcrypt lib.

 

Caching

No

 

post-413573-0-94656500-1350906956_thumb.jpg post-413573-0-15651800-1350907297_thumb.jpg

 

 

Many thanks

 

Newbie101

Link to comment
Share on other sites

its weird!

 

try to ping your website from your computer. Maybe it's problem with your connection. For me and others site works great without any delays.

 

so, open command (on windows) and type: "ping www.mefie.co.uk -t" and paste here several lines of logs

Link to comment
Share on other sites

Hi Vynx, thanks for info "gtmetrix". This is what it says.

Page load time: 28.12s

Page Speed Grade:

(61%) grade D.

 

 

What's the recommended speed please.

 

average website is 74% to 75% , so try to tuning to chase that number...

 

its weird!

 

try to ping your website from your computer. Maybe it's problem with your connection. For me and others site works great without any delays.

 

so, open command (on windows) and type: "ping www.mefie.co.uk -t" and paste here several lines of logs

 

it could be wrong network routing ...

Link to comment
Share on other sites

ping www.mefie.co.uk -t

 

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Users\AMPONSAH>ping www.mefie.co.uk

 

Pinging mefie.co.uk [70.33.246.110] with 32 bytes of data:

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=2188ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Link to comment
Share on other sites

ping www.mefie.co.uk -t

 

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation. All rights reserved.

 

C:\Users\AMPONSAH>ping www.mefie.co.uk

 

Pinging mefie.co.uk [70.33.246.110] with 32 bytes of data:

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=104ms TTL=56

Reply from 70.33.246.110: bytes=32 time=2188ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

Reply from 70.33.246.110: bytes=32 time=105ms TTL=56

 

logs looks fine, only one packet with time 2000+ .

try to routing test:

 

in command type:

tracert www.mefie.co.uk

 

you've got static IP or dynamic? Maybe try to restart your network connection.

 

ps. have you tested site loading speed in other web browsers?

Edited by vekia (see edit history)
Link to comment
Share on other sites

Maybe you have a similar problem as my host (Bluehost): CPU throttling. That means that they think that you use too much CPU power and for that reason switch off the CPU for a few seconds now and then. Added up to 1800 seconds a day for me. They claim that it doesn't effect your speed but you can notice it very well: most of the time the site is fast and then suddenly it (almost) doesn't load.

Link to comment
Share on other sites

The only cron script I have is to keep mcached alive as it tends to be swapped out. There are no special cpu intensive scripts as far as I know. If you google on "Bluehost cpu throttling" you will see that there seems to be a lot of arbitrariness in who gets throttled. I found even someone who claimed that his Joomla blog with 60 visitors a day was throttled.

Link to comment
Share on other sites

@ Benjamin Utterback: sure, that happens every day. Unfortunately they have just removed the long term statistics but things seem only to get worse. Here is my latests stat: 3000 seconds blocked yesterday. In the worst hour I was a third of the time offline.

 

 

wow is all I can say maybe new host time.. That really is a lot to be blocked?

Link to comment
Share on other sites

×
×
  • Create New...