Welcome to the LimeSurvey Community Forum

Ask the community, share ideas, and connect with other LimeSurvey users!

Very slow rendering of first page

More
8 years 9 months ago #145293 by bruce78
Hi guys, I'm finding that the first page of a survey takes about 25 seconds to load in both FF and Chromium. Once it's loaded, the survey progresses at a reasonable speed but not as fast as I'd like...

Here's a link to the survey with some pre-filled answers...

data-2.brandreflections.com/index.php/76...5X735X51084SQ2=Email

I've just upgraded to 2.5 and I'm using the default theme. When I was running 2.06 LTS, the survey would load in about 2 - 5 seconds so I don't know what's changed?

I've got a variety of ideas as to why the survey might be slow but if anyone has any ideas, questions or pointers, that would be great...
The topic has been locked.
More
8 years 9 months ago - 8 years 9 months ago #145352 by DenisChenu
You still have a 2.6/2.06 version ?

If yes, or if you can create another one with the same survey (on data-test.... for example) : report the bug with the speed comparaison using a "speedometer" (firefox or chrome have some in Developper tools).

If no : you can report bug, but it will have to be convincing . Put a clear example is really more convincing.

PS : i think you can "downgrade" to a 2.6lts version without issue : but the best is to report the bug before.
PS2: i can confirm the speed :ohmy:

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. - Professional support - Plugins, theme and development .
I don't answer to private message.
Last edit: 8 years 9 months ago by DenisChenu. Reason: PS2 + Capture
The topic has been locked.
More
8 years 9 months ago #145353 by bruce78

DenisChenu wrote: You still have a 2.6/2.06 version ?

If yes, or if you can create another one with the same survey (on data-test.... for example) : report the bug with the speed comparaison using a "speedometer" (firefox or chrome have some in Developper tools).


Thanks Denis, so are you saying that if I export the survey and run it on a 2.6/2.06 version and it's faster, then I can report the bug given the speed difference between the 2 versions?
The topic has been locked.
More
8 years 9 months ago #145354 by DenisChenu
Hi,

I think if server was not updated elsewhere, and 2.6 is really speediest than 2.5X : this bug MUST be reported. But it's better to have a "realtime" comparaison between the 2 versions.
Without compare, i think bug must be reported, but sometimes it's still hard to fix speed with big survey.

You don't have any plugin activated too ?

:)

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. - Professional support - Plugins, theme and development .
I don't answer to private message.
The topic has been locked.
More
8 years 9 months ago #145355 by bruce78

DenisChenu wrote:
I think if server was not updated elsewhere, and 2.6 is really speediest than 2.5X : this bug MUST be reported. But it's better to have a "realtime" comparaison between the 2 versions.
You don't have any plugin activated too ?


Ok, I'll setup a 2.6/2.06 LTS version in the next day or two to compare...

