• Priority: 0
  • Status: Closed
  • Theme: Venedor
  • Assigned To: Alex
  • Private: No
  • Open Date: 18.05.16, 19:45
  • Opened by: Eddie Piazza
  • Closed by: Alex
  • Closed on: 30.05.16, 12:54
  • Reason: Closed
  • Comment: Glad to help!

Ticket #9567 - Time To First Byte really slow - Venedor Optimization Needed !

Hi, We spent more than two days trying to find the reason of our slow loading speed in Prestashop.

We optimized all cache system and reduced all images, CSS, HTML and Javascripts.

We disabled ALL unnecessary modules from Prestashop, made some tests in debug mode and after hours of desesperation we decided to make tests with new clean installation.

Results with PH 1.6.1.4: Default Theme TTFB 1.24s / Venedor Theme TTFB 3.95s

There is not a problem related with files size, all site content is being loaded in logical timings. The problem is becoming from connection to the pages.

Tests with PS Default template: http://www.webpagetest.org/result/160518_GX_1935/1/details/

Test with PS Venedor template: http://www.webpagetest.org/result/160518_5Z_19D7/1/details/

I also attach images showing timings comparison

Please we need a solution because it seems we are coming back to 90’s in our site. RDSI party!

Comments

Eddie Piazza 18 May 2016, 19:50

 FS#9551  - Loading Time Fontend // https://support.promokit.eu/index.php?do=details&task_id=9551&project=14

By our tests we are proving that this loading torture is not coming from Backend configurations.
Please don´t modify our backend configs, they are already 90% optimized.

Alex 18 May 2016, 19:59

Hi. Really sorry for that but was our module “Facebook like box” module.
in the file /modules/pk_facebooklike/pk_facebooklike.php
changed the code

$ageInSeconds = 0;

to

$ageInSeconds = 3600;
Eddie Piazza 18 May 2016, 20:17

That parameter is already at 3600. Any other hint?

I also disabled Facebook module and still in the same TTFB time (4sec)

Anyway, is not a problem of page load time (in content). It´s a connection to page content problem.

Please check this: https://gtmetrix.com/reports/www.opengrow.es/LVLBNboa

Alex 18 May 2016, 20:39

Do you have a test site in some subfolder with the default theme? Here opengrow.es/order/es/ now I see Venedor as well.
We did tests and our theme has good performance comparing with the default theme.

Now your site with Venedor has good speed for me http://prntscr.com/b5mkd2
Home page of course much slower because of slides and other modules.
Please check Category and product page

Eddie Piazza 19 May 2016, 11:29

After directly disabling Facebook module website speeded up a bit. We reduced time to 2 seconds.

By trying to fix this problem I discover from other users a lot of Bugs in the system that have to be implemented for Venedor 2.3

Please, could you create a document taking all Fixes for other users and us correct all bugs until you release next version?

We are near to release our site and we would like to not have troubles in the moment of clients will start to enter in our site.

Thank you very much

Marek 19 May 2016, 13:04

Hi Eddie.
I see an issue in your back office what should be fixed. I suppose it could be a reason of slow loading. Please fix it and let me know, I’ll continue to on loading speed of your shop.
media.promokit.euscreenshotsscreencloudscreenshot20160519_130203.jpg

Eddie Piazza 19 May 2016, 13:27

It might be a bug because Index.php was there, I substituted it and now is fixed, and all folders and sub-folders from cache are in 777.

there are files also inside cache/smarty/cache and compile folders. So this message has to be buged

Marek 19 May 2016, 13:29

Ok, I’ll try to figure out why it appears

Eddie Piazza 19 May 2016, 13:31

Now I see Twitter module stop to work. not connecting. maybe because I disabled Facebook module… loading tweets…

Eddie Piazza 19 May 2016, 13:51

I don´t know if it´s you who is touching files now but suddenly I am receiving some errors from site.

Catalog → Products

Marek 19 May 2016, 13:58

Yes, I see. I’ll try to fix it too

Marek 19 May 2016, 15:17

To solve the issue with twitter we need to see into a server log file, and find there all errors related to /modules/pk_twitterwidget/ajax.php

Marek 19 May 2016, 15:24

As I can see here (see the link below), the main issue is with Revolution slider. I see you are using new version of Revolution slider. With previous version I don’t see such problem on our server and localhost.
https://www.dropbox.com/s/gesgr1w7w3n9eos/Screenshot%202016-05-19%2015.20.16.png?dl=0

Eddie Piazza 19 May 2016, 15:54

We will check this with revslider.

About twitter, we just saw that they changed the APP platform. Seems not easy to access to configs by this new system
https://dev.twitter.com/

Now it s needed to access by https://apps.twitter.com/app/

I restarted module, reinstalled and introduced twitter data. Still not working.

How can I help you to get more info about this problem?

Marek 19 May 2016, 18:41

To solve the issue with twitter we need to see into a server log file

Eddie Piazza 20 May 2016, 11:35

May I have an email for send you our login to our server by PM ?

Marek 20 May 2016, 11:36

marek@promokit.eu

Marek 20 May 2016, 11:53

Unfortunately there is no useful information in logs. I’ll continue o find a solution

Eddie Piazza 20 May 2016, 11:55

I disabled a lot of modules to try to reduce loading time. Maybe one of them is needed for Twitter module runs prefectly. But is strange because yesterday morning it was working perfectly and I didn t modify nothing in the backend.

Marek 20 May 2016, 12:09

When you try to access to the file modules/pk_twitterwidget/ajax.php through browser you should get blank page, like here http://venedor.promokit.eu/modules/pk_twitterwidget/ajax.php But there is an error http://www.opengrow.es/shop/modules/pk_twitterwidget/ajax.php Could you please ask your hosting provider? they should know a reason of that.

Eddie Piazza 20 May 2016, 12:47

Fixed, Because of some wrong folder´s permissions the server was locking the access to the file from browser. modules folder was in 777 and now is back to 755. All starts to run correctly again.

Marek 20 May 2016, 13:49

Great. Hope overall site performance is good as well now?

Eddie Piazza 20 May 2016, 15:52

Now is all right until we tested. But It could be nice to publish a list of all bugs and fixes founded by other users for V 2.2 until you release the 2.3 version.
I am sure I stil having some bugs that others already discovered and solved.
Thank you very much

Alex 20 May 2016, 19:05