4 ms·
YSlow only applies to browser rendering and sort of assumes you are able to get the page to the browser in the first place. Somehow I doubt client-side renderin
by danielrhodes 18y ago
YSlow only applies to browser rendering and sort of assumes you are able to get the page to the browser in the first place. Somehow I doubt client-side rendering is going to be the bottleneck. ;-)
- aschobel 18y agoIt also looks at if you use a CDN, which may help him.
- iigs 18y agoI was under the impression it checked page retrieval times, which (after subtracting for idle network latency) would reveal which pages were transferring slow because of excess computation or disk use on the server. The idea being if it's slow for one user it's going to be _really_ slow for 1000+. I've not more than installed and tried YSlow once, so I can't say too much about it.
- dkubb 18y agoYSlow's primary purpose is to help you make sure the browser renders each page in the minimum amount of time. However YSlow does not only apply to browser rendering, following 6 of the 13 YSlow rules will result in a reduction of the total work the server must perform for each request.