Hacker News Reader

I think part of the thing is that it's relatively easy to measure how long it takes to generate your page. You don't need fancy tools or guidance from google to time how long you queries take.

Figuring out how to make the page appear to load faster or how to encourage browsers to cache your files in a smarter way is quite a bit more complicated and subtle.

View on HN

This is what I don't quite get; why make the distinction between "real speed" and "perceived speed"? Really, as far as the vast majority of your users are concerned, the speed of the page is from when they click you in a Google result to when Internet Explorer's status bar says "Done". How long your queries take relative to the page's rendering speed is irrelevant.

My main point is that the database and queries to it usually has much lower-hanging fruit for speed hacks.

Using perceived speed as a goal, I can load the most prominent and interesting aspects of a page first. Ads and whatnot can show up 1s later. So even before IE says "done" users can be gratified and interacting with my site.

I don't think that's true. Most people aren't watching the status bar, they're waiting to see a page appear.

Also, I can make the status bar say "Done" before my page is actually finished loading.

Reply on news.ycombinator.com