David, you have very good points here. See below: >>>>> ... >>>> Yeah of course I could do that too. It is psychologically proven that >>>> the subjective waiting time is shorter when you see something as >>>> soon as >>>> possible. >>> Yes and what I'm suggesting is providing actual content as soon as >>> possible. The whole idea of the "critical rendering path" is exactly >>> about engineering your webpage so useful content is provided to the >>> user as soon as possible (which is as soon as you're currently capable >>> of showing a "Fetching data" screen). >>> >>> If you're being serious about bandwidth and UX (including percieved >>> performance), it's exactly what you should be doing, I believe. >> I agree totally with you here. But again, I want to know the 404 in one >> request, not within two requests (Ajax). > I am suggesting that you make a single request, not two. > You're focusing on the HTTP status code, but in the end the code isn't > important. Showing the relevant information to the user is what's > important. The status code (client-side or server-side) is just a > means to get there. > What I'm proposing is to bypass the "which status is it?" part to get > to the "show the relevant information to the user" part.