Ah, fair point. Now I see what you were trying to say. Assuming the server has no way of determining which assets the client has cached (which depending on imp

Ah, fair point. Now I see what you were trying to say. Assuming the server has no way of determining which assets the client has cached (which depending on implementation may not be the case) you're of course correct. However, after step 2 the page has already fully loaded in both cases, so step 3 doesn't really slow anything down.