I don't know if you're into javascript but this is the new code I have inserted into the majority of the questions to allow respondents to 'auto-advance' when they click a response (I'm using one question at a time)... This code is a bit different and longer than what I used in 2.06...
Code:
<script type="text/javascript" charset="utf-8">
$(document).ready(function(){
 
  $('tr.radio-list input.radio').bind('click', function () {      
    var thisArray = $(this).closest('table');
    if($('input.radio:checked', thisArray).length == $('tr.radio-list', thisArray).length) {
      $("#movenextbtn,#movesubmitbtn").delay(1).click();
    }
  });
 
  $(".list-dropdown select").change(function(){
    if($(this).val()!="" &amp;&amp; $(this).val()!="-oth-"){
    $("#movenextbtn,#movesubmitbtn").delay(1).click();
    }
  });
 
  $('#movenextbtn, #movesubmitbtn').hide();
 
});
</script>
 

While this is what I used in 2.6/2.06. Do you think this might be the cause of the delay?
Code:
<script type="text/javascript" charset="utf-8">     $(document).ready(function(){      $('#movenextbtn, #movesubmitbtn').hide();   });  </script>
The topic has been locked.
More
8 years 9 months ago #145358 by DenisChenu
No,

I think more on plugin using 'beforeSurveyPage' PHP plugin only. Because here : it's not javascript, it's PHP

Page size is not heavy, but more than 30 seconds to get it /////

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. - Professional support - Plugins, theme and development .
I don't answer to private message.
The topic has been locked.
More
8 years 9 months ago #145360 by bruce78
ok, thanks Denis, I'll get a test setup and will get back to you...
The topic has been locked.
More
8 years 9 months ago #145373 by bruce78

DenisChenu wrote: I think more on plugin using 'beforeSurveyPage' PHP plugin only. Because here : it's not javascript, it's PHP

Page size is not heavy, but more than 30 seconds to get it /////


Hi Denis,

Ok, so here's the survey url for v 2.5 which is taking c. 30 seconds to load.

And here's the url for the same survey running v 2.06 . This loads in about 7 or 8 seconds.

I did an export/import of the .lss file, so everything should be the same and both surveys are being loaded from the same machine.

Let me know your thoughts and if you think I should file a bug report?
The topic has been locked.
More
8 years 9 months ago #145379 by DenisChenu

bruce78 wrote: Let me know your thoughts and if you think I should file a bug report?

Yes, yes and yes ....

Surely hard to track down and fix .... i don't remind a big Expression Manager update between 2.6 and last 2.5X

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. - Professional support - Plugins, theme and development .
I don't answer to private message.
The topic has been locked.
More
8 years 9 months ago #145382 by ollehar
Check the browser console for output. Otherwise, we can do some profiling to find the bottleneck.
The topic has been locked.
More
8 years 9 months ago #145387 by bruce78
Ok, here's the bug report - bugs.limesurvey.org/view.php?id=11974 . Let me know if I can add anything further...
The topic has been locked.
More
8 years 9 months ago - 8 years 9 months ago #145389 by bruce78

olle wrote: Check the browser console for output.


Hi Olle, thanks for your suggestions... I've attached console output from FF and Chromium, although to be honest I'm not entirely sure what I'm looking at, although nothing sticks out at me apart from the message at the bottom in firefox
Code:
The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.

Chromium Console


Firefox Console

olle wrote: Otherwise, we can do some profiling to find the bottleneck.


The profiling sounds like a good idea, what does that involve?
Last edit: 8 years 9 months ago by bruce78. Reason: add titles to images
The topic has been locked.
More
8 years 9 months ago #145431 by jelo

bruce78 wrote: Ok, here's the bug report - bugs.limesurvey.org/view.php?id=11974 . Let me know if I can add anything further...

Did you report the bug to be private? Attached your survey? The ticket seems to be non-accessible for normal users.

The meaning of the word "stable" for users
www.limesurvey.org/forum/development/117...ord-stable-for-users
The topic has been locked.
More
8 years 9 months ago #145436 by bruce78

jelo wrote: Did you report the bug to be private? Attached your survey? The ticket seems to be non-accessible for normal users.


Yeah, the bug is private and the lss survey file is attached... do you think the bug report it should be available to all users?
The topic has been locked.
More
8 years 9 months ago #145445 by holch
The question is if you think it shouldn't. ;-)

If the bug is a general bug and there is no private data from your side and no security issue for Limesurvey, I don't see why a bug should be private (if private, only the core LS team can have a look at it, if not private a broader public can see it).

Now if your .lss file contains data that you don't want to make accessible publicly, then go for private.
If you report a security issue, that can be used by others to caus problems, go for private.
So I think only the reporter can decide if private is necessary or not.

Help us to help you!
  • Provide your LS version and where it is installed (own server, uni/employer, SaaS hosting, etc.).
  • Always provide a LSS file (not LSQ or LSG).
Note: I answer at this forum in my spare time, I'm not a LimeSurvey GmbH employee.
The topic has been locked.
Moderators: holchtpartner

Lime-years ahead

Online-surveys for every purse and purpose