jQuery Forum

^ Sure, there's a way to speed it up. Don't use any jQuery Mobile widgets on the page.

@watusiware

^ Sure, there's a way to speed it up. Don't use any jQuery Mobile widgets on the page.

well this is not an option, whole point of JQM is to use some widgets for UI at least in my case.

In my specific example I am sending complete jqm page from server, page has header,footer(with navigation) and as content I have listview widget with 21 item with icons and data-filter='true' .

• The size of page in JQM 1.4.0 is 9,637kB( 1,0kB gzip) and it takes in average 102.1ms (10 mesurment) to pageChange,

• In other case I tested the same staff with JQM 1.3.1 page size 9,637kB(1,0kB gzip) and in average it takes 102.8ms(10 mesurment) to pageChange  .

So results are more or less the same . I need less time to go to server and grab data, than to render page via $.mobile.changePage method :(. And this is tested on desktop browser, mobile browsers are probably event more slower with JS.

Regard to "pre-enhance" well this may be an option, I don't know how much better results can I expect , any clues :) ? But it is not strait forward with Listview widget, I need to do some hacks..
 

Wait... what is it that you are measuring and how?  You're muddying the issue if you include network time. You can't control that.

Hi,
I don't include network delay. Here is example how I mesure time.

1. ...
2. ...
   
3. $.mobile.loading("show"); 
4.  getHomePageUI().always(function (data) {//AJAX CALL
               $.mobile.loading("hide");
   
               if (data.d != null) {
                
                   var homePage = $(data.d);
                   homePage.appendTo($.mobile.pageContainer);
                  
                   console.time('home1');
                   $.mobile.pageContainer.pagecontainer("change", homePage);
                   console.timeEnd('home1');
                  
               }
               else {
                   MyApp.DisplayErrorMsg("Error calling service!!");
               }
           });
5. ...
6. ...
   

I didin't test this on pageload and  pagebeforeshow events, I will do that definitly, I just mesure time which is needed to complete    $.mobile.pageContainer.pagecontainer("change", homePage); method.If this is not valid test then my apologies, but I would like to know why is not?

Thanks

^ No, it's not a valid test. The real times are almost certainly *longer* than what you are measuring.