DARKF3D3 Posted January 3, 2015 Share Posted January 3, 2015 My website it not slow at all, in fact it load in 2,3 seconds. But I'm have a cloud server with multiple cpu and 2gb of ram, and actually the resource usage is low. And the problem is that the response time it's 1,3 seconds, while the remaining second load the rest of the page. How can I identify the cause of this slow response time? The website is in signature. Link to comment Share on other sites More sharing options...
'Woger Posted January 3, 2015 Share Posted January 3, 2015 (edited) If I do a speedtest it looks ok indeed. It's just the time to first byte which is slow. http://www.webpagetest.org/result/150103_3P_FPV/ I think this is a problem on the server side and can be a lot of things. slow disks, badly configured cache, slow mysql server, etc. I guess you allready tried emptying the cache dir? Do you have ssh access to the server? You can check the size of the mysql database size. Edited January 3, 2015 by 'Woger (see edit history) Link to comment Share on other sites More sharing options...
selectshop.at Posted January 3, 2015 Share Posted January 3, 2015 (edited) Site is not slow, but you have a TTFB (time to first byte problem). This could be a problem on the server where your domain is hosted or a distance problem between request and first view. Try to ping the IP of your domain and you will see how many server the request has to go/trespass first and look for your page. You should optimize this, this means minimize the way. Edited January 3, 2015 by selectshop.at (see edit history) Link to comment Share on other sites More sharing options...
DARKF3D3 Posted January 4, 2015 Author Share Posted January 4, 2015 (edited) These are my performance settings: SMARTY Template compilation: Recompile templates if the files have been updated Cache: YES CCC (COMBINE, COMPRESS AND CACHE) Smart cache for CSS: YES Smart cache for JavaScript: YES Minify HTML: YES Compress inline JavaScript in HTML: YES Move JavaScript to the end: YES Apache optimization: YES CIPHERING Algorithm: Use Rijndael with mcrypt lib. (you must install the Mcrypt extension) CACHING Use cache: No I also tried empy cache from ADVANCED PARAMETERS >> PERFORMANCE I can't ping the domain, it always show expired request. Edited January 4, 2015 by DARKF3D3 (see edit history) Link to comment Share on other sites More sharing options...
selectshop.at Posted January 4, 2015 Share Posted January 4, 2015 You don't have a performance problem on your site. The problem is the TTFB, which is a problem of response to the first byte. The reason for this could be a hosting server on the other end of the world. For better performances you should, if possible, host in your country. The reason for this is that your domain (dns server) will approach your hosting server quicker, without trespassing inumerous outhr servers in the world for to than open your site the first time (TTFB - time to firs byte). I don't presume that your DNS server is having a problem (it could be, but it is really very rarely). So the bad performance on the first byte could be the trespassing of several servers before your site is opened first time. If you cannot ping, so there must be a firewall on a server blocking the service (bad !). use traceroute for ex: http://tools.pingdom.com There you will see too how many servers the request is trespassing. 16 hops and max 67 ms response time on some slow servers. Here you can work on it to minimize. Your Prestashop is hosted on an Italian server, or one abroad ? BTW i will don't really take care of it, cause the only thing you can do is to have a better TTFB, all other possibilities are done cause as I can see you are using smart caching and compression. For the TTFB problem you can do nothing, it is a hosting problem. 1 Link to comment Share on other sites More sharing options...
DARKF3D3 Posted January 4, 2015 Author Share Posted January 4, 2015 (edited) Hi selectshop, the server it's phisically placed in the same conuntry (Italy). These are the detail of the first line of the pingdom report: DNS 76ms Connect 102ms Send 0ms Wait 1,42s Receive 27ms Total 1,62ms So almost the 90% of the time is the WAITING, this couldn't be a problem with PS performance, like slow query or something similar? Edited January 4, 2015 by DARKF3D3 (see edit history) Link to comment Share on other sites More sharing options...
'Woger Posted January 5, 2015 Share Posted January 5, 2015 You have some sort of cache enabled. What happens when you enable APC in cache? Do you know if you have some kind of php accelarator enabled on the server. Link to comment Share on other sites More sharing options...
selectshop.at Posted January 5, 2015 Share Posted January 5, 2015 (edited) I presume the server is using fast-cgi (in combination with nginx) - see webpagetest.com. In this case you cannot use APC or other accelarators together. APC or other Accelerators are not faster than fast-cgi (+combination of nginx). The use of fast-cgi and nginx are for big sites the optimal performance I've got till now. My site has about 10.000 products. For sites with 2.000 products you will not notice any performance difference. The problem is on TTFB and not on cache. And this should be solved. Perhaps there is a performance problem on the DNS-Server. You have to contact first your provider and than the hoster of your DNS. On one of my site I had too a performance problem on the DNS server, but as I told this is a case in 1 million. DNS 76ms Connect 102ms boths values are too high. DNS should 4mx and connect not more than 24ms. Edited January 5, 2015 by selectshop.at (see edit history) Link to comment Share on other sites More sharing options...
selectshop.at Posted January 6, 2015 Share Posted January 6, 2015 See a very simple and good topic about TTFB problem: http://www.websiteoptimization.com/speed/tweak/time-to-first-byte/ Link to comment Share on other sites More sharing options...
DARKF3D3 Posted January 6, 2015 Author Share Posted January 6, 2015 The DNS value doesn't seem high to me. I testest some other website and all they're similar value, only big website like facebook, amozon and similar have really low value. I think the best problem is the "wait" time, infact while dns and connect are less than 200ms, the wait time is between 2 and 2 seconds. PS database weight 366.6 MiB with 3,043,682 tables. These are the bigger tables: ps_connections 994.147 117.9 MiB ps_connections_source 548.231 132 MiB ps_search_index 181.676 4.9 MiB ps_statssearch 176.378 8.6 MiB ps_search_word 25.723 1.4 MiB Meanwhile i asked my provider to enasle the slow qury report. Link to comment Share on other sites More sharing options...
Recommended Posts