Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here are my answers for your questions:</p> <p>1) You should use images as less as possible, because images reduce the page load time a lot. Should use CSS instead, just use image where we can't use CSS. Many pieces of images should be joined in a single one to reduce the number of request (http://www.w3schools.com/css/css_image_sprites.asp).</p> <p>2) There are a lot of tools that can help us monitor and improve the performance of our app. The two important things we can inspect and improve are the page load time (include static assets like images, css, js,...) and benchmark of the backend code (Ruby code).</p> <p>I recommend these two tools to do the above measurement:</p> <ul> <li>YSlow (add-on for Firefox and Chrome): measure page load time with a lot of instruction of improvement. </li> <li>New Relic: tool to measure backend code: <a href="https://github.com/newrelic/rpm" rel="nofollow">https://github.com/newrelic/rpm</a></li> </ul> <p>Another tip, you should run Rails in development environment when optimizing code for performance. Because the app runs more slowly in dev mode than in production mode. If it runs fast in dev mode, it will run faster in production mode ;).</p> <p>3) The way you are using assets compression is not wrong but strange :), because you are trying to compress assets in development mode (configure in development.rb) while we should do it in production mode instead (configure in production.rb).</p> <p>4) It depends on your choice. But, yes, you should place all images in assets/images/ folder.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload