- Posts: 77
- Thank you received: 4
Welcome to the LimeSurvey Community Forum
Ask the community, share ideas, and connect with other LimeSurvey users!
Very slow rendering of first page
- bruce78
- Topic Author
- Offline
- Senior Member
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...
- DenisChenu
- Offline
- LimeSurvey Community Team
- Posts: 13935
- Thank you received: 2551
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 service on demand , plugin development .
I don't answer to private message.
- bruce78
- Topic Author
- Offline
- Senior Member
- Posts: 77
- Thank you received: 4
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?
- DenisChenu
- Offline
- LimeSurvey Community Team
- Posts: 13935
- Thank you received: 2551
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 service on demand , plugin development .
I don't answer to private message.
- bruce78
- Topic Author
- Offline
- Senior Member
- Posts: 77
- Thank you received: 4
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...
<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()!="" && $(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?
<script type="text/javascript" charset="utf-8"> $(document).ready(function(){ $('#movenextbtn, #movesubmitbtn').hide(); }); </script>
- DenisChenu
- Offline
- LimeSurvey Community Team
- Posts: 13935
- Thank you received: 2551
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 service on demand , plugin development .
I don't answer to private message.
- bruce78
- Topic Author
- Offline
- Senior Member
- Posts: 77
- Thank you received: 4
- bruce78
- Topic Author
- Offline
- Senior Member
- Posts: 77
- Thank you received: 4
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?
- DenisChenu
- Offline
- LimeSurvey Community Team
- Posts: 13935
- Thank you received: 2551
Yes, yes and yes ....bruce78 wrote: Let me know your thoughts and if you think I should file a bug report?
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 service on demand , plugin development .
I don't answer to private message.
- ollehar
- Offline
- LimeSurvey GmbH Employee
- Posts: 522
- Thank you received: 108
- bruce78
- Topic Author
- Offline
- Senior Member
- Posts: 77
- Thank you received: 4
- bruce78
- Topic Author
- Offline
- Senior Member
- Posts: 77
- Thank you received: 4
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
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?