At what point do you perform foreground optimization?

Question

I am talking about things like page / style caching, mini javascript, etc.

Half of me thinks that it’s better to do these things as early as possible while still in the process of development, so I can consciously be aware of more realistic problems with speed and response, and also interact with something that more closely resembles what will be deployed into production, but the other half of my brain thinks that it makes sense to do nothing until launch, so I constantly work with raw data that was not optimized during development.

Is there any general or generally accepted wisdom on this?

Answer 1

I do all the optimizations at the end. This way I know when something is not working because the code is wrong. I tried to optimize things too soon, and realized that I wasted an hour because I was caching something, etc.

Answer 2

Understand that the user spends most of his time waiting for frontend objects to be (down) loaded. Your application can generate html in 0.1 second, but the user spends at least 2 seconds waiting for all images to load, etc. Getting this load time to a small number will positively increase the user interface.

, GZIP javascript. YSlow - . .

- CSS. css javascript, , .

, -, .

Answer 3

, , YSlow, .

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

, - . / , ( , , ).

Answer 4

- :)

, , .

, , , , , ( ).

Answer 5

, ​​ , . (: 1/2 , + r!), , , , - . , .

Answer 6

, : " , , ". , , , .

, , , , , " ". , , , " " , , , .

Answer 7

, , , , , .

, . , ( , , ), . http .. . , , ; , .

Answer 8

, .

DB JS/Jquery JavaScripts

By identifying bottlenecks in advance, by creating / modifying each part of the application that deals with these bottlenecks, you can spend time tuning, knowing that spending time while coding, you get better performance in the end.

He also seeks to make us less lazy, always creating the optimal code and learning that it is in real life.