first things first or getting pedantic on http-communication

As I am sitting in mobilehome, hitting reload on toyflish.com again and again watching the chrome network tab, jerking of by the speed of pageload I was recognizing my todays major issue to solve.

The most important selfie on my home screen was top in the source code but loaded at last. Terrible I should be the first thing to be seen on my homepage ;).

I found out that chrome was requesting after all other images because it was background-image declared by inline css.

To get it on top of the list of things to load from the server I added it as a img not displayed

<img src=".." style="display:none">