Re: What is the minimum Internet speed connexion that the GWT team is considering when testing their GWT application ?

Hello,

Ok, firstly I should read the documentation, and I will do it, but maybe you could clarify me most of my preoccupations :

For now it seems that my resources (images, css) are taking enough memory at the initial download. Maybe you can help me to reduce it... :)

I am asking the following : 

#1

I have not used "inline CSS", I mean, I did not put any css code in my ui binder files. I just use 3 stylesheets (admin.css, common.css, normal.css) that are declarated in the client bundle. 

- Will "inline css" reduce the code to download ?

- How could I do to not download the admin.css at startup but just when the user go to the admin ?

#2  

Actually I am thinking that : "all images declarated as ImageResource or DataResources inside a ClientBundle will be download  at startup time." Is it true ?

#3

As Joseph tolds me, the server should  compress the content (RPC + images) ?
 - Could I do that with YUI Compressor ?
 - I heard about a tool to compress images (Webp - https://developers.google.com/speed/webp/index )...Should I use a combination of YUI Compressor AND Webp ?

 - How to compress RPC ?

#4

Finally there is so much tools that I do not what should be the code optimization workflow ?

** I assume that I should not go to a further step without having accomplished the current one. (I would not play with speed tracer without having already analyzed all code split points)

For the moment, my vision about using tools for code optimization is the following one (could you correct or complete me if I have misunderstood or have forgotten an important thing ?) : 

step 1 - (compiler) - Use -compileReport and see where should I introduce code split points.

step 2 - (plugin) - Use inspectorwidget (I have not used yet...) to optimize the DOM structure (minimizing the use of gwt widgets). 

step 3 - (tool) - Use Speed tracer to see what happen at execution time (if handlers are slowing my app)

step 4 - (tool)  - Use various other tools to see their suggestions about optimizing the code:

                           - Page speed Service : https://developers.google.com/speed/pagespeed/service)

                           - WebPageTest :  http://www.webpagetest.org/

                           - YSlow : http://developer.yahoo.com/yslow/

step 5 - (compiler)  - when ready for production,   use more compiler option (closureCompiler...) to reduce the javascript code generated.

Remarks, I do not know at witch moment should I use Chrome Developper tool with the "Timeline", "Profile" ... functionalities ?

Thanks a lot, again, for your help.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/0sixH8JfEg0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.